Skip to content

Daily insider-buy trading plan

Connect InsiderAlpha to Cursor

Cursor is configured from a JSON file rather than a settings screen, which means you can commit the setup to a repository and share it with a team. That is also the risk: the same file is where people paste tokens by accident. Use the environment variable form below if you go the token route, and note that Cursor's top level key is mcpServers, which is not the key VS Code uses.

Server URL: https://mcp.insideralpha.ai/mcp. You need an InsiderAlpha account. Sign up free if you do not have one, then follow the steps below.

Setup in Cursor

3
  1. Choose the config file

    Use ~/.cursor/mcp.json to enable InsiderAlpha everywhere, or .cursor/mcp.json inside a project to scope it to that repository.

  2. Add the server block

    The OAuth form below is the simpler one. Cursor opens a browser for sign-in on first connect, and no token is stored in the file.

  3. Reload Cursor and check the MCP settings pane

    The InsiderAlpha tools should appear once the server connects.

Configuration

Paste one of these into ~/.cursor/mcp.json or .cursor/mcp.json.

OAuth sign-in, nothing secret in the file

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

Personal Access Token, read from an environment variable

{
  "mcpServers": {
    "insideralpha": {
      "url": "https://mcp.insideralpha.ai/mcp",
      "headers": {
        "Authorization": "Bearer ${env:INSIDERALPHA_MCP_TOKEN}"
      }
    }
  }
}

Mint the token on your MCP tokens page. It starts with iamcp_ and is shown once. Keep it in the environment variable, not in the file: a project level .cursor/mcp.json is usually committed, and a token pasted there is a token published.

Cursor troubleshooting

3

Failure modes specific to this client, and what is actually going on.

What you seeWhy, and what to do
I copied a VS Code example and nothing happensVS Code uses a top level servers key and requires a type field. Cursor uses mcpServers and infers the transport from the url. The two files look similar enough to swap by accident and neither one warns you.
The server works in one project but not anotherA project level .cursor/mcp.json only applies to that project. Move the block to ~/.cursor/mcp.json to make it global.
Revoking a token did not cut access immediatelyToken validation is cached for about a minute, so a revoked Personal Access Token can keep working for up to roughly sixty seconds. It stops after that.

Good to know

  • Cursor also accepts static OAuth client credentials in mcp.json for servers that require them. InsiderAlpha does not require them, so omit the auth block.

What the server exposes

19 tools in total: 14 read-only research, market and portfolio tools, plus 5 that act on a connected broker account and are switched off unless you explicitly enable them. The full list, the scopes and the rate limits are the same whichever client you use, so they live in one place: the MCP server reference.

Setting up a different client

Cursor setup steps verified against Cursor documentation: Model Context Protocol on 2026-08-09. Cursor controls its own interface and can change it without notice, so if a menu name here does not match what you see, trust their documentation over ours and tell us.

InsiderAlpha returns SEC filing data and research output. It is informational and is not investment advice, and nothing it returns is a recommendation to buy or sell any security. You are responsible for every order placed from your own account.

Related