Home · Docs · MCP clients

Add the FoxAPIs MCP server to your AI client

The FoxAPIs data server is one remote MCP server. Your client needs three things: the address, the transport, and your FoxAPIs key as a bearer token. This page holds the part that is the same for every data-source page on the site, so each of those pages can show only its own address and snippet.

The three things every client needs

Claude Code

Where it goes: Run in a terminal. The client's own page on remote servers is its MCP documentation.

claude mcp add --transport http foxapis-data https://foxapis.com/mcp/data \
  --header "Authorization: Bearer YOUR_KEY"

The Claude Code docs show this form (--transport http, name, URL, --header) for a server that takes a bearer token.

Cursor

Where it goes: .cursor/mcp.json in a project, or ~/.cursor/mcp.json for every project. The client's own page on remote servers is its MCP documentation.

{
  "mcpServers": {
    "foxapis-data": {
      "url": "https://foxapis.com/mcp/data",
      "headers": {
        "Authorization": "Bearer YOUR_KEY"
      }
    }
  }
}

Cursor's remote-server example uses a url and a headers object.

VS Code (Copilot)

Where it goes: .mcp.json at the workspace root, or ~/.copilot/mcp-config.json. The client's own page on remote servers is its MCP documentation.

{
  "mcpServers": {
    "foxapis-data": {
      "type": "http",
      "url": "https://foxapis.com/mcp/data",
      "headers": {
        "Authorization": "Bearer YOUR_KEY"
      },
      "tools": [
        "*"
      ]
    }
  }
}

Do not store a real key in a file you share.

Cline

Where it goes: cline_mcp_settings.json (open it from Cline's MCP Servers panel). The client's own page on remote servers is its MCP documentation.

{
  "mcpServers": {
    "foxapis-data": {
      "type": "streamableHttp",
      "url": "https://foxapis.com/mcp/data",
      "headers": {
        "Authorization": "Bearer YOUR_KEY"
      },
      "disabled": false,
      "autoApprove": []
    }
  }
}

Cline's docs say that leaving type out selects the older SSE transport, so keep type.

Zed

Where it goes: settings.json (Zed: open settings). The client's own page on remote servers is its MCP documentation.

{
  "context_servers": {
    "foxapis-data": {
      "url": "https://foxapis.com/mcp/data",
      "headers": {
        "Authorization": "Bearer YOUR_KEY"
      }
    }
  }
}

n8n

Where it goes: an MCP Client Tool node in a workflow. The client's own page on remote servers is its MCP documentation.

Endpoint: https://foxapis.com/mcp/data
Server transport: HTTP Streamable
Authentication: Header Auth
  Name: Authorization
  Value: Bearer YOUR_KEY

Not run by us: the fields are the ones n8n's MCP Client Tool documents. The server speaks Streamable HTTP.

Which address to pick

A client lists every tool the address carries, and the assistant has to read that list before it chooses one. The all-sources address is the simplest start; a single-source address (for example the PubMed one) keeps the list to the tools you actually want and so keeps the assistant's choice easy. The ?source= form is for two or three sources that belong together, such as papers and trials.

The people and company research tools (dossiers, comparisons, enrichment) are not on this data address. They live on foxapis.com/mcp, which you add the same way with that address in place of this one. Both can be added side by side in the same client under different names.

To change the address later, edit the one line in the client's settings file or settings screen and restart the client's MCP connection. To remove the server, delete its entry from the same file or screen.

Claude Desktop and ChatGPT

Not covered by a snippet. Their custom-connector screens ask for sign-in (OAuth) or for no authentication, and this server takes a bearer key in a header, so it works best in the clients above. We have not tested the server in either, and a page that said otherwise would be a guess.

Check that it works

  1. Ask the client to list the server's tools. This needs no key; if the list comes back, the address and transport are right.
  2. Give it one of the example prompts from a data-source page. A first call that returns data and a line saying how many credits it used means the key is right too.
  3. If you see 401, the key is missing or mistyped; if you see 402, the account is out of credits. Both, and every other status, are explained on errors and limits, and a call that fails is never charged.
  4. Keep the key out of any file you share or commit: the snippets use YOUR_KEY as a placeholder on purpose.

Start with 1,000 credits, no card. They arrive once you confirm your email and expire 90 days after they are added; credits you buy never expire.

Start with 1,000 credits

Related: Data-source MCP servers · The MCP server · Errors and limits