Organiq

Connect Organiq to Cursor and other MCP clients

Before you start: have an Organiq account with at least one Search Console property connected. Sign in with Google at https://app.organiqgeo.com, click "Connect Search Console" (read-only access) and wait for the first sync. The connector only completes authorization for accounts with a property.

Cursor

In Settings → MCP → Add new MCP server, or in the project's .cursor/mcp.json (or ~/.cursor/mcp.json):

{
  "mcpServers": {
    "organiq": { "url": "https://organiqgeo.com/mcp" }
  }
}

Cursor opens the OAuth flow in the browser the first time. If you prefer a fixed key:

{
  "mcpServers": {
    "organiq": { "url": "https://organiqgeo.com/mcp", "headers": { "Authorization": "Bearer gy_live_YOUR_KEY" } }
  }
}

Claude Desktop (config file) and clients without OAuth

Use the mcp-remote bridge with the API key (the value sits in clear text in the file; treat it as a secret):

{
  "mcpServers": {
    "organiq": {
      "command": "npx",
      "args": ["-y", "mcp-remote", "https://organiqgeo.com/mcp", "--header", "Authorization:Bearer gy_live_YOUR_KEY"]
    }
  }
}

On Claude Desktop the recommended path is the custom connector with OAuth (Claude guide); mcp-remote is only for clients that do not implement OAuth.

VS Code, Windsurf, Gemini CLI, Codex

Any client that speaks Streamable HTTP works with the same URL; if it supports OAuth, no header is needed. With an API key: header Authorization: Bearer gy_live_….

Inspector (developers)

npx @modelcontextprotocol/inspector --cli https://organiqgeo.com/mcp --transport http --method tools/list
npx @modelcontextprotocol/inspector --cli https://organiqgeo.com/mcp --transport http --method tools/call --tool-name get_capabilities

Example prompts