Cursor

Connect Moonlit to Cursor through its MCP configuration file, for all projects or one.

Before you start

  • A Moonlit account. Sign in at app.moonlit.ai with your email and the one-time code it sends you, or with Google or Microsoft. Organizations can use single sign-on. Signing in creates the account if you do not have one.

The server URL:

https://mcp.moonlit.ai/mcp

Add the server

Add the server to ~/.cursor/mcp.json for all projects, or to .cursor/mcp.json at the root of one project:

{
  "mcpServers": {
    "moonlit": {
      "url": "https://mcp.moonlit.ai/mcp"
    }
  }
}

Sign in

Cursor detects that the server needs a sign-in and shows a connection prompt for Moonlit. Follow it, sign in with your Moonlit account and click Allow.

Check it works

Open Customize in the sidebar and switch Moonlit on; its nine tools appear under available tools. In a chat in agent mode, ask:

Prompt

Find the official text of Article 6 of the EU AI Act.

A good answer cites CELEX 32024R1689, links to the official publication, and quotes the article.

Use an MCP key instead

For a configuration shared with your team, or a machine that cannot open a browser, an organization MCP key replaces the sign-in. Keys come from Organizations; keep them in an environment variable, never in the file itself.

{
  "mcpServers": {
    "moonlit": {
      "url": "https://mcp.moonlit.ai/mcp",
      "headers": {
        "Authorization": "Bearer ${MOONLIT_MCP_KEY}"
      }
    }
  }
}

If something fails

  • Check that the URL ends in /mcp.
  • Remove the server entry, add it again, and sign in once more.
  • Ask for your Moonlit account status. The check is free and shows your remaining calls.
  • Cursor shows an MCP error in the chat: open the Output panel (Cmd+Shift+U), choose MCP Logs, and read the last lines for the Moonlit server.

For the app's own steps, see the Cursor MCP documentation. Still stuck? Email support@moonlit.ai with what you see.

esc
↑↓ navigateenter openesc close