The short overview
Transport
Streamable HTTP (MCP). One endpoint for both JSON-RPC and server→client streaming.
Authentication
OAuth 2.1, discovered via RFC 9728. Your access token determines which account
and which connectors you can reach.
Tools
Read-only. You only get the tools your account is subscribed to.
Hosting
Hosted in the EU. The connector never sees a token your client sent.
Endpoints
Each connector is its own named MCP at its own URL; the aggregate/mcp is
the Consile Concierge (management tools only — no raw connector tools). Your
URLs are shown in the portal under Konto.
<base> = a connector URL or /mcp):
| Method & path | Purpose |
|---|---|
POST <base> | JSON-RPC: initialize, tools/list, tools/call, … |
GET <base> | Server→client SSE stream |
GET /.well-known/oauth-protected-resource/<id>/mcp | RFC 9728 metadata (public) for that connector — points to the authorization server |
405 with Allow: GET, POST.
Tenancy comes solely from your access token — never from the URL or from
tool arguments. A connector endpoint serves ONLY that connector’s tools; calling
top_queries against /mcp (the Concierge) will not reach Search Console. Your
access is re-checked on every call.What this section covers
Connect an MCP client
From a custom client or via an SDK / mcp-remote.
Authentication
The OAuth flow at the protocol level — discovery, token, scopes.
API reference: Google Search Console
All seven tools with parameters and examples.
API reference: e-conomic
The 18 read-only accounting tools.
API reference: Uniconta
The single ledger-balance tool.
API reference: Concierge
The six management tools on
/mcp.Errors & limits
JSON-RPC errors, row limits, data freshness.