Skip to main content
FocusAlpha ships a hosted Model Context Protocol server. Point an MCP-capable client at it and the model can search transcripts, pull financials, screen companies, and watch events — every dataset in the API, as tools.
The server speaks the HTTP transport and is stateless. Authentication is your normal API key, sent as a header on every request:
MCP tool calls are ordinary API calls underneath. They spend the same credits, respect the same plan entitlements, and count against the same rate limits as REST requests — see Plans & credits. A missing or invalid key is rejected with 401 before any data is read.
This is the data server. Separately, https://docs.focusalpha.ai/mcp serves this documentation site itself over MCP (search and read the docs) — no API key required. Connect both if you want an agent that can look up the docs and pull the data.

Claude Code

Claude Desktop

Add to claude_desktop_config.json:

Cursor

Add to .cursor/mcp.json (project) or ~/.cursor/mcp.json (global):

Other clients

Any MCP client that supports the HTTP transport and can attach an Authorization header works the same way — configure the URL and the header, nothing else is required.
Your API key travels in the client configuration. Keep the config file out of source control, and revoke the key in the dashboard if it leaks.

Available tools

Tools map one-to-one onto the REST API. The model can also call list_datasets and list_coverage at any time to discover what is available and how fresh it is. Datasets your plan does not include return a clear upgrade message rather than data — the model will tell you which tier a tool needs.

Authentication

Creating and managing the API key your MCP client uses.

Plans & credits

What each plan unlocks and how tool calls are metered.