MCP setup guide

Connect zakki to MCP clients with OAuth

Authorize a client once, then review and revoke the grant from the connected apps page.

What AI can read

A connected client can list records, search them, and follow thread trails.

What AI can write

When the server supports the write tool, AI can add a new record with provenance and keep that usage on a separate meter from human-authored records.

AI comes to read

The flow is inverted on purpose: you capture first, and AI comes back later to read the right slice of context.

OAuth first

Authorize the client and keep the grant in one place

Open the consent screen, approve the requested scopes, and manage the connection later from connected apps.

https://api.zakki.app/mcp

OAuth replaces the manual token copy flow for supported clients.

Verify the connection

After approving OAuth, ask a prompt that should require a read from your recent records.

Example prompt

Summarize my recent records about MCP setup and point out anything I might have missed.

If the answer includes your recent records, the connection is working.

Client setup

Use a client that supports OAuth and remote HTTP MCP. The shared flow is always consent first, then manage the grant from connected apps.

Claude Desktop can open the zakki OAuth consent screen and then reuse the stored grant from connected apps.

Claude Code can use the same OAuth-backed remote HTTP flow when the client can launch a browser for consent.

OAuth-backed clients store the grant instead of a session token.

Cursor can point at the same OAuth consent page and then reuse the stored connection.

Manage the grant from connected apps after you approve it.

Any remote HTTP MCP client that supports OAuth can use the same consent and management flow.

The shared grant list lives in connected apps. The canonical transport is /mcp.

Manage grants from connected apps, then come back here if you need a quick reminder.