Install for Cursor and Zed

Both Cursor and Zed support stdio MCP servers. The CueAPI server is a standard stdio process — configuration is effectively the same shape as Claude Desktop, just in each host's settings file.

Cursor

Config location

• macOS: ~/.cursor/mcp.json
• Windows: %USERPROFILE%\.cursor\mcp.json
• Linux: ~/.cursor/mcp.json

Or via Settings → Features → Model Context Protocol.

Config

{
  "mcpServers": {
    "cueapi": {
      "command": "npx",
      "args": ["-y", "@cueapi/mcp"],
      "env": {
        "CUEAPI_API_KEY": "cue_sk_your_key_here"
      }
    }
  }
}

Restart Cursor. The CueAPI tools appear in the Composer tool picker.

Zed

Zed registers MCP servers under context_servers in settings.json:

• macOS: ~/Library/Application Support/Zed/settings.json
• Linux: ~/.config/zed/settings.json

Config

{
  "context_servers": {
    "cueapi": {
      "command": {
        "path": "npx",
        "args": ["-y", "@cueapi/mcp"],
        "env": {
          "CUEAPI_API_KEY": "cue_sk_your_key_here"
        }
      }
    }
  }
}

Restart Zed. CueAPI tools become available through the assistant panel.

Self-hosted CueAPI

Add CUEAPI_BASE_URL next to CUEAPI_API_KEY in the env block for either host.

Other MCP hosts

Any host that supports the stdio MCP transport can run @cueapi/mcp. The essentials are always the same:

1. Spawn npx -y @cueapi/mcp (or cueapi-mcp if installed globally).
2. Pass CUEAPI_API_KEY in the subprocess environment.
3. Optionally pass CUEAPI_BASE_URL for self-hosted deployments.

Verify

Ask the agent to list your cues. It should call cueapi_list_cues and return results.

Scope

MCP tools inherit whatever the API key is allowed to do. See API key scope.