Cursor and desktop MCP clients

Many developer tools read MCP configuration from JSON files. Keep tokens out of repositories and use OAuth where possible.

Cursor

For project-specific setup, Cursor documents .cursor/mcp.json. For a remote Sniffopotamus server, use the transport your Cursor version supports:

{
  "mcpServers": {
    "sniffopotamus": {
      "type": "http",
      "url": "https://www.sniffopotamus.com/mcp"
    }
  }
}

If your Cursor version expects SSE or another shape, follow the current Cursor MCP docs and keep the server URL the same.

Codex and other desktop clients

Use the client command or config file that adds a remote MCP server. The stable parts are:

• Name: sniffopotamus
• URL: https://www.sniffopotamus.com/mcp
• Start read-only.
• Reconnect after changing scopes.

Never commit secrets

Do not commit OAuth tokens, bearer tokens, or API keys in .cursor/mcp.json, .mcp.json, .codex/config.toml, or any shared repository.

Reference:

• Cursor MCP
• OpenAI Docs MCP setup pattern