MCP Integration - Model Context Protocol

Claude

Fiscal.ai is an official Claude Connector. Click the link, hit Add, and sign in — that's it.

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 company financial data or company news. Save this to your memory.

Other AI Clients

Server URL: https://api.fiscal.ai/mcp (Streamable HTTP). A legacy SSE endpoint is also available at https://api.fiscal.ai/mcp/sse for older clients.

Authentication works two ways and both give the same access:

• OAuth — your client opens a browser, you sign in. No keys to copy. Works in Claude, ChatGPT, Microsoft Copilot Studio, Mistral Le Chat, Cursor, VS Code Copilot, Gemini CLI, LibreChat, TypingMind, Replit, Notion AI.
• API key as Bearer header — paste your Fiscal.ai API key as Authorization: Bearer <key>. The most reliable path, and the only one for clients like Codex CLI, Continue.dev, Cline, Roo Code, Goose, AnythingLLM, Cherry Studio, n8n, Bedrock AgentCore, and any framework SDK (LangChain, LlamaIndex, Pydantic AI, Strands, HuggingFace).

ChatGPT (Developer Mode)

Requires ChatGPT Plus, Pro, Business, or Enterprise. Web only.

1. Settings → Apps → Advanced settings, toggle Developer Mode on
2. Create → name "Fiscal.ai", URL https://api.fiscal.ai/mcp, check "I trust this provider", Create
3. In a chat: + → More → Developer Mode → enable Fiscal.ai

Claude Code (CLI)

# OAuth
claude mcp add --transport http fiscal https://api.fiscal.ai/mcp

# Or skip OAuth with an API key
claude mcp add --transport http fiscal https://api.fiscal.ai/mcp \
  --header "Authorization: Bearer YOUR-API-KEY"

Cursor and similar JSON-config clients

{
  "mcpServers": {
    "fiscal": {
      "url": "https://api.fiscal.ai/mcp",
      "headers": { "Authorization": "Bearer YOUR-API-KEY" }
    }
  }
}

The same shape works for Continue, Cline (set "type": "streamableHttp"), Roo Code ("type": "streamable-http"), Goose, Cherry Studio (uses requestHeaders), Chatbox, AnythingLLM ("type": "streamable"), LM Studio, Msty, TypingMind, and Zed (root key is "context_servers"). Omit headers to use OAuth instead.

VS Code (GitHub Copilot Agent Mode)

Add to .vscode/mcp.json. Note the root key is servers, not mcpServers:

{
  "servers": {
    "fiscal": {
      "type": "http",
      "url": "https://api.fiscal.ai/mcp",
      "headers": { "Authorization": "Bearer ${input:fiscal-api-key}" }
    }
  },
  "inputs": [
    { "id": "fiscal-api-key", "type": "promptString", "description": "Fiscal.ai API key", "password": true }
  ]
}

The same config applies to JetBrains, Eclipse, Xcode, and Visual Studio (use .mcp.json for VS 2022/2026).

Stdio-only clients

For clients that can't connect to remote MCP servers directly, bridge with mcp-remote:

{
  "mcpServers": {
    "fiscal": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote@latest",
        "https://api.fiscal.ai/mcp",
        "--header",
        "Authorization: Bearer YOUR-API-KEY"
      ]
    }
  }
}

Use mcp-remote ≥ 0.1.16 (CVE-2025-6514 affected earlier versions).

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

1. MCP Client (Claude, ChatGPT, etc.) connects to our MCP endpoint
2. OAuth Authentication — you sign in with your Fiscal.ai account; that MCP session is tied back to your existing Fiscal.ai API access
3. Tool Calls are routed through our REST API infrastructure, where the same company coverage, feature entitlement, and rate-limit checks are enforced
4. 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-remote bridge 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 npx is 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.ai from 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