Mesakem guides
Ask Claude, Codex or Grok about your Mesakem meetings
This guide describes Mesakem's documented MCP implementation and configuration for Claude, Codex and Grok, not a promise of availability for every account. Confirm availability for your account and environment before setup. With full read access, the documented tools cover what your Mesakem dashboard shows you: meetings including unsummarized ones, summaries, full transcripts with speakers, participants, your tasks from every source, full-history search and rooms, plus your own Notepad notes and summary (yours only). The connector uses Mesakem sign-in, runs with the signed-in user's permissions and stays read-only—it never returns audio or video. Connections made before full read access was offered keep the four summary-and-task tools until the user disconnects and connects again once, choosing full read access on the consent screen.
What does the Mesakem MCP connector expose?
Every connection gets four read-only summary-and-task tools: search, fetch, list_recent_meetings and list_tasks. A connection that approves full read access also gets list_meetings, get_meeting, get_meeting_transcript, get_meeting_participants, list_my_tasks, get_task, search_meetings, list_rooms and get_room—the same information the signed-in Mesakem user's dashboard shows in the chosen workspace. Every tool is read-only: nothing is written, deleted or sent, and recordings, video and audio are not returned. Existing connections reconnect once to get full read access.
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, Grok 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
Read-only tools, up to what your dashboard shows
Every connection starts with four summary tools; full read access adds the rest after an explicit consent.
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.
A connection that approved full read access also lists and opens meetings (including unsummarized ones and your own upcoming calendar meetings), reads a meeting's full transcript with speaker labels and its participants, lists and opens your tasks from every source and searches your whole meeting history, and lists and opens the rooms you can access. All of it is limited to what your own dashboard shows you.
- 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
- list_meetings — list your meetings, including unsummarized ones and upcoming calendar meetings
- get_meeting — open one meeting with its current summary, and your own Notepad notes and summary for it (yours only)
- get_meeting_transcript — a meeting's full transcript, by speaker
- get_meeting_participants — a meeting's invitees and speakers
- list_my_tasks — your tasks from every source
- get_task — one task with its description and full checklist
- search_meetings — search your whole meeting history
- list_rooms — the rooms you can open
- get_room — one room and the meetings in it
- 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, in the browser or the desktop app, 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
Connect from Grok on grok.com
If Production MCP access is enabled for your account, follow these documented custom-connector steps at grok.com in a browser.
At grok.com, open Plugins in the sidebar (grok.com/connectors), choose New Connector, then Custom. Enter a recognizable name such as Mesakem, paste https://mcp.mesakem.com/mcp into Server URL and select Add Connector. The form has no key, password or header fields; Grok finds Mesakem sign-in by itself.
Complete Mesakem sign-in and review the requested access in the popup window before approving it. Mesakem then appears under Connected. In a chat, type @ and pick Mesakem, or ask about your meetings and let Grok use the connector. On Grok Business or Enterprise, a team admin first provisions the connector in xAI's cloud console.
- Plugins › New Connector › Custom
- Server URL: https://mcp.mesakem.com/mcp
- No key, password or header fields
- Complete Mesakem sign-in in the popup
- Type @ in a chat and pick Mesakem
Know what crosses the connector boundary
The connector returns only what the signed-in user can already see, and only for reading.
With full read access, the assistant can receive what the signed-in Mesakem user's dashboard shows in the chosen workspace: meetings, summaries, decisions, full transcripts, participants (including invitee email addresses), tasks and rooms. It never receives meeting audio or video. A summaries-and-tasks-only connection receives bounded summaries, decisions, search passages and meeting-derived tasks only.
With the Notepad included, opening a meeting also returns your own Notepad notes and Notepad summary for it: only the signed-in user's own, never a teammate's or an admin's, never through a share link, and never the Notepad's live transcript.
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 or video; full transcripts only with full read access
- 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. In Grok, open Mesakem under Plugins › Connectors and select Disconnect.
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
- Grok: open the connector, then Disconnect
- 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, Codex or Grok change my Mesakem data?
No. Every tool in this connector is read-only; none writes, deletes, sends email or invites a meeting bot.
I connected before full read access. How do I get it?
Connections made before full read access was offered keep the four summary-and-task tools until the user disconnects and connects again once, choosing full read access on the consent screen. Until then the existing connection keeps working as before.
Can the connector read recordings or full transcripts?
Recordings, no: audio and video are never returned. Full transcripts, yes, with speaker labels, but only for a connection that approved full read access; a summaries-and-tasks-only connection does not receive 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:
- Grok connectorsSource checked:
Review the documented read-only MCP configuration
If Production MCP access is enabled for your account, add the documented Mesakem endpoint in Claude, Codex or Grok, complete browser sign-in and start with a narrow question about a summarized meeting.
Get started with Mesakem