The Model Context Protocol (MCP) lets you access Squad’s AI capabilities directly within Claude Desktop and other compatible applications. Query your product data and get strategic insights without leaving your workflow.Download Squad MCP

​
Overview

Squad’s MCP server enables AI assistants to:
  • Query your product strategy and roadmap
  • Analyze opportunities and solutions
  • Search through user feedback and insights
  • Generate reports from your Squad workspace
This guide shows how to set up and use Squad through MCP.

​
Why this matters for product teams

  • Copy-pasting specs between tools
  • Manual PRD templates
  • Context gaps in conversations
Bottom line: MCP turns Claude into an extension of Squad, giving PMs instant, conversational access to strategy artifacts while developers stay in sync with up-to-date requirements.

​
Under the hood

Our open-source squad-mcp server bundles a curated set of tools generated from the Squad API:
Tool prefixPurposeTypical actions
opportunity_*Discover and refine product opportunitiescreate, list, update
solution_*Generate and iterate on solutionscreate, list, update
outcome_*Track desired business or user outcomescreate, list
requirement_*Capture detailed requirementscreate, list
knowledge_*Store useful references / researchcreate, list
workspace_*Manage Squad workspacesget, update
feedback_*Send customer or analytics feedback into Squadcreate
All tools conform to the MCP JSON schema format so that agents can introspect inputs and outputs automatically.

​
Prerequisites

Before starting, ensure you have:

Squad Account

Active Squad workspace with data

Claude Desktop

Version 0.7.2 or higher installed

Node.js

Version 18 or higher (for npx)

API Key

Squad API key from Settings

​
Quick start

​
Step 1: Get your Squad API key

1

Open Squad Settings

Navigate to Workspace → API Keys in your Squad workspace
2

Generate API key

Click Generate New Key and copy the key
squad-mcp-api-key.webp
3

Save securely

Store this key safely - you’ll need it for configuration
Keep your API key secret. Anyone with this key can access your Squad data.

​
Step 2: Configure Claude Desktop

Add Squad to your Claude Desktop configuration:
Open config file:
code ~/Library/Application\ Support/Claude/claude_desktop_config.json
Or:
nano ~/Library/Application\ Support/Claude/claude_desktop_config.json

​
Step 3: Add Squad MCP server

Add this configuration to your claude_desktop_config.json: 
{
  "mcpServers": {
    "meet-squad": {
      "command": "npx",
      "args": [
        "-y",
        "@meetsquad/mcp-server"
      ],
      "env": {
        "SQUAD_API_KEY": "your-api-key-here"
      }
    }
  }
}
Replace your-api-key-here with your actual Squad API key from Step 1.

​
Step 4: Restart Claude Desktop

  1. Fully quit Claude Desktop (not just close the window)
  2. Reopen Claude Desktop
  3. Look for the 🔌 icon in the chat interface
  4. Click it to verify Squad is connected

​
Available commands

Once connected, you can query Squad data directly in Claude:

​
Strategy queries

"What is our product mission?"
"Show me our current goals and progress"
"Which goals are we behind on?"

​
Analytics queries

"What are users complaining about most?"
"Show recent feedback about delivery times"
"What's our current NPS score?"

​
Report generation

"Generate a weekly status update"
"Create an executive summary of our strategy"
"What did we ship last month?"

​
Example workflows

​
Workflow 1: Strategy review

You: Can you review our current product strategy and identify gaps?

Claude (with Squad): I'll analyze your Squad workspace...

Based on your data:

CURRENT STRATEGY:
- Mission: "Make food delivery faster and more affordable"
- Active goals: 3 (1 on track, 2 behind)
- Opportunities in backlog: 12
- Solutions in development: 4

KEY GAPS IDENTIFIED:
1. Delivery time goal is 7 minutes behind target
   - Root cause: Restaurant prep delays (8,234 mentions)
   - No active solution addressing this

2. Low user retention (2.1 orders/week vs 3.0 target)
   - Missing lunch-time availability
   - Limited restaurant variety in suburbs

3. Unaddressed opportunities:
   - Group ordering (3,892 requests, no solution)
   - Dietary filters (2,156 requests, no solution)

RECOMMENDATIONS:
1. Prioritize restaurant prep time optimization
2. Expand lunch partnerships
3. Add group ordering to Q3 roadmap

​
Workflow 2: Data analysis

You: Analyze user feedback from the last 30 days and identify trends

Claude (with Squad): Analyzing your Squad feedback data...

FEEDBACK ANALYSIS (Last 30 days):
Total feedback items: 4,827

TOP THEMES:
1. Delivery delays (1,243 mentions, ↑23% from previous)
   - "Food arrives cold"
   - "Waited over an hour"
   - Concentrated in downtown areas

2. Payment issues (892 mentions, ↑45% from previous)
   - "Payment failed but still charged"
   - "Can't save payment method"
   - Spike started after latest app update

3. Restaurant variety (634 mentions, →0% change)
   - "Same restaurants every time"
   - "No healthy options"
   - Consistent complaint, not growing

EMERGING ISSUES:
- App crashes on Android 14 (127 mentions, new)
- Promo codes not applying (89 mentions, ↑200%)

SENTIMENT TREND:
- Overall: 3.8/5 (↓ from 4.1/5)
- Critical driver: Payment failures

​
Workflow 3: Roadmap planning

You: Based on our data, what should we build next quarter?

Claude (with Squad): Analyzing your opportunities, user feedback, and current metrics...

Q3 ROADMAP RECOMMENDATIONS:

MUST DO (High impact, addresses critical issues):
1. Fix payment processing bugs
   - Impact: 892 users affected monthly
   - Effort: 1 sprint
   - Reduces churn by ~15%

2. Restaurant prep time prediction
   - Impact: 7-minute delivery reduction
   - Effort: 3 sprints
   - Addresses top complaint

DO NEXT (High value, strategic):
3. Group ordering
   - Impact: $45 AOV increase
   - Effort: 2 sprints
   - 3,892 requests

4. Lunch partnerships
   - Impact: +0.8 orders/week/user
   - Effort: 2 sprints
   - Unlocks new daypart

CONSIDER (Nice to have):
5. Dietary filters
6. Advanced routing v3
7. Loyalty program expansion

This prioritization optimizes for fixing critical issues first, then expanding use cases.

​
Best practices

Be specific

Ask for particular metrics or date ranges for better results

Cross-reference

Combine multiple data sources for comprehensive analysis

Regular reviews

Schedule weekly strategy reviews with Claude + Squad

Action-oriented

Always end with “What should we do about this?”

​
Troubleshooting

Check these common issues:
  1. Config file syntax: Ensure valid JSON (check commas, quotes)
  2. API key: Verify key is correct and active
  3. Claude restart: Must fully quit and reopen
  4. Node.js: Ensure Node 18+ is installed
If Squad commands fail:
  1. Check the 🔌 icon shows Squad as connected
  2. Verify your API key has correct permissions
  3. Ensure your Squad workspace has data
  4. Try simpler queries first
If you see rate limit errors:
  • Squad MCP allows 100 requests per minute
  • Complex queries may use multiple requests
  • Wait 60 seconds if you hit limits
  • Consider upgrading your Squad plan for higher limits

​
Security considerations

Important security notes:
  • API keys are stored locally on your machine
  • Never share your claude_desktop_config.json file
  • Rotate API keys regularly
  • Use read-only keys when possible

​
Advanced usage

​
Custom queries

Squad MCP supports complex analytical queries: 
"Compare our user retention to industry benchmarks and suggest 
improvements based on what's working for competitors"

"Generate a board presentation covering our Q2 performance, 
Q3 roadmap, and key risks to address"

"Analyze which features correlate with highest user LTV and 
recommend where to double down"

​
Workflow automation

Combine Squad MCP with other tools:
  1. Daily standup prep: “What changed in our metrics since yesterday?”
  2. Sprint planning: “Which backlog items align with this sprint’s goal?”
  3. Investor updates: “Generate a monthly progress report”

​
Getting help

MCP Docs

Learn more about MCP