Cursor

Cursor 0.45+ accepts custom MCP servers via Settings → MCP or by editing `mcp.json`, OAuth runs the first time you invoke a tool.

Add to Cursor

One click installs the server; the manual config below does the same thing.

Setup

Cursor

Cursor 0.45+, open Settings → MCP → Add new MCP server, or edit ~/.cursor/mcp.json (global) or .cursor/mcp.json (workspace) directly:

{
  "mcpServers": {
    "creatorland": {
      "url": "https://mcp.creatorland.com/mcp"
    }
  }
}

Restart Cursor after editing mcp.json so the new server is picked up. Cursor prompts for OAuth on the first tool call, the consent flow opens in your default browser.

Workspace-scoped mcp.json overrides the global file entirely.

Loading setup…

Who it’s for: Developers running Cursor as their primary editor + agent.
Compatibility: Cursor 0.45 and later supports custom MCP servers. Configuration lives in `~/.cursor/mcp.json` (global, applies to every Cursor workspace) or `.cursor/mcp.json` at the project root (workspace-scoped, takes precedence). Both shapes use the same JSON schema.
Verify the connection: After you sign in with your Creatorland account, your tools appear in the client, scoped to your account. If the list comes back empty, that signals the email you signed in with has no Creatorland account yet, create one (or sign in with the right one) at creatorland.com and reconnect. An empty list still confirms the OAuth handshake succeeded and you’re pointed at the right server.

Troubleshooting

After editing `mcp.json`, restart Cursor so the new server is picked up, hot-reload isn’t reliable for MCP config.
If the OAuth window opens but never returns, check that your browser allows localhost callbacks from Cursor.
Workspace-scoped `mcp.json` overrides the global file entirely; if a global server isn’t showing up in a project, check whether the workspace has its own `mcp.json`.

Other clients

Perplexity

Grok