Skip to main content

MCP Configuration

Yoav Grossman avatar
Written by Yoav Grossman
Updated this week

Connecting Spinach Meeting Context to Cursor using the MCP Server

Applies to: Users wishing to integrate recent Spinach meeting data with external tools like Cursor, VSCode, Windsurf, Claude, etc. You will find insturctions for each below.

Overview

Want to access insights and context from your recent Spinach meetings directly within tools like Cursor? The Spinach MCP (Meeting Context Provider) Server integration makes this possible.

This feature provides a secure link that allows connected tools to query the content of your last 10 Spinach meetings. This guide explains how to set up the integration specifically for Cursor.

Here is a demo of how you can use the MCP to help chain prompts and get insights into your IDE:

Benefits of Using the MCP Server:

  • Query Recent Meetings: Ask questions about features, discussions, decisions, or topics from your last 10 meetings directly in your tools.

  • Faster PRD Generation: Leverage meeting context to quickly draft Product Requirements Documents.

Before You Start:

  • Ensure you have an active Spinach account.

  • Ensure you have Node installed.

How to Set Up the Integration

The setup involves two main parts: getting your unique MCP API key from Spinach and adding it to your tool.

Part 1: Get Your MCP API Key from Spinach

  1. Log in to your Spinach Dashboard.

  2. Navigate to the Settings section (usually found via a gear icon or profile menu).

  3. Within Settings, find the section labeled MCP Server

  4. Locate your unique MCP API KEY. Click Display API key.

  5. Copy this complete API Key to your clipboard. You'll need it for the next part.

    • Example API Key (Yours will be unique): a1b2c3d4e5f6...

Part 2 (Cursor): Add the MCP API to Cursor

  1. Make sure you have Node installed on your computer as the implementation relies on NPM package.

  2. Open the Cursor application.

  3. Go to the Settings menu within Cursor -> Cursor settings

  4. Click on MCP

  5. Click Add new global MCP server

  6. Click create file

  7. In this file you will add in your unique API Key this format from the link in settings

    1. { "mcpServers": { "spinach": { "command": "npx", "args": ["-y", "@spinach.ai/spinach-mcp-stdio-server@latest"], "env": { "API_KEY": "<your_api_key>" } } }

    2. Note: This API Key is unique to you and includes a token to your specific meetings. DO NOT SHARE this API Key with anyone else.

  8. Go back to Cursor settings and tap Refresh/Reload Connection (Important): After adding the API key, you may need to refresh or reload the data sources within Cursor to ensure it recognizes the new connection. This might be a specific button or might require restarting a part of Cursor.

  9. Test the Connection: Use Cursor's interface and select Agent to run a test connection to the MCP server.

    1. To test the connection type the following:

    2. Test my connection with Spinach

c. When calling the tool, you will want to click the run tool to make it work

Part 2 (Claude) Adding MCP To Claude:

  1. Setup Claude to support MCP servers. You can find instructions here.

  2. Make sure you have Node installed on your computer as the implementation relies on NPM package.

  3. Go to claude settings -> Developer -> Edit config

  4. In config, enter this JSON:

    { "mcpServers": { "spinach": { "command": "npx", "args": ["-y", "@spinach.ai/spinach-mcp-stdio-server@latest"], "env": { "API_KEY": "<YOUR API KEY FROM SPINACH>" } } } }

  5. Test the Connection: Use Chat interface to run a test connection to the MCP server.

    1. To test the connection type the following:

    2. Test my connection with Spinach

Part 2 (VS Code) Adding MCP To VS Code:

  1. Setup VS Code for MCP servers. You can find instructions here.

  2. Make sure you have Node installed on your computer as the implementation relies on NPM package.

  3. In the .vscode/mcp.json config file, enter this JSON:

    { "mcpServers": { "spinach": { "command": "npx", "args": ["-y", "@spinach.ai/spinach-mcp-stdio-server@latest"], "env": { "API_KEY": "<YOUR API KEY FROM SPINACH>" } } } }

  4. Test the Connection: Use Chat interface to run a test connection to the MCP server.

    1. To test the connection type the following:

    2. Test my connection with Spinach

Part 2 (Windsurf) Adding MCP to Windsurf.

  1. Setup Windsurf for MCP servers. You can find instructions here.

  2. Make sure you have Node installed on your computer as the implementation relies on NPM package.

  3. In the ~/.codeium/windsurf/mcp_config.json config file, enter this JSON:

    { "mcpServers": { "spinach": { "command": "npx", "args": ["-y", "@spinach.ai/spinach-mcp-stdio-server@latest"], "env": { "API_KEY": "<YOUR API KEY FROM SPINACH>" } } } }

  4. Test the Connection: Use Chat interface to run a test connection to the MCP server.

    1. To test the connection type the following:

    2. Test my connection with Spinach

Using the Spinach MCP Integration

Once the connection is successfully set up and tested, you can start querying your meeting data.

  1. In the chat: Generate PRD using Spinach about [Feature name] and put it into <File name>

    1. This will gather all the context from the last 10 meetings about this specific feature and generate a crafted PRD to enable you to build

    2. This will output the PRD into a file that you can then reference and use with other tasks

    3. We suggest using at least Claude 3.5 with agent to get good results. (depends on tool, below is what it looks like in Cursor)

  2. In chat ask: Based on my last meetings in spinach, [ask question] and put into <file name>

    1. This will analyze your last 10 meetings to provide you insight about the concept

    2. Putting into file name will make it easier to leverage the data

  3. Chaining - In the chat ask: Find the most important task in Spinach and generate a PRD for it

    1. This will chain tool 1 and 2 together to create multiple step context. You can try all sorts of variations of this feature.

Remember: All queries made through this integration will only access data from your last 10 meetings recorded in Spinach.

Troubleshooting Tips:

Note: This is an Alpha feature and we expect that connect will drop when we deploy. If you experience an outage, just wait a few minutes and refresh.

  • Connection Test Fails: Double-check that you copied the entire MCP API Key from Spinach correctly. Ensure there are no extra spaces or characters. Try refreshing the connection again. Try restarting the client.

  • No Data Found: Remember the 10-meeting limit. Ensure the information you're querying falls within your most recent sessions.

If you continue to experience issues setting up or using the integration, please contact our support team for assistance.

Related Articles
Spinach on Zoom
Getting Started with Spinach AI
Google Drive/Docs Integration
Spinach on Webex
Zapier Integration
Did this answer your question?