MCP

What this is

MCP (Model Context Protocol) is the standard AI agents use to connect directly to external tools. If your agent or IDE speaks MCP, it can talk to Redpine Connect the moment you add one server: no API integration to write, no request shapes to learn.

Once connected, your agent can search Redpine's collections and reach every integration (news mentions, aviation data, and more) on its own: it discovers what's available and figures out how to call it. You don't write any code, and neither does it.

If you're building your own integration instead of using an existing client, see the REST API quickstart. Everything below is for connecting an agent.

The short version

https://api.redpine.ai/mcp

That's the whole server. Every client below just needs this URL. Most clients open your browser once to approve access. No key to copy.

Connect your client

Pick yours: each links straight to its instructions below.

Claude Code

Codex

Cursor

Redpine CLI

Claude Desktop

ChatGPT

Windsurf

Lovable

Antigravity

Claude Code

Run this in your terminal, then approve Redpine in the browser it opens:

claude mcp add --transport http redpine https://api.redpine.ai/mcp

Codex

Register the server, then authorize it: the second command opens your browser:

codex mcp add redpine --url https://api.redpine.ai/mcp
codex mcp login redpine

Cursor

Open ~/.cursor/mcp.json (or .cursor/mcp.json in your project), add this, and save. Then click Login on the Redpine server in Cursor's MCP settings:

{
  "mcpServers": {
    "redpine": {
      "url": "https://api.redpine.ai/mcp"
    }
  }
}

Prefer a static key over the browser login? Create one from your API Keys page and use this instead:

{
  "mcpServers": {
    "redpine": {
      "url": "https://api.redpine.ai/mcp",
      "headers": {
        "X-API-Key": "YOUR_API_KEY"
      }
    }
  }
}

Redpine CLI

brew install redpine-ai/tap/connect-cli
redpine auth login

Claude Desktop

1. Open Claude Desktop → Settings → Connectors
2. Click Add custom connector at the bottom-left
3. Set the name to "Redpine" and paste this URL:

   https://api.redpine.ai/mcp

4. Click Add, then click Connect

ChatGPT

1. Open ChatGPT → Settings → Apps/Connectors
2. Enable Developer Mode in advanced settings
3. Click Create App
4. Set the name to "Redpine" and paste this URL:

   https://api.redpine.ai/mcp

5. Select OAuth as the authentication method
6. Click Connect

Windsurf

Open Windsurf → Settings → MCP, and add a new server with this URL:

https://api.redpine.ai/mcp

Lovable

1. Go to Connectors → All, then scroll to Custom MCP
2. Name it "Redpine" and add this URL:

   https://api.redpine.ai/mcp

3. Click OAuth, press Add & Continue, then choose your organization

Antigravity

Antigravity doesn't support the browser login, so this one needs a key. Create one from your API Keys page first.

1. Open Antigravity
2. In the Agent panel, click the "more options" menu → MCP Servers → Manage MCP Servers
3. Click View raw config
4. Paste this and save:

   {
     "mcpServers": {
       "redpine": {
         "serverUrl": "https://api.redpine.ai/mcp",
         "headers": {
           "X-API-Key": "YOUR_API_KEY"
         }
       }
     }
   }

Something else

Any MCP client that supports a remote HTTP server works, even if it's not listed above: this is a standard Streamable HTTP endpoint. Give it the URL:

https://api.redpine.ai/mcp

If your client asks how to authenticate, it almost certainly supports OAuth discovery and will figure it out on its own from that URL alone. If it needs manual configuration, see Authenticating without OAuth below.

What your agent can do once connected

You don't need to tell your agent which tool to use. Just ask a question, like "find me recent news mentions of Nvidia" or "search my documents for adverse event reports," and it works out which integration and tool applies, then calls it.

Under the hood, this happens through three tools every client sees: find-tools looks up what's available by keyword, inspect-tool gets the exact parameters for one, and call-tool runs it. Your agent chains these on its own; you never call them directly unless you're scripting against MCP yourself.

Browse everything your organization has access to (full tool list, parameters, and pricing) on the Integrations page.

Search over MCP

Search maps onto the same three REST behaviours as everywhere else, but preview and confirm are their own top-level tools while search itself isn't: it's reached the same way any integration tool is, through find-tools then call-tool, not as a separate named tool most clients see directly.

Your agent picks between these the same way it picks any tool: given a task, not a command. Ask it to search, and it finds and calls search; ask it to check what something would cost first, and it reaches for preview then confirm directly. Parameters and response shapes match their REST counterparts exactly. See Search and Preview and unlock for the full field reference. /search/assisted's agentic loop isn't exposed as a fourth MCP tool: an MCP-connected agent already plans its own multi-step searches using search, so there's no separate tool for it. To search a specific collection by name, your agent finds it the same way it finds any other detail: by calling list_collections, discovered the same way search is.

Sandbox keys and MCP

A sandbox key works over MCP for search (search, preview, and confirm all return fixture results, same as the REST API). It does not work for integration tools reached through call-tool: those reach real third-party services, so a sandbox key gets 403 SANDBOX_UNSUPPORTED_ENDPOINT instead. Use a live key to try aviation, media, or any other integration tool.

Authenticating without OAuth

Most clients above use OAuth: your browser opens once, you approve Redpine for your organization, and the client is done. No key ever touches its config file. This is what "Connect" or "Login" buttons trigger.

If your client doesn't support that flow, or you're scripting against MCP directly, send an API key instead:

X-API-Key: sk_live_YOUR_API_KEY

Everything else about the request is identical either way. Create a key from your API Keys page. See Authentication for the two kinds and what each does.

Managing connections

See and revoke connected clients from your organization's Connections page in the dashboard. Revoking there ends that client's access immediately. No restart needed on your end.

Troubleshooting

Anything else, see Errors for the full status code reference.