Overview

Want to access insights and context from your recent Spinach meetings directly within your favorite AI tools? Our new integration makes this possible, allowing connected applications to securely query the content of ALL you Spinach meetings.

This guide provides specific instructions for connecting Spinach to Claude (Desktop, Cowork, claude.ai, and Claude Code), ChatGPT, and developer IDEs like Cursor and VS Code. The connection is handled with a secure, simple OAuth flow, giving you full control to manage and revoke access at any time.

What's Available Through the Spinach MCP

Once connected, your AI tool can use the following Spinach capabilities on your behalf:

Search across your meetings — Find specific discussions, decisions, or action items. Combines keyword and semantic search so natural-language queries work well.
List meetings — Browse meetings with filters for title, date range, participants, platform (Zoom, Google Meet, Teams), and now collection.
List your collections (new) — Get all collections (curated groups of related meetings) you own or have access to, including how many meetings each contains and your role on each.
Filter meetings by collection (new) — Narrow lookups to a specific collection, e.g. "weekly engineering syncs" or "customer interviews."
Pull a full meeting — Get the summary, action items, decisions, chapters, participants, and transcript of a specific meeting by ID.
Live meeting context — When a meeting is in progress (and live captions are enabled), pull the live transcript so the AI can act on it in real time.

Heads up — initial indexing: After connecting Spinach 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 before assuming something is wrong.

Connecting Spinach to Claude

You can connect Spinach to Anthropic's Claude across the Claude Desktop App, Cowork (Anthropic's desktop agent), claude.ai (web, including Team and Enterprise workspaces), and Claude Code (the command-line tool for agentic coding). All of them use MCP under the hood.

Claude Desktop, Cowork, and claude.ai (Web)

All three surfaces use the same connector setup, accessed via Customize → Connectors. Claude Team and Enterprise workspaces have one extra one-time step for the org Owner.

For personal Pro / Max accounts (Desktop, Cowork, or claude.ai)

Open Claude (Desktop, Cowork, or claude.ai) and go to Customize → Connectors.
Click the + button next to Connectors, then choose Add custom connector.
Fill in:
- Name: Spinach AI
- Remote MCP server URL: https://mcp.spinach.ai/mcp
Leave Advanced settings alone — Spinach uses its own OAuth flow, so you do not need a Client ID or Client Secret.
Click Add to save the connector.
Open a chat and ask a Spinach question. A browser window opens — log in to your Spinach account and click Allow.

For 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 user is personally 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).
Fill in Name: Spinach AI and Remote MCP server URL: https://mcp.spinach.ai/mcp. Leave Advanced settings alone.
Click Add. The connector is now available to every member of the organization.

Each team member — connect your Spinach account:

Go to Customize → Connectors.
Find Spinach AI in the list (it will be labeled "Custom") and click Connect.
Log in to your Spinach account in the browser window and click Allow. You're returned to Claude with the connector connected.

Don't see "Spinach AI" in your connector list? The Owner has not added it yet at the org level — they need to complete the Owner setup above first. Connectors added on a personal Claude account do not appear inside a Team / Enterprise workspace.

Note: Anthropic recently moved custom-connector setup from Settings to the Customize tab. If older instructions point you to Settings > Connectors, look under Customize → Connectors instead.

Claude Code (Terminal)

To add Spinach as an MCP server in Claude Code:

Open your terminal and run:

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

Authorize: Start a new Claude Code session and ask a Spinach question. Claude Code will open a browser window — log in with your Spinach account and click Allow.

Alternatively, add Spinach to your project's .mcp.json file:

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

Connecting Spinach to ChatGPT

Spinach is now an approved ChatGPT app — you can install it directly from the ChatGPT app directory, no custom connector setup required. Install link: Spinach AI on ChatGPT.

Personal Plus / Pro users can install the app for themselves. Business, Team, and Enterprise workspace admins can install Spinach AI once for the entire organization and (optionally) pin it as a default app — each member then signs in to their own Spinach account, so ChatGPT only ever sees the meetings each individual user is authorized to access.

Personal accounts (Plus / Pro)

Open Spinach AI in the ChatGPT app directory (or search for "Spinach AI" from Apps in ChatGPT).
Click Install on the app page.
Start a new chat and call Spinach with @ — e.g. @spinach what was discussed in my last meeting?
ChatGPT will open a browser window — log in with your Spinach account and click Allow to authorize the connection.

Workspace admins — Install Spinach AI for your organization

A ChatGPT Business, Team, or Enterprise workspace owner or admin installs the app once at the workspace level. After that, every member sees Spinach AI as an available app and just needs to sign in to their own Spinach account.

Sign in to ChatGPT as a workspace owner or admin.
Open Settings → Workspace → Connectors & apps.
Open the Spinach AI app page (or search "Spinach AI" in the directory).
Click Install for workspace (or Add to workspace) and confirm. Spinach AI is now available to every member of your workspace.

(Optional) Pin Spinach AI as a default app

Pinning makes Spinach AI more discoverable — it surfaces in the apps drawer for every member by default, so they don't have to enable it manually.

In Settings → Workspace → Connectors & apps, find Spinach AI in your installed apps list.
Toggle Pin for members (or Recommended / Default app — wording varies by plan) so Spinach AI shows up in every member's chat composer by default.

Members — Connect your Spinach account

Once your admin has installed Spinach AI for the workspace, each member completes a one-time per-user sign-in:

Open ChatGPT and start a new chat.
Click the + / Apps button in the composer and select Spinach AI — or just type @spinach.
The first time you use it, ChatGPT will prompt you to sign in. Click the button, log in to your Spinach account, and click Allow.
You're done. Try @spinach summarize my last meeting to confirm it's working.

Each member only sees their own meetings. Authorization happens per user via OAuth, so ChatGPT can only access the meetings each individual is authorized to access in Spinach. End users can revoke access at any time from Settings → Integrations → Authorized Applications in their Spinach account (see the Managing Your Connected Applications section below).

Notes:

ChatGPT apps require a paid ChatGPT plan (Plus, Pro, Business, Team, or Enterprise).
Each user signs in to their own Spinach account, so ChatGPT only sees meetings they're already authorized to access in Spinach.
You can revoke ChatGPT's access to Spinach at any time from Settings → Integrations → Authorized Applications in your Spinach account.

Connecting Spinach to IDEs (Cursor, VS Code, etc.)

For developer tools, the connection is made by editing a local JSON configuration file.

Find Your Tool's Configuration File:
- For Cursor: Go to Settings > Cursor Settings > Tools & Integrations and click New MCP Server to open the mcp.json file.
- For VS Code: Run the command MCP: Open User Configuration from the Command Palette to open your mcp.json file.
Add the Spinach Server Configuration: Add the following JSON object to the mcpServers configuration:
```
"spinach": {  "url": "https://mcp.spinach.ai/mcp"}
```
Authorize the Connection: Save the file and return to the chat interface. Call the Spinach tool (@spinach Test my connection). Your IDE will open a browser window — log in with your Spinach account and click Allow.

Best Practices for Querying Spinach

These tips apply across Claude (Desktop, Cowork, claude.ai, Code), ChatGPT, Cursor, VS Code, and any other MCP-enabled tool. The more context you give the AI, the better Spinach can find what you need.

Be specific in your prompts

Instead of "What did we talk about?", ask:

"@spinach summarize the key decisions made about the Q4 roadmap in our meetings last week."
"@spinach what action items were assigned to me in last Thursday's standup?"

Include project names, people, and dates whenever possible.

Use collections to scope your searches

If you organize meetings into collections in Spinach (for example, "Customer Interviews", "Eng Weekly", or "Board Meetings"), reference them in your prompts to dramatically improve relevance:

"@spinach list my collections" — to see what's available to you.
"@spinach in the 'Customer Interviews' collection, what feature requests came up most often this quarter?"
"@spinach summarize the last 5 meetings in 'Eng Weekly' and list the top blockers."

Naming a collection is the single biggest lever for cutting through irrelevant context — use it whenever you can.

Use action-oriented language

"@spinach list the action items assigned to me regarding the user authentication feature."
"@spinach generate a list of engineering concerns raised about the database migration."
"@spinach find the original discussion where we decided on the new pricing model."

Iterate and refine

Start broad, then dig deeper:

"@spinach what were the main topics from the last project sync?"
"For topic #3, what were the exact blockers that were mentioned?"

Ask for formatted output

"@spinach summarize the discussion about our new marketing campaign and format it as a bulleted list of key takeaways."
"@spinach list all the action items from this week's meetings as a markdown table grouped by owner."

Use date ranges to narrow results

Adding a timeframe ("last week", "since the start of April", "this quarter") helps the AI narrow down quickly and avoid pulling irrelevant context.

Chain Spinach with your AI's other tools

In Cursor, Claude Code, Claude Desktop, or Cowork, combine Spinach with file edits, GitHub, or other connectors:

"@spinach what were the engineering action items from yesterday's planning meeting? Then create a TODO.md in this repo with each one as a checkbox."
"@spinach summarize today's customer call, then draft a Linear ticket for the top three feature requests."

Managing Your Connected Applications

You have full control over which applications can access your Spinach data. You can view, manage, and revoke access at any time from your Spinach dashboard.

Log in to your Spinach account.
Navigate to Settings > Integrations.
Scroll to the Authorized Applications section.

Here you will see a list of all the applications you have connected. For each connection, you can see when it was authorized, when it was last used, its current status, and the permissions it has.

To disconnect an application, click the Revoke button. Access will be terminated immediately.

Troubleshooting Tips

I just connected but searches return nothing: After your first connection, it can take 5–10 minutes for all your meeting data to be fully indexed and available. Wait a few minutes and try again before assuming something is broken.
I don't see new Spinach tools (e.g. list_collections): If you connected Spinach a while ago and aren't seeing newer tools, your client may have cached the older tool list. Refresh the tool list in your client:
- Claude Desktop, Cowork, or claude.ai: Go to Customize → Connectors, toggle the Spinach connector off and on, or remove and re-add it (use the + button to add). Restart the app if the new tools still don't appear.
- Claude Code: Run claude mcp remove spinach, then claude mcp add spinach --transport streamable-http https://mcp.spinach.ai/mcp, and start a new session. Confirm with claude mcp list.
- ChatGPT: Open Settings > Apps & Connectors, click into Spinach AI, and use Refresh — or remove and reinstall the app.
- Cursor / VS Code: In Cursor Settings > Tools & Integrations (or the VS Code MCP panel), disable and re-enable the Spinach server, or restart the editor.
I don't see the connector setup under Settings: Anthropic moved custom-connector setup from Settings to the Customize tab. In Claude Desktop, Cowork, and claude.ai, look under Customize → Connectors and use the + button.
Claude Team / Enterprise members can't see the Spinach connector: The org Owner has not added Spinach at the workspace level yet. Have an Owner or Primary Owner follow the Owner setup steps in the Claude section above. Connectors added on personal claude.ai accounts do not carry over into Team / Enterprise workspaces.
Don't see Spinach AI in ChatGPT (Business / Team / Enterprise): Your workspace admin needs to install the Spinach AI app from the ChatGPT app directory first. Once it's installed for the workspace, the app appears in your apps list and you can sign in to your Spinach account.
IDE Connection Fails: Ensure the JSON in your mcp.json file is formatted correctly. A missing comma or bracket will cause it to fail. Try restarting your IDE to re-trigger the connection prompt.
Claude Code Connection Fails: Make sure you have the latest version of Claude Code installed. You can verify the server was added by running claude mcp list. If the server isn't appearing, try removing it with claude mcp remove spinach and adding it again.
Claude Desktop, Cowork, or claude.ai Connection Fails: Ensure you entered the URL exactly as https://mcp.spinach.ai/mcp. Try removing the connector from Customize → Connectors and adding it again. If the issue persists, restart the app.
Authorization Issues: If a tool is having trouble connecting, navigate to the Authorized Applications section in your Spinach settings, revoke access for that application, and then try the connection process again.
App failing authentication: We have only currently whitelisted a few services to work with Spinach. If you are running into an issue with a non-standard service or internal tool, please reach out so we can help whitelist new use cases for you.