Skip to main content
Concierca AI exposes its whole surface — agents, missions, data, knowledge, memory, skills, approvals, and the market-intelligence vertical — as a Model Context Protocol (MCP) server. Any MCP-capable client (Claude, ChatGPT, your own agent) connects once and can then read and act inside your workspace, always under the same tenant, scope, and governance rules as the app.
Every call runs server-side as the user who owns the key. Reads are filtered to what that user may see; writes need the matching per-tool grant. Secrets and OAuth flows never travel the model channel.

Endpoint

The main endpoint is what you connect in day-to-day use. The vertical endpoint is a standalone surface for the market-intelligence tools (vertical_*) — see Vertical.

Authentication

Two ways to connect, both from Settings → MCP Access:
  1. OAuth (recommended for a person) — connect the client and approve in the browser. A Company-Admin connect grants the full surface; a Member connect grants the read-only baseline. See Authentication for the scope model.
  2. API key — generate a key and pass it as a bearer token. Best for headless agents and the CLI.

Connect from Claude (Desktop / Code)

Add the server to your MCP client config, pointing at the main endpoint and your key:
For OAuth-capable clients, add the server by URL and complete the browser approval instead of pasting a key.

Connect from ChatGPT

Add a connector pointing at https://app.concierca.ch/api/mcp/v1 and authorize it.
ChatGPT loads the tool list only when a connector is created, and does not refresh it live. After your grants change (new tools, a reconnect), delete the connector and add it again to pick up the current tool set — re-login or “reload” is not enough.

First calls

Ground every session before acting:
  1. whoami — confirms identity, role, tenant, and the tools your key may use.
  2. get_context — returns your Operating Manual (the always-load governance + knowledge block).
  3. guardrails_get — the governance rules to honor; over MCP these are pull-only, so fetch them at session start.
Then use the resource tools — All Tools is the full 136-tool index; Data, Agents, Missions, Knowledge, Memory, Skills, Inbox, Approvals, Administration, Vertical. Naming, common parameters, errors, and limits are in Conventions.

Reconnecting

Reconnecting inherits your existing scopes and deactivates the previous key — you never lose access by reconnecting, and old keys stop working. Details in Authentication.