MCP Integration - Model Context Protocol
Power AI assistants with real-time financial data. Connect Claude, ChatGPT, or any MCP client to the Fiscal.ai API in minutes.
Claude
Fiscal.ai is an official Claude Connector. Click the link, hit Add, and sign in — that's it.
Install Fiscal.ai Connector →
Once installed, Fiscal.ai tools are available in every Claude chat. To make Claude always reach for Fiscal.ai by default, enable Memory (Settings → Memory → On) and send this prompt:
Always use the Fiscal.ai Connector every time I ask for financial data. Save this to your memory.
Other AI Clients
For any MCP-compatible client, use this server URL:
https://api.fiscal.ai/mcp/sse
ChatGPT
Requires ChatGPT Plus, Pro, or Business. Only available on the web (chatgpt.com).
- Open Settings → Apps → scroll to Advanced settings → toggle Developer Mode on
- Click the Create button that appears
- Enter a name (e.g., "Fiscal.ai"), a description, and paste the server URL:
https://api.fiscal.ai/mcp/sse - Check "I trust this provider", then click Create
- In a new chat, click + → More → Developer Mode → enable "Fiscal.ai"
Claude Code (CLI)
claude mcp add --transport sse fiscal https://api.fiscal.ai/mcp/sse
When you first use a Fiscal.ai tool, you'll be prompted to authenticate via OAuth.
Cursor and Other MCP Clients
For clients that support direct SSE connections with OAuth:
{
"mcpServers": {
"fiscal": {
"url": "https://api.fiscal.ai/mcp/sse"
}
}
}
For clients that only support stdio transport, use the mcp-remote bridge:
{
"mcpServers": {
"fiscal": {
"command": "npx",
"args": ["-y", "mcp-remote@latest", "https://api.fiscal.ai/mcp/sse"]
}
}
}
Authentication:
All connections use OAuth, but OAuth does not create a separate entitlement tier. It maps the MCP session back to your existing Fiscal.ai account and API access. No API key configuration is needed in the client, but every tool call is still checked against the same plan limits your regular API key has.
What is MCP?
The Model Context Protocol (MCP) is an open standard that enables AI assistants to connect with external data sources through a standardized interface. It lets AI models access real-time data and execute functions seamlessly.
Fiscal.ai's MCP server exposes our financial data API through this protocol, so any MCP-compatible AI assistant can query the same company financials, ratios, market data, and other resources your plan already allows. MCP is not a wider catalog and it does not bypass plan enforcement.
How It Works
- MCP Client (Claude, ChatGPT, etc.) connects to our MCP endpoint
- OAuth Authentication — you sign in with your Fiscal.ai account; that MCP session is tied back to your existing Fiscal.ai API access
- Tool Calls are routed through our REST API infrastructure, where the same company coverage, feature entitlement, and rate-limit checks are enforced
- Responses are formatted per MCP standards and streamed back to the AI assistant
What You Can Do
The MCP server routes tool calls to the same Fiscal.ai API endpoints your plan includes. Your assistant can only retrieve data you could retrieve yourself with your API key for the same tickers, periods, and features.
If you are on the free plan, that means:
- You can connect to the MCP server normally
- Requests are still rate-limited the same way as the REST API
- Company-level data access is limited to the 25 free-plan companies
- Seeing a tool in your MCP client does not mean your plan has broader access to that endpoint
Testing Your Connection
Quick Test
After setup, test your connection by asking your AI assistant:
Get the company profile for NASDAQ_MSFT
If connected, it should call the company_profile tool and return Microsoft's profile. This is a better smoke test than asking for broad catalog coverage, because it confirms the server is working on a ticker the free plan is actually allowed to access.
Usage Examples
Once connected, ask natural language questions about financial data:
Company Analysis:
- "What's Apple's current P/E ratio compared to Microsoft?"
- "Show me Tesla's quarterly revenue growth over the last 2 years"
- "Compare the profit margins of Netflix and Disney"
Financial Statements:
- "Get Amazon's latest cash flow statement"
- "Show me the balance sheet for NVIDIA as reported in their 10-K"
- "What are Google's standardized income statement metrics?"
Market Data:
- "Has Apple had any stock splits recently?"
- "Show me the daily stock price trend for Microsoft this year"
- "What's the current shares outstanding for Tesla?"
Document Research:
- "Get page 15 of Tesla's latest 10-K filing as an image"
- "Download the PDF of Apple's most recent earnings report"
The MCP server accepts the same query parameters and data formats as the REST API. See the API Reference for details on company identifiers, statement types, and available parameters.
Troubleshooting
OAuth Sign-in Issues
- Make sure you have an active Fiscal.ai account
- If the OAuth flow doesn't redirect, try clearing your browser cookies for fiscal.ai
- For Claude Desktop, ensure you're on the latest version (older versions may not support remote MCP servers natively — use the
mcp-remotebridge instead)
Server Not Appearing in Claude Desktop
- Verify the JSON configuration is valid (no trailing commas, proper quotes)
- Completely quit Claude Desktop (use Cmd+Q on Mac, not just closing the window)
- Check that
npxis available in your system PATH - Try running the npx command manually in terminal to verify it works
Connection Timeouts
- Check your internet connection
- Verify you can access
https://api.fiscal.aifrom your browser - If behind a corporate firewall, ensure SSE connections are allowed
- Try the MCP Inspector to test the connection directly
Tools Not Working as Expected
- Verify you're using valid company identifiers (e.g.,
NASDAQ_AAPL) - Check that date parameters are in YYYY-MM-DD format
- Ensure period types are spelled correctly (annual, quarterly, ltm, etc.)
- Review error messages returned by the MCP server for specific guidance
- A tool being visible in Claude, ChatGPT, or Cursor does not mean your account has unrestricted access to it