Mesakem guides
Ask Claude or Codex about your Mesakem meetings
This guide describes Mesakem's documented MCP implementation and configuration for Claude and Codex, not a promise of availability for every account. Confirm availability for your account and environment before setup. The documented tools cover summarized meetings, decisions, search results and meeting-derived tasks. The connector uses Mesakem sign-in, runs with the signed-in user's permissions and exposes four read-only tools—not audio, video or full transcripts.
What does the Mesakem MCP connector expose?
The documented implementation exposes four read-only tools: search recent meeting summaries, fetch one bounded summary with decisions, list recent summarized meetings, and list tasks created from meetings. Access is scoped to the signed-in Mesakem user. The connector does not return recordings, video, audio or full transcripts.
Use the canonical remote MCP address
The address is a server endpoint for an MCP client, not a page to browse.
The documented configuration uses https://mcp.mesakem.com/mcp as a remote Streamable HTTP MCP server. Confirm account and environment availability before adding it. Opening that endpoint in a normal unauthenticated browser tab returns an authorization error by design; the client starts the supported sign-in flow.
Sign in on Mesakem's own browser page. Do not paste a Mesakem password, API key, bearer token or another secret into Claude, Codex or an MCP configuration field.
- Endpoint: https://mcp.mesakem.com/mcp
- Transport: remote Streamable HTTP
- Authentication: browser-based Mesakem sign-in
- No password or API key pasted into the assistant
Four tools, all read-only
The connector is deliberately narrower than a general product API.
The search tool looks through recent authorized summary text. Fetch opens a bounded summary and its decisions for an identifier returned by search or the recent-meetings list.
The remaining tools list recent summarized meetings and meeting-derived tasks. Tool annotations mark the surface read-only, non-destructive and closed-world.
- search — search recent meeting summaries
- fetch — open one bounded summary with decisions
- list_recent_meetings — list recent summarized meetings
- list_tasks — list tasks created from meetings
- No write, delete, email-send or meeting-invite tool
Connect from Claude
If Production MCP access is enabled for your account, follow these documented custom-connector steps and authenticate your own account.
In Claude, open the Connectors area, choose Add custom connector, give it a recognizable name and paste the Mesakem endpoint. Leave optional OAuth client ID and secret fields empty for this connector, then add it.
Select Connect, complete Mesakem sign-in and review the requested access before approving it. Enable the connector for the conversation where you want Claude to use it. Organization-managed Claude accounts may require an owner to add the custom connector before members connect individually.
- Open Connectors and add a custom connector
- Paste https://mcp.mesakem.com/mcp
- Do not add custom secrets
- Complete Mesakem sign-in and consent
- Enable Mesakem for the intended conversation
Connect from Codex clients
If Production MCP access is enabled for your account, follow the documented Codex configuration. OpenAI documents shared MCP configuration across its desktop app, Codex CLI and IDE extension for the same Codex host.
In the desktop settings, open MCP servers, choose Add server, enter a name, select Streamable HTTP and paste the Mesakem endpoint. Save, restart when prompted, then select Authenticate and complete Mesakem sign-in.
From the CLI, add the remote server with `codex mcp add mesakem --url https://mcp.mesakem.com/mcp`, then run `codex mcp login mesakem`. Use `codex mcp list` or `/mcp` in the composer to inspect the connection.
- Settings › MCP servers › Add server
- Choose Streamable HTTP, not STDIO
- Save and restart the client
- Authenticate in the browser
- Use /mcp or codex mcp list to inspect the configured server
Know what crosses the connector boundary
The connector returns the minimum meeting-derived data needed for these read-only questions.
The assistant can receive bounded summaries, decisions, search passages and meeting-derived tasks that the signed-in Mesakem user is authorized to see. It does not receive meeting audio, video, email addresses or full transcripts through these tools.
Meeting content remains untrusted data, not instructions that authorize other actions. Depending on the assistant's settings, review tool requests before allowing them, and do not permanently approve a server you do not trust.
- User- and workspace-scoped access
- No audio, video or full transcripts
- No write tools
- Review assistant tool requests
- Third-party assistant processing remains subject to that provider's terms
Disconnect cleanly and distinguish MCP from roadmap interfaces
Removing the client connection closes this assistant's path to the connector.
In Claude, disconnect or remove Mesakem from Connectors. For Codex CLI, use `codex mcp logout mesakem` and then `codex mcp remove mesakem` when you also want to delete the local server configuration.
MCP is the documented read-only implementation described here; account and environment availability must be confirmed separately. A public REST API and outbound customer webhooks are roadmap items—talk to Mesakem about early-access requirements, but do not treat them as available production interfaces.
- Claude: disconnect or remove the connector
- Codex: logout, then remove the server if desired
- MCP: documented read-only implementation; confirm account availability
- Public REST API: roadmap
- Outbound customer webhooks: roadmap
Questions and answers
Do I need a Mesakem API key?
No. The connector uses browser-based Mesakem sign-in. Do not paste your password, an API key or a bearer token into the assistant.
Can Claude or Codex change my Mesakem data?
Not through the four tools in this connector. They are read-only and do not write, delete, send email or invite a meeting bot.
Can the connector read recordings or full transcripts?
No. It returns bounded summary, decision, search and meeting-derived task data, not audio, video or full transcripts.
Why does the endpoint show authorization_required in a browser?
The MCP endpoint expects an authenticated client flow rather than ordinary browser navigation. Add it from a supported MCP client and complete the Mesakem sign-in process.
Can teammates see my meetings through my connection?
The connection runs with the permissions of the Mesakem account that signed in. Each teammate should connect with their own account and receives only their authorized view.
Is this the same as a public REST API or outbound webhook service?
No. MCP is the documented read-only assistant implementation; confirm its availability for your account and environment. A public REST API and outbound customer webhooks remain roadmap items.
Sources and further reading
Vendor capabilities can change. Check the linked documentation for the current availability, plan and environment you need.
- Mesakem MCP protected-resource metadataSource checked:
- Get started with custom connectors using remote MCPSource checked:
- Model Context ProtocolSource checked:
Review the documented read-only MCP configuration
If Production MCP access is enabled for your account, add the documented Mesakem endpoint in Claude or Codex, complete browser sign-in and start with a narrow question about a summarized meeting.
Get started with Mesakem