MCP / Connectors

MCP / Connectors

Fiscal.ai data inside any AI assistant. Pick your client.

Claude and ChatGPT: click, Add, sign in. Microsoft 365 Copilot: admin enables Fiscal.ai under Copilot connectors, then you connect it in Copilot Chat under Settings, Sources. Gemini Enterprise: admin adds the Fiscal.ai data store, then you sign in.

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).

Microsoft 365 Copilot and Copilot Studio

For Microsoft 365 Copilot, use OAuth instead of API-key auth. As of June 5, 2026, Microsoft documents that MCP plugins don't support API key authentication when packaged as a Copilot plugin or declarative agent — API-key auth remains available for the generic MCP clients above. Copilot Studio also requires Streamable HTTP transport and no longer supports SSE after August 2025, so register the /mcp endpoint, not /mcp/sse.

• MCP server URL: https://api.fiscal.ai/mcp

• OAuth authorization URL: https://api.fiscal.ai/authorize

• OAuth token URL: https://api.fiscal.ai/oauth/token

• OAuth callback URL to allow in your registration: https://teams.microsoft.com/api/platform/v1.0/oAuthRedirect (Microsoft requires this exact redirect URI)

• Microsoft plugin manifest template: https://api.fiscal.ai/.well-known/microsoft-copilot/ai-plugin.json

• MCP tool description JSON: https://api.fiscal.ai/.well-known/microsoft-copilot/mcp-tools.json

• Copilot Studio custom connector schema: https://api.fiscal.ai/.well-known/microsoft-copilot/openapi.json

If you package Fiscal.ai as a Microsoft 365 declarative agent, register OAuth in Teams developer portal or the Microsoft 365 Agents Toolkit, then replace the placeholder reference_id in the plugin manifest with the OAuth registration ID. Users should then be prompted to sign in rather than paste a Fiscal.ai API key.

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) or newer, keep the existing JSON.