Cursor

Cursor connects through mcp-remote and authenticates with your API key in the X-API-Key header, the same way Claude Code does. Node.js is required.

Open the MCP settings

Go to Cursor Settings → Tools & Integrations → MCP and click Add Custom MCP. Cursor opens an mcp.json file: .cursor/mcp.json in the project for a project-level server, or ~/.cursor/mcp.json for all projects.

Add the Pipecorn server

Paste the following, replacing YOUR-API-KEY with your Pipecorn API key:

{
  "mcpServers": {
    "pipecorn": {
      "command": "npx",
      "args": [
        "mcp-remote",
        "https://mcp.pipecorn.com/mcp",
        "--header",
        "X-API-Key:${API_KEY}"
      ],
      "env": {
        "API_KEY": "YOUR-API-KEY"
      }
    }
  }
}

Check the connection

Back in the MCP settings, the Pipecorn server should show a green status and list its tools. In chat, ask for something like “find the head of sales at Pipecorn” to try it.

To use a workspace API key instead, replace X-API-Key with X-Workspace-Key in args. Never send the key in an Authorization header: the server only accepts an OAuth access token there.

Keep the key out of version control. Prefer the user-level ~/.cursor/mcp.json, or add .cursor/mcp.json to .gitignore when the server is configured per project.

Overview

Setup

Reference