Installation

FinanceDataAPI exposes a remote HTTP MCP server. Every client-specific setup reduces to the same three values:

1. URL — https://<your-financedataapi-host>/v1/mcp
2. Header name — X-API-Key
3. Header value — your FinanceDataAPI API key

Claude Desktop

Claude Desktop can connect directly to remote MCP servers from claude_desktop_config.json.

{
  "mcpServers": {
    "financedataapi": {
      "url": "https://<your-financedataapi-host>/v1/mcp",
      "headers": {
        "X-API-Key": "<YOUR_API_KEY>"
      }
    }
  }
}

After saving the file, fully exit Claude Desktop and reopen it so the tool inventory refreshes.

Cursor / Continue

Cursor and Continue both support remote MCP servers. Their config file shapes evolve over time, but the FinanceDataAPI values stay the same: server name, URL, and one auth header.

Use this object as the server entry inside your client's MCP settings:

{
  "name": "financedataapi",
  "type": "http",
  "url": "https://<your-financedataapi-host>/v1/mcp",
  "headers": {
    "X-API-Key": "<YOUR_API_KEY>"
  }
}

npx

FinanceDataAPI does not publish an official npm MCP wrapper from this repository. If your tool only supports local stdio servers, place a remote-to-stdio MCP bridge in front of the FinanceDataAPI HTTP endpoint and feed the bridge these values:

FINANCEDATAAPI_MCP_URL=https://<your-financedataapi-host>/v1/mcp
FINANCEDATAAPI_MCP_AUTH_HEADER=X-API-Key
FINANCEDATAAPI_MCP_AUTH_VALUE="<YOUR_API_KEY>"

The important part is not the bridge implementation; it is that every upstream request reaches /v1/mcp with one valid FinanceDataAPI auth header.

Docker

FinanceDataAPI does not publish an official Docker image for a local MCP bridge either. If your deployment standard requires containers, containerize the same bridge pattern:

Remote MCP bridge container
  -> forwards HTTP requests to https://<your-financedataapi-host>/v1/mcp
  -> injects X-API-Key: <YOUR_API_KEY>

That keeps desktop or IDE tooling local while the actual FinanceDataAPI MCP server remains remote.

Sanity checks

Before you debug the client, verify these basics:

• The URL ends with /v1/mcp
• The API key belongs to an active, non-disabled account
• The client was fully restarted after the config change
• Your network can reach the FinanceDataAPI host over HTTPS