Remote MCP Connection

The Index Alpha API exposes a standards-compatible remote MCP server at https://api.indexalpha.id/mcp. You can connect Claude Desktop, Cursor, Windsurf, or any other MCP-capable client directly to this endpoint — no local server setup required.

What remote MCP enables

Remote MCP lets your AI client query live IDX broker summary and foreign-flow data in real time. Unlike the local MCP server setup described in the AI Integration guide, the remote endpoint:

• requires no Node.js runtime or local files
• authenticates with your Google account (OAuth 2.0) — no API key pasting
• shares your existing subscription quota with the REST API
• is always up to date with the latest API features

Subscription and quota requirements

• You need an active Index Alpha subscription (Starter or Professional).
• Free-plan accounts can access the remote MCP endpoint but are subject to the same daily/monthly quota as the REST API.
• Each successful MCP tool call consumes 1 quota unit, identical to an equivalent REST request.
• Check your remaining quota with the get_account_status tool or the Usage endpoint.

Connect from AI clients

Any AI client that supports the Model Context Protocol (MCP) can connect to the remote endpoint:

https://api.indexalpha.id/mcp

The setup steps differ slightly per client, but the first connection always ends with a Google sign-in in your browser. There is no API key to paste - authentication and your subscription are resolved server-side.

Claude Desktop

1. Open Claude Desktop → Settings → Developer → Edit Config. This opens claude_desktop_config.json.
2. Paste the following into the mcpServers object:

{
  "mcpServers": {
    "index-alpha": {
      "url": "https://api.indexalpha.id/mcp",
      "transport": "streamable-http"
    }
  }
}

3. Restart Claude Desktop. Claude will automatically discover the available tools. You can now ask questions like:

"What does the broker summary for BBCA look like on 2026-03-26?"

Claude will call the get_broker_summary tool and display the result inline.

Claude Code

In your terminal, add the server with:

claude mcp add index-alpha https://api.indexalpha.id/mcp

On first use, Claude Code opens a browser window for the Google sign-in. Verify the connection with:

claude mcp list

You can then ask Claude Code for market data in any project, e.g.:

"Use the index-alpha MCP server: what is the foreign flow for TLKM this month?"

ChatGPT

1. Open the ChatGPT desktop app (macOS or Windows).
2. Click your profile icon → Settings → Work with Apps.
3. Click Connect app and choose MCP Server, then paste the server URL:

https://api.indexalpha.id/mcp

4. Approve the connection in the browser that opens (Google sign-in). ChatGPT then discovers the available tools and can call them in your conversations.

Cursor / Windsurf

1. Open Settings → AI → MCP Servers.
2. Add a new server with URL https://api.indexalpha.id/mcp and transport streamable-http.
3. The client will prompt you to sign in with Google on first use.

Generic MCP client

If your client supports the MCP specification, configure it with:

• Transport: Streamable HTTP
• Endpoint: https://api.indexalpha.id/mcp
• Authentication: Google OAuth 2.0 (handled automatically by the server)

Authentication flow

1. Your client sends a request to the MCP endpoint.
2. The server responds with a Google OAuth challenge.
3. Your client opens a browser window for you to sign in with your Google account.
4. After granting access, the server receives a Google ID token.
5. The server resolves your Index Alpha account, verifies your subscription is active, and provisions a dedicated MCP key for your account (used only for quota accounting).
6. The session is established and tools become available.

No API key is ever stored or transmitted to the client. The server uses your Google identity to look up your account internally.

About your MCP key. Connecting to the MCP endpoint creates a dedicated key on your account, visible in the dashboard under "MCP Access". It is used only by the MCP endpoint for quota accounting, is never exposed to any client, does not count toward your API key limit, and cannot be deleted manually.

Available tools (v1)

The remote MCP server exposes three tools:

get_broker_summary

Retrieves aggregated daily broker activity for a stock ticker.

get_foreign_flow

Returns aggregated foreign buy, sell, and net trading activity.

get_account_status

Returns your current plan, monthly limit, and period end date. Takes no parameters.

Limits and rate limiting

• MCP calls share the same rate limits as the REST API.
• When your quota is exhausted, MCP calls return an error message explaining the situation.
• The get_account_status tool never consumes quota.

Privacy and security

• Google OAuth only. Authentication is handled entirely through Google's OAuth 2.0 flow. Index Alpha never sees or stores your Google password.
• No API key exposure. Your API key is resolved server-side from your account. It is never sent to or stored on the client.
• Encrypted in transit. All communication uses TLS.
• Minimal data. The MCP server returns only the data you request. No internal IDs, SQL queries, or stack traces are exposed.
• Usage logging. MCP calls are logged for quota accounting and abuse prevention, identical to REST API calls.

Disconnecting and revoking access

Disconnect a client

In your MCP client (Claude Desktop, Cursor, etc.), remove or disable the index-alpha MCP server entry. This stops the client from making further requests.

Revoke Google OAuth access

1. Go to Google Account → Security → Third-party apps.
2. Find Index Alpha in the list of apps with access.
3. Click Remove access.

This immediately terminates all active MCP sessions. To reconnect, you will need to sign in again through the OAuth flow.

Troubleshooting