Connect an MCP client

Any MCP-compatible client can connect to Consile. The client just needs to speak Streamable HTTP and OAuth. Everything else is handled automatically via standard MCP authorization (see Authentication).

If you use Claude or ChatGPT, use the consumer flow instead: Connect Claude. This is for your own clients.

Option 1: an MCP-aware client

Clients that already speak MCP (e.g. desktop AI apps with custom connectors) only need a connector’s URL from the portal. Each connector is its own endpoint, and /mcp is the Concierge. They discover the authorization server themselves, take you through login, and store your token.

https://mcp.consile.ai/gsc/mcp

Option 2: mcp-remote (stdio → remote bridge)

Clients that can only run local stdio servers can bridge to Consile with mcp-remote. It opens the browser for OAuth the first time and caches your token:

{
  "mcpServers": {
    "consile": {
      "command": "npx",
      "args": ["-y", "mcp-remote", "https://mcp.consile.ai/gsc/mcp"]
    }
  }
}

Option 3: programmatically via an MCP SDK

Use an official MCP SDK with a Streamable HTTP transport and an OAuth provider. Once connected, the flow is the standard MCP handshake:

initialize

Negotiate protocol version and capabilities.

tools/list

Fetch the tools your account can access (depends on subscription).

tools/call

Call a tool with its arguments. See the API reference.

Example: raw JSON-RPC

A tools/call request over POST /gsc/mcp (abbreviated; the Authorization: Bearer <token> header is omitted here). Note gsc__top_queries is a GSC tool, so it goes to the GSC endpoint, not the aggregate /mcp. Tool names on a per-connector endpoint are namespaced connector__tool:

{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "gsc__top_queries",
    "arguments": {
      "siteUrl": "sc-domain:example.com",
      "startDate": "2026-05-01",
      "endDate": "2026-05-28",
      "limit": 10
    }
  }
}

{
  "siteUrl": "sc-domain:example.com",
  "startDate": "2026-05-01",
  "endDate": "2026-05-28",
  "queries": [
    { "query": "example keyword", "clicks": 421, "impressions": 9120, "ctr": 0.046, "position": 7.8 }
  ]
}

If you call a connector endpoint without a valid token, you get 401 with a WWW-Authenticate header pointing to the discovery document. That’s the normal starting point for OAuth. See Authentication.

​Option 1: an MCP-aware client

​Option 2: mcp-remote (stdio → remote bridge)

​Option 3: programmatically via an MCP SDK

​Example: raw JSON-RPC

Option 1: an MCP-aware client

Option 2: mcp-remote (stdio → remote bridge)

Option 3: programmatically via an MCP SDK

Example: raw JSON-RPC