Spinach AI

Search Spinach recordings, summaries and action items.

Add to Agentman Studio

Opens Agent Studio, where connecting is one click. The connector URL below works in any MCP client.

Paste it into any MCP client. Setup docs

Resources

What the Spinach AI connector does

The Spinach AI MCP server connects a Spinach meeting archive to Claude, ChatGPT, Claude Code and any MCP-compatible agent. It searches recordings, opens one for its summary, decisions, action items and transcript, and — for the last seven days — hands the model the video itself. Access is scoped to the meetings the signed-in person is already authorized to see.

Verified connector

Listed by Anthropic as a partner connector in its Connectors Directory.

Connection checked by Agentman on .

Anthropic states this reflects the level of review a connector received, not a security audit.

Spinach AI tools (3)

  • TestConnection
  • Search
  • Fetch

Tool names from Anthropic's directory listing. This server requires sign-in, so we could not read tool descriptions or parameter schemas.

Limits

  • The scope set contradicts the permissions label. The authorization server advertises mcp:write alongside mcp:read, while Anthropic's directory labels the connector "Read only" and no Spinach documentation describes an MCP write tool. We could not resolve the disagreement without authenticating.
  • The tool listing is a floor. Anthropic's snapshot lists three tools. Spinach's troubleshooting names a fourth, list_collections, and states new tools reach existing connections automatically. Anything built from the listing alone will be incomplete.
  • The three listed names describe nothing. Search and Fetch are generic. What they cover comes from Spinach's capability prose, not from its tool names, and Spinach publishes no tool table.
  • No result cap is published. Spinach names no maximum result count, page size or pagination mechanism for search, where Fireflies documents 50 transcripts per query.
  • We could not verify tool behaviour ourselves. The endpoint returns 401 to an anonymous handshake, so no schemas and no safety annotations were readable to us.
  • The video path can be asked to read people. Spinach advertises asking an assistant who looked engaged or skeptical in a recording. That is model-generated inference about individuals' demeanour, reachable by an agent.
  • Video is limited to seven days over MCP, and text is not. Transcripts, summaries, action items and search carry no equivalent window, so letting recordings age out does not remove a meeting from an agent's reach.
  • The searchable corpus is incomplete for 5–10 minutes after connecting. Spinach documents an initial indexing delay during which searches can return nothing.
  • Grants last twelve months. Spinach documents raising the connection lifetime from 30 days to 12 months, so a connection persists far longer than a browser session and has to be revoked deliberately.
  • New tools reach existing connections without re-consent. Spinach states you never need to reconnect to pick up new capabilities, so the tool surface a grant covers can grow after you approved it.
  • Rate limits are unpublished. Spinach documents MCP tools as rate limited per hour but gives no figure, and says the ceiling can be raised on request.
  • How a Spinach permission is granted is undocumented. Spinach repeatedly ties MCP access to what you are authorized to see, but does not publish what creates that authorization — attendance, calendar invite, or collection membership.
  • The pause control is participant-operated and easy to miss. Anyone in the meeting can type pause in the chat, but Spinach documents no in-meeting announcement that the command exists, and states a misspelling will not work.
  • Some recordings are unreachable. Spinach states recordings not hosted directly by the meeting provider may not be reachable over MCP.
  • Prompts are unconfirmed. Anthropic's snapshot lists no prompt names, but the gated endpoint blocked our own check, so we cannot say whether the server serves any.
  • Meetings have a three-hour ceiling. Spinach's FAQ states meetings longer than three hours may not produce a summary at all, so the archive an agent searches can be missing a long session entirely.

Frequently asked questions

Whose meetings can the Spinach MCP connector read?

Only the meetings you are already authorized to see in Spinach. Spinach repeats that boundary for every client it documents: each member signs in with their own account, so the assistant sees one person's permitted archive rather than the workspace. Video access follows the same rule. Spinach documents no admin-wide or service-account credential that would widen the reach across a team.

Can the Spinach MCP server create Jira or Linear tickets?

No. Spinach documents ticket creation into Jira, Linear, Asana, Trello, ClickUp and Monday.com as a click in the emailed summary or the dashboard, after connecting a ticketing tool in settings. None of it is described as an MCP capability, and no documented Spinach MCP tool creates anything. An agent can draft a ticket, but a human still files it.

Why does the Spinach MCP server advertise an mcp:write scope?

Its authorization-server metadata lists both mcp:read and mcp:write, which we read live on 2026-08-19. Anthropic's directory labels the connector Read only, and no documented Spinach tool writes, so the two do not agree. A published write scope is a server capability, not proof of a write tool. Treat it as an unexplained gap rather than a hidden write path.

How many tools does the Spinach MCP server actually have?

Three in Anthropic's directory snapshot, but Spinach's own documentation names a fourth and describes more capabilities than four names could carry. Its troubleshooting section refers to newer tools by naming list_collections directly, and states new tools reach existing connections automatically. So the count moves, and the snapshot is a floor rather than a ceiling.

Do meeting participants know Spinach is recording?

Spinach joins as a named bot participant, and on Zoom and Teams somebody usually has to admit it from the waiting room. That is the notice mechanism: it appears in the attendee list the way a person does. Spinach also documents an off-the-record control — anyone in the meeting can type pause in the chat to stop recording, and resume to restart it.

How long does Spinach keep meeting recordings?

Video retention depends on your plan. Spinach documents one year for Trial, Pro and Business users and seven days for Free users, with Google Drive as the route to keep recordings past a year and custom retention available on request. Transcripts, summaries, action items and search are documented separately as not subject to the seven-day limit that applies to MCP video.

Does Spinach train AI models on my meeting data?

Spinach states plainly that your data is never used for AI model training, and names SOC 2 Type II, GDPR and HIPAA compliance alongside that claim on its security page. Its documentation draws no distinction between content read through MCP and content read in the app, so the same statement is the only one available for either path.

Can Claude analyze the video of a Spinach meeting, not just the transcript?

Yes, for recordings from the last seven days. Spinach documents this as deliberate — an agent working through your history cannot quietly pull every recording you have ever made. Video is opt-in per request, so ordinary transcript queries do not fetch it, and links point at the recording provider rather than direct storage URLs. Older meetings return a pointer to the web app.

Sources

  • MCP Configuration — https://help.spinach.ai/en/articles/11030670-mcp-configuration (fetched 2026-08-19; the directory's documentation URL, served by Intercom and requiring a browser user agent) · retrieved 2026-08-19
  • Claude MCP Integration — https://help.spinach.ai/en/articles/15304675-claude-mcp-integration (fetched 2026-08-19 as Markdown via the .md suffix) · retrieved 2026-08-19
  • Video Retention Period — https://help.spinach.ai/en/articles/10067927-video-retention-period (fetched 2026-08-19) · retrieved 2026-08-19
  • Off the Record — Pause Button — https://help.spinach.ai/en/articles/9034593-off-the-record-pause-button (fetched 2026-08-19) · retrieved 2026-08-19
  • Troubleshooting: Spinach Bot Not Joining or Rejoining Meetings — https://help.spinach.ai/en/articles/14441991-troubleshooting-spinach-bot-not-joining-or-rejoining-meetings (fetched 2026-08-19) · retrieved 2026-08-19
  • Create Tickets from Action Items — https://help.spinach.ai/en/articles/8593494-create-tickets-from-action-items (fetched 2026-08-19) · retrieved 2026-08-19
  • Organize Recordings with Collections — https://help.spinach.ai/en/articles/14627815-organize-recordings-with-collections (fetched 2026-08-19) · retrieved 2026-08-19
  • FAQ — https://help.spinach.ai/en/articles/6143481-faq (fetched 2026-08-19) · retrieved 2026-08-19
  • Security — https://www.spinach.ai/security (fetched 2026-08-19) · retrieved 2026-08-19
  • Spinach help centre machine index — https://help.spinach.ai/llms.txt (fetched 2026-08-19) · retrieved 2026-08-19
  • help.spinach.ai/robots.txt disallows three paths and names a sitemap, with a one-second crawl delay; www.spinach.ai/robots.txt is a bare allow with a sitemap. Neither host sends a Content-Signal header (fetched 2026-08-19). spinach.ai without the www. prefix 301-redirects · retrieved 2026-08-19
  • Live RFC 9728 protected-resource descriptor — https://mcp.spinach.ai/.well-known/oauth-protected-resource (fetched 2026-08-19; both the path-append and path-insert forms return an HTML 404, and the descriptor carries no scope field) · retrieved 2026-08-19
  • Live RFC 8414 authorization-server metadata — https://mcp.spinach.ai/.well-known/oauth-authorization-server (fetched 2026-08-19; scopes_supported names mcp:read and mcp:write) · retrieved 2026-08-19
  • Live anonymous probe — 2026-08-19: a POST to the endpoint returns HTTP 401 with www-authenticate naming resource_metadata at the root well-known path. https://mcp.spinach.ai/.well-known/openid-configuration returns 404 · retrieved 2026-08-19
  • Anthropic connector directory — https://claude.ai/directory/50817992-a7f8-4ac2-bdc4-2f655b87168c (snapshot 2026-08-16; three tool names, no prompt names, permissions label "Read only") · retrieved 2026-08-16

More Productivity connectors

  • 6sense

    Ask an AI agent about 6sense account insights, buying signals and keyword trends.

  • Adobe Workfront

    Find, create, update and delete Workfront work items from an AI agent.

Browse all MCP connectorsClaude and ChatGPT setup guideBrowse AI skills

Product names and logos belong to their owners. Agentman is not affiliated with a connector's maker unless the page says the connector is built and run by Agentman.

Use it in an agent

Put Spinach AI to work.

Connect Spinach AI once and your agents call these tools on their own: on a schedule, in a workflow, with nobody at the keyboard.

Open in Agentman Studio
Call (650) 285-1019Our AI receptionist answers.