The short overview
Transport
Streamable HTTP (MCP), stateless. Each endpoint handles both JSON-RPC and
server→client streaming.
Authentication
OAuth 2.1, discovered via RFC 9728. Your access token identifies your user and
organization. Which connectors and tools you can use is checked on the server on
every call.
Tools
You get the tools of the connectors your organization subscribes to. Calling them
also requires a seat assigned to your user, and on e-conomic and Uniconta your
access level can limit you to the read tools. Search Console, CVR, Dinero, Billy,
Ordrestyring and Business Central are read-only; e-conomic, Uniconta, Shopify,
HubSpot CMS, HubSpot Marketing Email, Meta Ads and LinkedIn Ads are read +
guardrailed write. See
Write tools & guardrails.
Hosting
Hosted in the EU (Frankfurt). The token your client sends is never forwarded to a
data source.
Endpoints
Each connector is its own named MCP server at its own URL. The aggregate/mcp is the
Consile Concierge: management tools only, no connector tools. The URLs are the same for
every customer, and your login decides what you can reach. You find them in the
portal on each connector’s page and under Konto.
<base> = a connector URL or /mcp):
Any other method returns
405 with Allow: GET, POST. Headers, statelessness and
limits are described under
Protocol notes.
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
gsc__top_queries against /mcp (the Concierge) returns Unknown tool. and never
reaches Search Console. Your access is re-checked on every call. Connector tools are
namespaced as <id>__<tool> (e.g. uniconta__get_account_balance,
meta-ads__create_campaign); the AI resolves these automatically. The system tool
connect_account (on every connector endpoint except CVR) and the Concierge tools
are not namespaced.Extra portals
If your organization has added more than one portal of a connector (for example a second e-conomic agreement), portal 2 and up are separate endpoints:https://mcp.consile.ai/<id>-<n>/mcp, e.g. https://mcp.consile.ai/economic-2/mcp.
Their tools are prefixed <id>-<n>__ (e.g. economic-2__list_customers), they have
their own metadata document at /.well-known/oauth-protected-resource/<id>-<n>/mcp,
and each uses only its own connected account. The portal shows each portal’s URL on the
connector page under Portaler. CVR and HubSpot Marketing Email have no extra
portals. A second Shopify store cannot be connected self-serve today; write to
support@consile.dk before you add one.
What this section covers
Connect an MCP client
From a custom client, Claude Code, an SDK or mcp-remote, plus the protocol notes.
Authentication
The OAuth flow at the protocol level, and how subscription, seat and access level
decide what you can call.
Write tools & guardrails
How the write-capable connectors behave: dry-run previews, the
confirm: true contract, the PAUSED/DRAFT defaults and per-user access levels.API reference: Google Search Console
All 7 read-only tools with parameters and examples.
API reference: CVR
The 5 read-only company-register lookups (companies, production units, owners and
management).
API reference: Uniconta
25 tools: 21 read (debtors, creditors, G/L, inventory, journals,
query), 4
guardrailed write (daily-journal lines, including posting).API reference: e-conomic
40 tools: 28 read, 12 guardrailed write (customers, invoice and credit-note drafts,
journal entries).
API reference: Dinero
The 52 read-only tools (accounts, invoices, contacts, vouchers, reports).
API reference: Billy
The 17 read-only accounting tools (invoices, bills, contacts, ledger, bank
payments).
API reference: Ordrestyring
The 9 read-only job-management tools (cases, hours, sales invoices, read-only
GraphQL).
API reference: Business Central
Early access: the 5 read-only tools served today (environments, companies, company
information, allow-listed OData queries and entity metadata).
API reference: Shopify
All 50 tools: 40 read, 10 guardrailed write (products, publishing, inventory).
API reference: HubSpot CMS
23 tools: 14 read, 9 guardrailed write (pages, blog, HubDB).
API reference: HubSpot Marketing Email
19 tools: 8 read, 11 guardrailed write (draft writes apply directly; sending
needs
confirm: true).API reference: Meta Ads
All 39 tools: 34 read, 5 guardrailed write.
API reference: LinkedIn Ads
All 64 tools: 45 read, 19 guardrailed write. 22 of them (Company Page, organic
posts, comments and reactions, member profile) are not available yet; calls to
them fail.
API reference: Concierge
The management tools on
/mcp.Errors & limits
HTTP and tool errors, rate limits, timeouts and row limits.
Usage & fair use
How tool calls are metered and where you see the numbers.