Cursor Client

Connect Cursor to your Ideagram account with the hosted MCP endpoint and a personal access token. You do not need to clone this repository, install Supabase, or look up your user ID.

Create Your Token

1. Sign in to Ideagram and open Settings > MCP Access.
2. Create a token named Cursor and choose the access scope you need.
3. Copy the token shown once. It starts with idg_pat_.

The token identifies your account. Ideagram resolves your user ID on the server and applies your access permissions and token scope.

Configure Cursor

Open your personal Cursor MCP configuration at ~/.cursor/mcp.json (%USERPROFILE%\.cursor\mcp.json on Windows). Add the ideagram entry to mcpServers, keeping any existing servers:

{
  "mcpServers": {
    "ideagram": {
      "url": "https://ideagram.dev/mcp",
      "headers": {
        "Authorization": "Bearer <YOUR_IDEAGRAM_TOKEN>"
      }
    }
  }
}

Replace <YOUR_IDEAGRAM_TOKEN> with the token you copied, including its idg_pat_ prefix. Keep this personal configuration out of source control.

Alternatively, set IDEAGRAM_MCP_TOKEN in the environment inherited by Cursor and use "Authorization": "Bearer ${env:IDEAGRAM_MCP_TOKEN}". Restart Cursor after changing its environment. Cursor supports URL/header configuration and environment interpolation; see Cursor's MCP documentation.

Enable or reload the server in Cursor's MCP settings. Ask Cursor to list your Ideagram organizations or projects to verify the connection. No IDEAGRAM_MCP_USER_ID setting is needed.

If authentication fails, check that the token is complete and has not been revoked. You can revoke it and create a replacement from the same settings screen. See Remote HTTP MCP for server configuration and Troubleshooting for other errors.

Use the hosted configuration above for your real Ideagram account, even when Cursor runs on your own computer.