Connect the Spinach MCP server to Claude so you can pull meeting decisions, action items, and summaries straight into your conversation — grounded in what was actually said, and in what was actually on screen.

Difficulty: Easy · about 4 min · Server: mcp.spinach.ai

What you'll be able to do

Pull action items, decisions, and summaries into any chat — including who owns each action item and what's blocking it.
Ask questions across every meeting Spinach has recorded for you.
Have Claude analyze the recording itself, not just the transcript — slides, screen shares, whiteboards, and how the room reacted. See Ask about what was on screen below.
Draft follow-ups grounded in what was actually said.
Keep access governed by your Spinach permissions — Claude only ever sees the meetings you're authorized to see.

Before you start

An active Spinach account on a plan that includes MCP access.
A Claude plan that supports custom connectors — available on Free, Pro, Max, Team, and Enterprise (Free is limited to one custom connector).
No token or API key required. Spinach uses a secure OAuth sign-in, so you stay in control and can revoke access at any time.

Set it up

You can connect Spinach to Claude across the Claude Desktop app, Cowork, claude.ai (web, including Team and Enterprise workspaces), and Claude Code. They all use MCP under the hood.

Claude Desktop, Cowork, and claude.ai (personal Pro / Max)

Open Claude and go to Customize → Connectors.
Click the + button, then choose Add custom connector.
Fill in:
- Name: Spinach AI
- Remote MCP server URL: https://mcp.spinach.ai/mcp
Leave Advanced settings alone — Spinach runs its own OAuth flow, so you do not need an OAuth Client ID or Client Secret.
Click Add to save the connector.
Open a chat and ask a Spinach question (for example, "What did we decide in my last standup?"). A browser window opens — log in to Spinach and click Allow.

[Screenshot placeholder — Claude's "Add custom connector" dialog with Name "Spinach AI" and the server URL filled in.]

Claude Team / Enterprise workspaces

The connector is added once by an Owner at the org level. Each member then connects their own Spinach account, so Claude only sees the meetings each person is authorized to access.

Owner — one-time org setup (only an Owner or Primary Owner can do this):

Sign in to claude.ai as the workspace Owner.
Go to Settings → Organization settings → Connectors and click Add.
Hover over Custom, then select Web (remote MCP).
Enter Name: Spinach AI and Remote MCP server URL: https://mcp.spinach.ai/mcp. Leave Advanced settings alone.
Click Add. Spinach AI is now available to everyone in the organization.

Each team member — connect your account:

Go to Customize → Connectors.
Find Spinach AI in the list (labeled "Custom") and click Connect.
Log in to Spinach in the browser window and click Allow.

Don't see "Spinach AI" in your list? Your Owner hasn't added it at the org level yet — connectors added on a personal Claude account don't appear inside a Team / Enterprise workspace.

Claude Code (terminal)

In your terminal, run:

claude mcp add spinach --transport streamable-http https://mcp.spinach.ai/mcp

Start a new Claude Code session and ask a Spinach question. Claude Code opens a browser window — log in and click Allow.

Prefer config? Add Spinach to your project's .mcp.json instead:

{  "mcpServers": {    "spinach": {      "type": "streamable-http",      "url": "https://mcp.spinach.ai/mcp"    }  }}

Heads up — first-time indexing: after you connect for the first time, it can take 5–10 minutes for all of your meeting data to be indexed and queryable. If your first few searches come back empty, give it a few minutes and try again.

Your connection lasts 12 months. Once authorized, you shouldn't need to reconnect regularly — and you never need to reconnect to pick up new Spinach capabilities. New tools reach existing connections automatically.

Try it

The more context you give Claude, the better Spinach can find what you need. A few prompts to start with:

"What action items were assigned to me in last Thursday's standup?"
"Summarize the key decisions from the Q4 roadmap review."
Owners and blockers: "List every action item from my meetings this week as a table grouped by owner, and flag the ones that are blocked and who's blocking them."
Use collections: if you group meetings into collections in Spinach, name them — "In the Customer Interviews collection, what feature requests came up most this quarter?"
Chain with Claude's other tools: "What were the engineering action items from yesterday's planning meeting? Then create a TODO.md with each one as a checkbox."

Ask about what was on screen

Claude can reach the recording itself, not just the transcript — so anything that happened visually is now answerable. Slides. Screen shares. Whiteboards. Diagrams drawn mid-discussion. How the room reacted.

Things worth trying:

Document a workflow someone demonstrated. "In this meeting, someone walked through their whole process on a screen share. I don't want to watch it — sketch out the workflow from what's on screen."
Read data that was shown but never spoken. "Pull the numbers off the slides that got shared in this call. They were never read out loud."
Understand how a meeting landed. "Read the room on this pitch — who was engaged, who was checked out, who looked skeptical?"
Recover a whiteboard or diagram. "Someone drew an architecture diagram in this session. Describe it and turn it into a written spec."

Pairing the audio with the visual is where this gets useful — "what did the screen show when they said this was broken?" is a better question than either half on its own. Naming a specific meeting and a specific moment beats asking about a whole recording at once.

Video covers the last 7 days

Claude can reach video for recordings from the past week, not your whole archive. This is deliberate — it means an agent working through your meeting history can't quietly download everything you've ever recorded.

For older meetings, Claude will point you to the Spinach web app, where the recording is still available for as long as your video retention period allows. Transcripts, summaries, action items, and search are not limited to 7 days — only video.

Manage or revoke access

You're always in control of which apps can reach your Spinach data.

Log in to your Spinach account.
Go to Settings → Integrations.
Scroll to Authorized Applications. For each connection you can see when it was authorized, when it was last used, and its permissions. Click Revoke to disconnect immediately.

[Screenshot placeholder — the Authorized Applications list in Spinach Settings → Integrations.]

Troubleshooting

My first searches return nothing: initial indexing takes 5–10 minutes. Wait a few minutes and try again.
Claude can't get the video for a meeting: video covers the last 7 days only. For older meetings, open the recording in the Spinach web app. Some recordings not hosted directly by the meeting provider also aren't reachable over MCP.
I don't see connector setup under Settings: Anthropic moved custom-connector setup to the Customize tab. Look under Customize → Connectors and use the + button.
Team / Enterprise members can't see Spinach: an Owner has to add it at the org level first (see the Team / Enterprise steps above).
I don't see newer Spinach tools: your client may have cached the old tool list. Toggle the Spinach connector off and on (or remove and re-add it), and restart the app. In Claude Code, run claude mcp remove spinach, add it again, and confirm with claude mcp list.
Connection fails: make sure the URL is exactly https://mcp.spinach.ai/mcp, then remove and re-add the connector and restart.
Authorization issues: in Spinach, go to Settings → Integrations → Authorized Applications, revoke access for Claude, and connect again.

Connect another tool

Spinach also works with ChatGPT, Gemini, and Cursor:

ChatGPT — install the approved Spinach AI app from the ChatGPT app directory.
Gemini — see Gemini MCP Integration.
Cursor — see Cursor MCP Integration.

Claude MCP Integration