Connect Cursor or another client

Updated Oct 20262 min read

filtrat's MCP server is a standard remote server, so any client that supports MCP over HTTP can use it. You need two things: the server URL and an API key.

Connection settings

SettingValue
Server URLhttps://mcp.filtrat.io/mcp
TransportStreamable HTTP
Auth headerAuthorization: Bearer ak_… (your API key)

Create the key on API → MCP in the app. Pick Cursor there and the page fills in the snippet below with your key.

Cursor

  1. Open (or create) the MCP config file:
    • for every project: ~/.cursor/mcp.json in your home folder;
    • for one project only: .cursor/mcp.json in that project's folder.
  2. Add filtrat under mcpServers, with your key in place of YOUR_API_KEY:
~/.cursor/mcp.json
{
  "mcpServers": {
    "filtrat": {
      "url": "https://mcp.filtrat.io/mcp",
      "headers": {
        "Authorization": "Bearer YOUR_API_KEY"
      }
    }
  }
}
  1. Save the file. In Cursor's settings, open the MCP section and check that filtrat is listed and enabled. Restart Cursor if it doesn't show up.
Warning

A project's .cursor/mcp.json is easy to commit by mistake. If you use a project file, add it to .gitignore, or use the global file in your home folder instead.

Claude Code

Terminal
claude mcp add --transport http filtrat https://mcp.filtrat.io/mcp \
  --header "Authorization: Bearer YOUR_API_KEY"

Claude Desktop

Claude Desktop connects through the mcp-remote helper. See Connect filtrat to Claude (MCP) for the config.

Any other client

Most clients accept one of these two forms. Use the first if your client supports remote servers with headers:

Remote server with a header
{
  "mcpServers": {
    "filtrat": {
      "url": "https://mcp.filtrat.io/mcp",
      "headers": {
        "Authorization": "Bearer YOUR_API_KEY"
      }
    }
  }
}

If your client only starts local servers (a command and args), use mcp-remote to bridge to filtrat. It needs Node.js 18 or newer:

Local bridge
{
  "mcpServers": {
    "filtrat": {
      "command": "npx",
      "args": [
        "-y",
        "mcp-remote",
        "https://mcp.filtrat.io/mcp",
        "--header",
        "Authorization: Bearer YOUR_API_KEY"
      ]
    }
  }
}

The exact file name and location depend on the client: check its documentation for where MCP servers are configured.

Check it works

Ask the assistant "How many filtrat credits do I have?". It should call get_credits and answer with your balance. That call is free.

One key per client

Create a separate key for each client or computer, named after it (Cursor laptop, Claude Desktop). If you stop using one, or a config file is shared by mistake, revoke just that key on API → API keys.

Troubleshooting

  • The server shows as failed or disconnected. Check the URL ends in /mcp and the header reads Bearer, a space, then the key.
  • "Not authenticated". The key is wrong, revoked or incomplete, or your account's email isn't confirmed yet. See Authentication.
  • Tools are missing or old. Restart the client so it reloads the tool list.
Was this helpful?
Still stuck?

Email support@filtrat.io with the list or job name and what you expected to see.

Contact support
MYKHAILO BURIAK · NIP: 8982334042 · REGON: 544788490 · ul. Mieszczańska 18/40, 50-201 Wrocław, Poland© 2026 filtrat.io