Grain MCP server

What the model can do

Grain meeting recordings: list and search recordings, read one with its AI summary and action items, read its transcript, list teams, meeting types, users and playlists; can tag, untag or rename a recording, share it with a colleague or team, cut a clip, and create, change, fill or delete a playlist.

Reads

• grain_recordingsGrain recordings the token can see, newest as Grain returns them: title, start, length, source, meeting type, who recorded, teams…
• grain_recordingOne Grain recording in full: the details from grain_recordings plus Grain's AI summary, its AI action items (with assignee and status)…
• grain_transcriptThe transcript of a Grain recording as speaker-labelled lines with minute:second offsets, cut at max_chars.
• grain_teamsGrain teams and meeting types, with the ids grain_recordings filters by.
• grain_usersPeople in the Grain workspace: user id, name and email.
• grain_playlistsGrain playlists, newest first: id, title, who can open the link (restricted, workspace or public) and when made.

Acts, when you ask

These change something in Grain. The model is told to use them only when you ask for exactly that, and each one is granted by name: per team on a shared connection, by the owner on a personal one.

• grain_add_tagAdds a tag to a Grain recording (letters and numbers joined by dashes, such as follow-up or q4-renewal).
• grain_remove_tagRemoves one tag from a Grain recording.
• grain_rename_recordingChanges a Grain recording's title, replacing the old one, for everyone who can see it.
• grain_share_recording_with_userGives one Grain workspace user access to a recording, its transcript and summary.
• grain_share_recording_with_teamGives every member of a Grain team access to a recording, its transcript and summary.
• grain_create_clipCuts a clip (a Grain highlight) from a recording, from a start point for a length, with an optional title, and returns its share link.
• grain_delete_clipPermanently deletes a Grain clip; its share link stops working.
• grain_create_playlistCreates a Grain playlist with a title.
• grain_update_playlistRenames a Grain playlist or changes who can open its link: restricted, workspace, or public (anyone with the link, outside the company too…
• grain_add_recording_to_playlistPuts a recording into a Grain playlist, so everyone the playlist is open to can watch it (with a public playlist, anyone with its link).
• grain_delete_playlistPermanently deletes a Grain playlist; its link stops working, and the recordings in it are kept.

Connect it

First connect Grain on Dashboard → Connections, then add Memtro to your client once. The Grain tools appear alongside the tools of everything else you have connected; nothing is configured per connector.

claude plugin marketplace add memtro-org/claude-memtro
claude plugin install memtro@memtro --config api_key=sk-memtro-...

{
  "mcpServers": {
    "memtro": {
      "url": "https://platform.memtro.com/api/mcp",
      "headers": {
        "Authorization": "Bearer sk-memtro-..."
      }
    }
  }
}

{
  "mcp": {
    "memtro": {
      "type": "remote",
      "url": "https://platform.memtro.com/api/mcp",
      "headers": {
        "Authorization": "Bearer sk-memtro-..."
      }
    }
  }
}

Who may use it

The key identifies the person, and the server offers that person the tools they may use everywhere else in Memtro. A shared Grain connection is used by the teams an administrator granted it to, tool by tool, on the Permissions page; a personal connection is used by its owner alone, and its tools that act stay off until the owner allows them. See Teams and permissions and Connectors.

Ask it like this

• › What did we agree on yesterday's call with Northwind?
• › Which action items came out of the BigCo renewal meeting, and who owns them?
• › What did Dan say about pricing in the Acme demo?
• › Share the Brightwave Ltd kick-off recording with the onboarding team
• › Make a clip of the two minutes where BigCo's buyer talks about budget

Questions

Is this an official Grain MCP server?

No. It is Memtro's MCP server with Memtro's Grain connector behind it: the connector reads Grain through its API with the credentials you connect on Dashboard → Connections, and Grain publishes nothing here. The same endpoint carries every other system you connect and Memtro's memory tools.

What does it cost?

Nothing on top of Memtro. One price per organisation by its number of users, from $50 a month for up to 10 users after a 7-day free trial, with every connector, the MCP server, jobs and memory included. You bring your own model keys.

Can it change anything in Grain?

Only when you ask, and only what it has been granted: add a tag to a Grain recording; remove a tag from a Grain recording; rename a Grain recording; share a Grain recording with a workspace user; share a Grain recording with a Grain team; cut a clip (highlight) from a Grain recording; delete a Grain clip, permanently; create a Grain playlist; rename a Grain playlist or change who can open its link; add a recording to a Grain playlist; delete a Grain playlist, permanently (its recordings stay). Every other tool reads, searches or lists. An administrator grants each acting tool by name per team, and a personal connection acts only after its owner allows it.

Which clients work?

Any MCP client that speaks Streamable HTTP: Claude Code, Cursor, Claude Desktop, OpenCode, Codex, Zed, Windsurf, Cline and the Anthropic and OpenAI SDKs. There is no local process to run; the server is remote and authenticated with your key.

Other MCP servers · Email, calendar and chat

• AgentMail MCP server
• Gmail MCP server
• Google Calendar MCP server
• Slack MCP server
• Outlook Mail MCP server
• Outlook Calendar MCP server