Install

Four clients, one endpoint shape.

Both connectors are stateless MCP servers over Streamable HTTP with bearer-key auth. Anything that can POST JSON with a header can use them. Endpoints: https://gsc-mcp.bloggerclinic.com/mcp and https://bing-mcp.bloggerclinic.com/mcp. Your key (smcp_…) is issued from the dashboard and shown exactly once.

Claude Code

terminal

claude mcp add --transport http gsc https://gsc-mcp.bloggerclinic.com/mcp \
  --header "Authorization: Bearer smcp_your_key"

# verify
claude mcp list

Claude (web) — custom connector

Settings → Connectors → Add custom connector.
URL: https://gsc-mcp.bloggerclinic.com/mcp
Where your plan supports custom headers, add Authorization: Bearer smcp_your_key. Claude web requires connectors to be reachable over HTTPS — both endpoints are.

Claude Desktop

Desktop speaks stdio to local servers, so the remote endpoint is bridged with mcp-remote (needs Node 20+):

claude_desktop_config.json

{
  "mcpServers": {
    "gsc": {
      "command": "npx",
      "args": [
        "-y", "mcp-remote", "https://gsc-mcp.bloggerclinic.com/mcp",
        "--header", "Authorization: Bearer smcp_your_key"
      ]
    }
  }
}

Settings → Developer → Edit Config, paste, restart Claude Desktop.

Any MCP client

Raw protocol, if you are wiring your own client or checking with curl:

curl

curl -s https://gsc-mcp.bloggerclinic.com/mcp \
  -H "Authorization: Bearer smcp_your_key" \
  -H "Content-Type: application/json" \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/list"}'

initialize, tools/list, tools/call and ping are implemented; there is no SSE stream (GET returns 405) — the server never pushes.

First run

GSC: run gsc_setup with your OAuth client id + secret (create one here), open the returned URL, approve, then gsc_auth_status.
Bing: run bing_setup with your API key, then bing_list_sites.
Ask something real: “pages with impressions but zero clicks in the last 28 days, worst CTR first.”