MCP for agents

Mico's MCP server is cloud-hosted: it reads your synced meetings from Mico's servers, so an agent can use it from any machine — including ones where the desktop app is not installed. It requires a plan that includes the MCP server (Flow), and the check happens server-side on every request.

Connect a client

In the desktop app, open Settings → Developers → MCP and create a personal access token. The token is shown once; only its hash is stored.
Copy the connection command shown next to it. For Claude Code it looks like:

claude mcp add --transport http mico \
  https://<project>.supabase.co/functions/v1/mcp \
  --header "Authorization: Bearer mico_pat_..."

Any MCP client that speaks Streamable HTTP and lets you set an Authorization header works the same way.

Connect from claude.ai

The normal Claude client (web and desktop) connects through OAuth instead of a static header:

In claude.ai, go to Settings → Connectors → Add custom connector and paste the same endpoint URL. No client ID or secret: the server supports dynamic registration.
Claude opens Mico's authorization page. Paste a personal access token (created in Settings → Developers → MCP) once to prove it is you.
Done. Claude holds its own short-lived credentials from then on, and they refresh automatically.

The connection stays tied to the token you pasted. To disconnect Claude, revoke that token in Settings → Developers → MCP.

Tools

The server is read-only — every tool is idempotent and performs no writes:

Tool	What it returns
`list_meetings`	Recent meetings, filterable by title fragment or series, paginated
`get_meeting`	One meeting with its note, summaries, participants and action items
`get_meeting_transcript`	Transcript pages of up to 500 words; follow `pagination.next_offset`
`get_recurring_meeting_history`	The meetings in the same recurring series
`search_meetings`	Meetings whose title or summary contains a text
`list_pending_action_items`	Open action items across meetings, with their meeting
`search_shared_notes`	Notes other people share with you or your teams, by words they contain
`get_shared_note`	The text of one shared note. Notes and summaries only, never transcripts

The first four are the same tools, with the same schemas, that the retired local server exposed — an agent that learned them needs no changes.

Tokens

Tokens are managed in Settings → Developers → MCP: create as many as you need (one per agent is a good habit), see when each was last used, and revoke any of them instantly. A revoked token stops working on the next request, and so does every OAuth connection authorized with it.

See the MCP reference for every parameter and error.

What happened to the local server?

Earlier builds shipped a local MCP server (mico mcp) that read the desktop app's local database over stdio. It was retired in favor of the cloud server:

The local server only worked on a machine with the desktop app and its database — agents anywhere else saw nothing.
Your meetings already live, with row-level security, on Mico's servers, which is exactly what a hosted MCP endpoint can read without keeping a second copy anywhere.

The mico CLI is unaffected: it remains local and offline, reading the desktop app's database. See CLI for agents.