CCM
/MCP
SkillsMCPMarketplacesDigestToolsAdvertise

This week in Claude

Every Monday: Claude Code, Agent SDK, MCP, and the Anthropic platform moves worth your time.

Skills by Category
Frontend DevelopmentBackend & APIsTesting & QASecurityDevOps & CI/CDGit & Pull RequestsDocumentationCode Review & QualityAI & Agent BuildingSkill Development
MCP Servers by Category
Sales & MarketingWeb & Browser AutomationDatabasesAI & LLM ToolsCloud & InfrastructureCommunication & MessagingDeveloper ToolsDesign & CreativeDocuments & KnowledgeSearch & Web Crawling
Marketplaces by Category
AI Agents & OrchestrationLLM IntegrationDevelopment ToolsFrontend & UIBackend & APIsDatabasesTesting & Code QualityDevOps & CloudSecurity & ComplianceGit & Version Control

Claude Code Marketplaces

Discover Claude Code plugins, extensions, and tools. Automatically updated directory of Anthropic Claude AI marketplaces with development tools, productivity plugins, and integrations.

Resources

  • Browse Skills
  • Browse MCP Servers
  • Browse Marketplaces
  • Plugins Reference

Community

  • About
  • Tools
  • Feedback
  • Privacy Policy
  • Advertise

Built for the Claude Code community with Claude Code by @mertduzgun

Independent project, not affiliated with Anthropic

Squad

the-basilisk-ai/squad-mcp
240 toolsHTTPregistry active
Summary

Connects Squad's product management platform to Claude or any MCP client via OAuth, exposing 30+ tools for managing opportunities, solutions, goals, feedback, and knowledge. You get full CRUD on each entity type, plus relationship management between them, semantic search across your workspace, and strategic views like OST mapping and roadmaps. The server mints JWTs from OAuth tokens and proxies requests to Squad's API with user isolation. Reach for this when you want to research product ideas, build roadmaps, or query customer insights without leaving your AI conversation. Authentication happens through PropelAuth with automatic OAuth discovery, and there's a companion NPM package if you want to use the tools programmatically in Node apps.

CodeRabbit
CodeRabbit
AI writes the code. CodeRabbit catches the slop.
Try For Free →
AppSignal
AppSignal
Monitor with ease. Code with confidence.
Start Free Trial →
AI notepad for back-to-back meetings
AI notepad for back-to-back meetings
Notes, actions and memory. Without a meeting bot. First month 100% off.
Download for free →
Keep your Mac awake
Keep your Mac awake
Keep your Mac awake while Claude Code and 40+ AI agents run. Sleeps when they're idle.
One time payment $9 →
Email for Agents: Free tier availableEmail for Agents: Free tier available
Email for Agents: Free tier available
Give your AI agent a complete email layer—sending, inbound inboxes, and sandbox testing.
Get 4K emails/month free →
Context.devContext.dev
Context.dev
Integrate web data into your AI product. One API to scrape website & brand data.
Get API Key Now →
CodeScene MCP ServerCodeScene MCP Server
CodeScene MCP Server
Your agent targets a perfect 10 Code Health score. Deterministic. Every commit.
Try For Free →
Make your agent a DeFi expert
Make your agent a DeFi expert
Agent, run crypto. Access onchain data & trade routes via 1inch.
Install now →
CodeRabbit
CodeRabbit
AI writes the code. CodeRabbit catches the slop.
Try For Free →
AppSignal
AppSignal
Monitor with ease. Code with confidence.
Start Free Trial →
AI notepad for back-to-back meetings
AI notepad for back-to-back meetings
Notes, actions and memory. Without a meeting bot. First month 100% off.
Download for free →
Keep your Mac awake
Keep your Mac awake
Keep your Mac awake while Claude Code and 40+ AI agents run. Sleeps when they're idle.
One time payment $9 →
Email for Agents: Free tier availableEmail for Agents: Free tier available
Email for Agents: Free tier available
Give your AI agent a complete email layer—sending, inbound inboxes, and sandbox testing.
Get 4K emails/month free →
Context.devContext.dev
Context.dev
Integrate web data into your AI product. One API to scrape website & brand data.
Get API Key Now →
CodeScene MCP ServerCodeScene MCP Server
CodeScene MCP Server
Your agent targets a perfect 10 Code Health score. Deterministic. Every commit.
Try For Free →
Make your agent a DeFi expert
Make your agent a DeFi expert
Agent, run crypto. Access onchain data & trade routes via 1inch.
Install now →

Tools

Public tool metadata for what this MCP can expose to an agent.

40 tools
list_workspacesList all organisations and workspaces available to the current user. Use this to see what workspaces you can switch to.

List all organisations and workspaces available to the current user. Use this to see what workspaces you can switch to.

No parameter schema in public metadata yet.

select_workspaceSelect which organisation and workspace to use for subsequent operations. Required when user has access to multiple orgs/workspaces.2 params

Select which organisation and workspace to use for subsequent operations. Required when user has access to multiple orgs/workspaces.

Parameters* required
orgIdstring
The ID of the organisation to select
workspaceIdstring
The ID of the workspace to select
get_workspaceGet details of the current workspace. Workspaces contain the project name, detailed description, and mission statement.

Get details of the current workspace. Workspaces contain the project name, detailed description, and mission statement.

No parameter schema in public metadata yet.

update_workspaceUpdate the current workspace's details such as name, description, mission statement.5 params

Update the current workspace's details such as name, description, mission statement.

Parameters* required
namestring
Updated name for the workspace
logoUrlstring
Updated URL to the workspace's logo
descriptionstring
Updated detailed description of the workspace
homepageUrlstring
Updated URL to the workspace's homepage
missionStatementstring
Updated mission statement for the workspace
create_opportunityCreate a new opportunity. An opportunity is a detailed problem statement identified for the organisation. It doesn't have any solutionising and simply captures an opportunity for the organisation.2 params

Create a new opportunity. An opportunity is a detailed problem statement identified for the organisation. It doesn't have any solutionising and simply captures an opportunity for the organisation.

Parameters* required
titlestring
A short title
descriptionstring
A short description of the opportunity, detailing the problem statement and opportunity for the business
list_opportunitiesList all opportunities in the workspace. Opportunities are problem statements identified for the organisation.

List all opportunities in the workspace. Opportunities are problem statements identified for the organisation.

No parameter schema in public metadata yet.

get_opportunityGet details of a specific opportunity by ID. Opportunities are problem statements identified for the organisation.2 params

Get details of a specific opportunity by ID. Opportunities are problem statements identified for the organisation.

Parameters* required
opportunityIdstring
The ID of the opportunity to retrieve
relationshipsarray
Relationships to include in the response. Outcomes are business objectives/goals. Solutions are proposed approaches to address opportunities. Feedback is additional information or insights related to the opportunity.
update_opportunityUpdate an existing opportunity's details such as title, description, or status.4 params

Update an existing opportunity's details such as title, description, or status.

Parameters* required
titlestring
Updated title
statusstring
Updated status: New hasn't been developed, InProgress means we're currently building out solutions and implementing them. Planned means we've finished developing the solutions and are ready to implement them. Solved means we've completed the implementation and the opportunity is considered addressed.one of New · Solved · Planned · InProgress
descriptionstring
Updated description
opportunityIdstring
The ID of the opportunity to update
delete_opportunityDelete an opportunity by ID.1 params

Delete an opportunity by ID.

Parameters* required
opportunityIdstring
The ID of the opportunity to delete
generate_solutionsStart the process of generating solutions for an opportunity. This will use Squad AI to generate new potential solutions for a given opportunity.2 params

Start the process of generating solutions for an opportunity. This will use Squad AI to generate new potential solutions for a given opportunity.

Parameters* required
promptstring
Optional prompt to guide solution generation
opportunityIdstring
The ID of the opportunity to generate solutions for
manage_opportunity_relationshipsAdd or remove relationships between an opportunity and other entities (solutions, outcomes, or insights).5 params

Add or remove relationships between an opportunity and other entities (solutions, outcomes, or insights).

Parameters* required
actionstring
Whether to add or remove the relationshipsone of add · remove
insightIdsarray
IDs of insight items to relate to this opportunity
outcomeIdsarray
IDs of outcomes to relate to this opportunity
solutionIdsarray
IDs of solutions to relate to this opportunity
opportunityIdstring
The ID of the opportunity to manage relationships for
create_solutionCreate a new solution. A solution is a proposed approach to address an opportunity. The 'prd' field should contain the complete detailed specification, while 'description' should be a brief summary for AI context.6 params

Create a new solution. A solution is a proposed approach to address an opportunity. The 'prd' field should contain the complete detailed specification, while 'description' should be a brief summary for AI context.

Parameters* required
prdstring
The complete Product Requirements Document (PRD) containing the full detailed specification, implementation plan, and requirements for this solution. This is the primary content field.
consarray
List of cons/drawbacks of this solution. This is a sentence or two max.
prosarray
List of pros/benefits of this solution. This is a sentence or two max.
titlestring
A short title for the solution
statusstring
Status of the solution: New hasn't been developed, InDevelopment means we're currently building out requirements and implementing them. Planned means we've finished developing the solutions and are ready to implement them. Complete means we've completed the implementation and the opportunity is considered addressed. Cancelled means we've cancelled the implementation and the opportunity is no longer considered addressed. Backlog means we've added this to the backlog and it will be worked on in the future.one of New · InDevelopment · Planned · Complete · Cancelled · Backlog
descriptionstring
A brief AI-friendly summary of the solution for context and search purposes. Keep this concise.
list_solutionsList all solutions in the workspace. Solutions are proposed approaches to address opportunities.2 params

List all solutions in the workspace. Solutions are proposed approaches to address opportunities.

Parameters* required
filterstring
Filter solutions: 'roadmap' returns built solutions (user-created or edited), 'recommended' returns AI-generated suggestions not yet acted on. Omit to return all.one of roadmap · recommended
horizonstring
Filter by time horizon: 'now' for current work, 'next' for upcoming, 'later' for future.one of now · next · later
get_solutionGet details of a specific solution by ID.2 params

Get details of a specific solution by ID.

Parameters* required
solutionIdstring
The ID of the solution to retrieve
relationshipsarray
Relationships to include in the response. Opportunities are problem statements identified for the organisation. Outcomes are business objectives/goals. Feedback is additional information or insights related to the opportunity.
edit_solution_prdEdit the PRD (Product Requirements Document) of a solution. Use this to write or rewrite the detailed specification, implementation plan, and requirements for a solution.2 params

Edit the PRD (Product Requirements Document) of a solution. Use this to write or rewrite the detailed specification, implementation plan, and requirements for a solution.

Parameters* required
prdstring
The complete updated PRD content. This replaces the existing PRD entirely.
solutionIdstring
The ID of the solution to edit
update_solutionUpdate a solution's metadata (title, description, pros, cons, status, horizon). To edit the PRD content, use edit_solution_prd. To change priority, use prioritise_solutions. To move a solution between roadmap horizons, set the horizon field.8 params

Update a solution's metadata (title, description, pros, cons, status, horizon). To edit the PRD content, use edit_solution_prd. To change priority, use prioritise_solutions. To move a solution between roadmap horizons, set the horizon field.

Parameters* required
prdstring
Updated complete Product Requirements Document (PRD) containing the full detailed specification and implementation plan
consarray
Updated list of cons/drawbacks
prosarray
Updated list of pros/benefits
titlestring
Updated title
statusstring
Status of the solution: New hasn't been developed, InDevelopment means we're currently building out requirements and implementing them. Planned means we've finished developing the solutions and are ready to implement them. Complete means we've completed the implementation and the opportunity is considered addressed. Cancelled means we've cancelled the implementation and the opportunity is no longer considered addressed. Backlog means we've added this to the backlog and it will be worked on in the future.one of New · InDevelopment · Planned · Complete · Cancelled · Backlog
horizonstring
Roadmap time horizon: 'now' for current work, 'next' for upcoming, 'later' for future.one of now · next · later
solutionIdstring
The ID of the solution to update
descriptionstring
Updated brief AI-friendly summary for context and search purposes
delete_solutionDelete a solution by ID.1 params

Delete a solution by ID.

Parameters* required
solutionIdstring
The ID of the solution to delete
manage_solution_relationshipsAdd or remove relationships between a solution and other entities (opportunities).3 params

Add or remove relationships between a solution and other entities (opportunities).

Parameters* required
actionstring
Whether to add or remove the relationshipsone of add · remove
solutionIdstring
The ID of the solution to manage relationships for
opportunityIdsarray
IDs of opportunities to relate to this solution
prioritise_solutionsReorder the priority of solutions by moving them before a specified solution. This is the only way to change solution priority/ordering in the workspace.2 params

Reorder the priority of solutions by moving them before a specified solution. This is the only way to change solution priority/ordering in the workspace.

Parameters* required
beforeIdvalue
ID of the solution before which to place the solutions, or null to place at the end
solutionIdsarray
List of solution IDs to move
create_goalCreate a new goal. A goal is a business objective that the organization aims to achieve.7 params

Create a new goal. A goal is a business objective that the organization aims to achieve.

Parameters* required
titlestring
A short title for the goal
trendnumber
Trend indicator for the goal (numeric)
ownerIdstring
ID of the goal owner
prioritynumber
Importance level of the goal (1–5, higher = more important)
descriptionstring
A detailed description of the goal
hideContentboolean
Whether the goal content should be hidden
analyticEventsarray
List of analytic events associated with the goal
list_goalsList all goals in the workspace. Goals are business objectives that the organization aims to achieve.

List all goals in the workspace. Goals are business objectives that the organization aims to achieve.

No parameter schema in public metadata yet.

get_goalGet details of a specific goal by ID. Goals are business objectives that the organization aims to achieve.2 params

Get details of a specific goal by ID. Goals are business objectives that the organization aims to achieve.

Parameters* required
goalIdstring
The ID of the goal to retrieve
relationshipsarray
Relationships to include in the response. Opportunities are problem statements identified for the organisation. Solutions are proposed approaches to address opportunities. Insights are additional information related to the opportunity.
update_goalUpdate an existing goal's details.8 params

Update an existing goal's details.

Parameters* required
titlestring
Updated title
trendnumber
Updated trend indicator
goalIdstring
The ID of the goal to update
ownerIdstring
Updated ID of the goal owner
prioritynumber
Updated importance level (1–5, higher = more important)
descriptionstring
Updated description
hideContentboolean
Whether the goal content should be hidden
analyticEventsarray
Updated list of analytic events
delete_goalDelete a goal by ID.1 params

Delete a goal by ID.

Parameters* required
goalIdstring
The ID of the goal to delete
manage_goal_relationshipsAdd or remove relationships between a goal and opportunities for the business.3 params

Add or remove relationships between a goal and opportunities for the business.

Parameters* required
actionstring
Whether to add or remove the relationshipsone of add · remove
goalIdstring
The ID of the goal to manage relationships for
opportunityIdsarray
IDs of opportunities to relate to this goal
create_knowledgeCreate a new knowledge entry. Knowledge entries are text documents that can be used as references or information sources.3 params

Create a new knowledge entry. Knowledge entries are text documents that can be used as references or information sources.

Parameters* required
titlestring
A short title for the knowledge
contentstring
The full content of the knowledge
descriptionstring
A short summary of the knowledge content
list_knowledgeList all knowledge entries in the workspace. Knowledge entries are text documents that can be used as references or information sources. List only shows the available items and a short description for the actual knowledge use the get by id call.

List all knowledge entries in the workspace. Knowledge entries are text documents that can be used as references or information sources. List only shows the available items and a short description for the actual knowledge use the get by id call.

No parameter schema in public metadata yet.

get_knowledgeGet details of a specific knowledge entry by ID. Knowledge entries are text documents that can be used as references or information sources.1 params

Get details of a specific knowledge entry by ID. Knowledge entries are text documents that can be used as references or information sources.

Parameters* required
knowledgeIdstring
The ID of the knowledge entry to retrieve
delete_knowledgeDelete a knowledge entry by ID.1 params

Delete a knowledge entry by ID.

Parameters* required
knowledgeIdstring
The ID of the knowledge entry to delete
create_feedbackCreate a new feedback entry. Feedback represents raw, unprocessed feedback from users that can later be analyzed and converted into insights.5 params

Create a new feedback entry. Feedback represents raw, unprocessed feedback from users that can later be analyzed and converted into insights.

Parameters* required
sourcestring
The source of the feedback (e.g., 'Typeform', 'Slack', 'Manual', 'Email', etc.)
contentstring
The original raw feedback content from the user
sentimentScorenumber
Sentiment score from -1 (negative) to 1 (positive)
sentimentCategorystring
Sentiment classification category: 'Positive', 'Neutral', or 'Negative'one of Positive · Neutral · Negative
sentimentConfidencenumber
Confidence in sentiment analysis (0-1)
list_feedbackList all feedback entries in the workspace. Feedback entries are raw customer feedback that can be processed into insights.

List all feedback entries in the workspace. Feedback entries are raw customer feedback that can be processed into insights.

No parameter schema in public metadata yet.

get_feedbackGet details of a specific feedback entry by ID. Feedback entries are raw customer feedback.2 params

Get details of a specific feedback entry by ID. Feedback entries are raw customer feedback.

Parameters* required
feedbackIdstring
The ID of the feedback entry to retrieve
relationshipsstring
Show insights that were generated from this feedback.one of insights
delete_feedbackDelete a feedback entry by ID.1 params

Delete a feedback entry by ID.

Parameters* required
feedbackIdstring
The ID of the feedback entry to delete
create_insightCreate a new insight entry. An insight is customer-generated feedback about your product, often from reviews, surveys, or questionnaires.3 params

Create a new insight entry. An insight is customer-generated feedback about your product, often from reviews, surveys, or questionnaires.

Parameters* required
typestring
The type of insight: 'Feedback' for customer feedback, 'Bug' for bug reports, or 'FeatureRequest' for feature requests.one of Feedback · Bug · FeatureRequest
titlestring
A brief title summarizing the insight
descriptionstring
A short description of the insight
list_insightsList all insights for the workspace. These insights are gathered from various sources, created by customers, and help understand how to improve the business.

List all insights for the workspace. These insights are gathered from various sources, created by customers, and help understand how to improve the business.

No parameter schema in public metadata yet.

get_insightGet details of a specific insight entry by ID. Insight entries are text documents that can be used as references or information sources.2 params

Get details of a specific insight entry by ID. Insight entries are text documents that can be used as references or information sources.

Parameters* required
insightIdstring
The ID of the insight entry to retrieve
relationshipsarray
Show other entities that this insight is related to.
delete_insightDelete an insight entry by ID.1 params

Delete an insight entry by ID.

Parameters* required
insightIdstring
The ID of the insight entry to delete
similarity_searchPerform a semantic similarity search across the workspace. This searches through knowledge documents, feedback insights, opportunities, and solutions to find content similar to your query. Each result will contain a nodeId or an id. These can be used to retrieve the full conte...2 params

Perform a semantic similarity search across the workspace. This searches through knowledge documents, feedback insights, opportunities, and solutions to find content similar to your query. Each result will contain a nodeId or an id. These can be used to retrieve the full conte...

Parameters* required
querystring
The search query string
filtersarray
Filters to apply to the search. Options are: knowledge-base for knowledge documents, insights for insights, opportunities for opportunities, solutions for solutions.
view_strategy_contextShow an entity in its product strategy tree — displays the entity, its parent chain, and direct children in a rich visual UI. ALWAYS use this tool when the user asks about strategy, prioritisation, reasoning, context, positioning, or 'why' behind any entity. Use it when the us...2 params

Show an entity in its product strategy tree — displays the entity, its parent chain, and direct children in a rich visual UI. ALWAYS use this tool when the user asks about strategy, prioritisation, reasoning, context, positioning, or 'why' behind any entity. Use it when the us...

Parameters* required
entityIdstring
The ID of the entity to view. Not required for workspace (uses current workspace).
entityTypestring
The type of entity to viewone of workspace · goal · opportunity · solution · insight · feedback
view_roadmapShow the product roadmap — solutions organized by time horizon (Now/Next/Later) with goal context. Use this when the user asks about the roadmap, what's planned, what's coming next, priorities, or wants to see an overview of solutions being built.3 params

Show the product roadmap — solutions organized by time horizon (Now/Next/Later) with goal context. Use this when the user asks about the roadmap, what's planned, what's coming next, priorities, or wants to see an overview of solutions being built.

Parameters* required
goalIdstring
Filter to solutions linked to this goal
showResolvedboolean
Include completed/cancelled solutionsdefault: false
statusFilterarray
Filter by solution statuses

Squad MCP Server

smithery badge

A remote MCP server that brings Squad — the AI product feedback intelligence platform — directly into your AI workflows. Connect Squad to Claude, ChatGPT, or any MCP-compatible AI assistant to turn raw user feedback into signals, insights, actions, and decision briefs without context switching.

Squad continuously ingests feedback, clusters it into signals, distils it into insights, and links it to the actions and goals that move your product forward. The MCP server exposes that same intelligence — read the evidence behind a decision, capture new feedback, and generate decision briefs from your assistant.

🚀 Quick Start

For Users

Connect Squad to your AI assistant in seconds:

Claude Code:

claude mcp add --transport http squad https://mcp.meetsquad.ai/mcp

On first use, you'll be prompted to authenticate via OAuth in your browser.

Other MCP Clients:

Connect using https://mcp.meetsquad.ai/mcp — OAuth configuration is automatically discovered via the server's .well-known/oauth-protected-resource metadata (which points clients at PropelAuth as the authorization server).

📖 Usage Examples

See USAGE_EXAMPLES.md for detailed real-world examples. A few things you can ask:

  • Triage feedback — "Capture this support ticket in Squad and tell me if it's a known theme."
  • Weekly review — "Run my weekly product review: what changed and what needs deciding?"
  • Ground the evidence — "Show me the customer signals behind insight IN-42."
  • Draft a decision brief — "Generate a decision brief for action AC-12."
  • Search everything — "Find all feedback related to onboarding friction."
  • Ground a ticket — "Pull the customer evidence behind AC-7 before I build it."

Squad entities are referenced by short display IDs so the assistant can cite its evidence:

PrefixEntityPrefixEntity
SI-SignalGL-Goal
CL-ClusterRQ-Research question
IN-InsightOP-Decision brief
AC-ActionDC-Document

✨ Available Tools

The server exposes ~35 tools. Write tools require a token minted with the write:workspace scope; read tools only need read:workspace.

CategoryToolsPurpose
Workspacelist_workspaces, select_workspace, get_workspace_overview, update_workspace, list_membersOrient in and configure a workspace
Searchsearch, get_entitySemantic search and fetch any entity by ID
Evidencelist_signals, find_similar_signals, list_clusters, get_cluster, list_insightsExplore signals, clusters, and insights
Actionslist_actions, get_action_context, update_action, update_action_statusTrack and update product work
Strategylist_goals, create_goal, update_goal, list_research_questions, create_research_question, update_insight, dismiss_signal, get_activityManage goals, research questions, and activity
Knowledgelist_documents, create_document, update_documentStore research, references, and notes
Decision briefslist_one_pagers, generate_one_pager, update_one_pager_statusGenerate and manage one-page decision briefs
Ingestingest_signalCapture new feedback as a signal (with dedup)
Integrationslist_integrationsSee connected feedback sources

Prompts

Ready-made workflows exposed as MCP prompts:

  • triage-feedback — check for duplicates, ingest a piece of feedback, and report where it landed.
  • weekly-product-review — what changed, what the evidence says, and what needs deciding.
  • draft-decision-brief — generate a decision brief from an action or insight and walk it to a readable draft.
  • ground-this-ticket — for coding agents: pull the customer evidence behind a piece of work before building it.

Resources

Pin these so strategy questions need no tool calls:

  • squad://workspace/context — the current workspace's mission and product context.
  • squad://goals — the workspace's strategic goals with importance rankings.

Tool Capabilities

  • ✅ Safety annotations (readOnlyHint / destructiveHint) on every tool
  • ✅ Structured Zod input schemas
  • ✅ User- and workspace-isolated data access via OAuth
  • ✅ Scope-gated writes (write:workspace)

🏗️ Architecture

┌─────────────┐         OAuth          ┌──────────────┐
│  Claude /   │ ◄────────────────────► │  PropelAuth  │
│  ChatGPT    │    (Authentication)     │   (IdP)      │
└─────────────┘                         └──────────────┘
       │
       │ HTTPS + Bearer Token
       ▼
┌──────────────────────────────────────────────┐
│  Squad MCP Server                            │
│  ┌────────────────────────────────────────┐  │
│  │  OAuth → introspect + verify token     │  │
│  │  JWT minting → service credentials     │  │
│  │  Redis → sessions + stream state       │  │
│  │  MCP handler → tools / prompts / res.  │  │
│  │  PostHog → tool-call telemetry         │  │
│  └────────────────────────────────────────┘  │
└──────────────────────────────────────────────┘
       │
       │ Squad API Calls (minted JWT)
       ▼
┌──────────────┐
│  Squad API   │
└──────────────┘

The server is built on mcp-use and talks to the Squad platform API over GraphQL. Sessions and stream state are backed by Redis so the deployment is horizontally scalable. Backend types are generated from a committed GraphQL schema snapshot (see GraphQL codegen).

🛠️ Development

This repository contains the source code for the Squad MCP remote server.

Prerequisites

  • Node.js 22+
  • Yarn
  • Nix (optional, for a reproducible dev environment via flake.nix)
  • PropelAuth credentials (OAuth 2.1 client + backend API key)
  • Redis (optional locally; falls back to in-memory sessions)

Local Setup

# Clone repository
git clone https://github.com/the-basilisk-ai/squad-mcp.git
cd squad-mcp

# Install dependencies
yarn install

# Configure environment
cp .env.example .env
# Edit .env with your PropelAuth credentials (and SQUAD_ENV=dev to target the dev platform)

# Start development server with hot reload
yarn dev

# Server available at http://localhost:3232

Environment Variables

VariableRequiredPurpose
PROPELAUTH_CLIENT_ID / PROPELAUTH_CLIENT_SECRET✅OAuth 2.1 client credentials for token introspection
PROPELAUTH_API_KEY✅Backend integration key for minting service JWTs
SQUAD_ENVdev or production (default production) — selects auth/API/app URLs
PORT / MCP_URL / BASE_URIServer port and externally-advertised base URL
REDIS_URLRedis connection for deploy-safe sessions (in-memory if unset)
SQUAD_GRAPHQL_URLOverride the Squad GraphQL endpoint (also used by codegen)
POSTHOG_API_KEY / POSTHOG_HOSTEnable tool-call telemetry
LOG_LEVELLogger verbosity

Available Commands

yarn dev                # Start dev server with hot reload (mcp-use)
yarn build              # Build the server (mcp-use)
yarn start              # Start the built server
yarn deploy             # Deploy via mcp-use
yarn test               # Run unit tests (vitest)
yarn format             # Lint/format check (biome)
yarn format:fix         # Auto-fix lint/format issues
yarn codegen            # Regenerate GraphQL types from schema.graphql
yarn codegen:check      # Fail if generated GraphQL types are stale

Testing the Server

# Check health
curl http://localhost:3232/health

# Check OAuth discovery
curl http://localhost:3232/.well-known/oauth-protected-resource

# Test with the built-in inspector
yarn dev   # then open the inspector and connect to http://localhost:3232/mcp

Project Structure

squad-mcp/
├── server.ts                   # MCP server entry point (OAuth, Redis, tool/prompt/resource registration)
├── server.json                 # MCP registry metadata (see MCP_REGISTRY.md)
├── schema.graphql              # Committed snapshot of the Squad platform GraphQL schema
├── codegen.ts                  # GraphQL Code Generator config
├── src/
│   ├── tools/                  # Tool implementations, grouped by surface
│   │   ├── registry.ts         # Single registration path (annotations, errors, telemetry)
│   │   ├── workspace.ts        # list/select workspaces, overview, members
│   │   ├── search.ts           # semantic search
│   │   ├── get-entity.ts       # fetch any entity by display ID / UUID
│   │   ├── evidence.ts         # signals, clusters, insights
│   │   ├── actions-read.ts     # list actions, action context
│   │   ├── actions-write.ts    # update actions + status
│   │   ├── strategy-read.ts    # goals, research questions, activity
│   │   ├── strategy-write.ts   # create/update goals, insights, dismiss signals
│   │   ├── research-write.ts   # create research questions
│   │   ├── knowledge.ts        # documents + decision briefs (one-pagers)
│   │   ├── ingest.ts           # ingest new signals
│   │   └── integrations.ts     # list connected sources
│   ├── prompts/                # MCP prompt workflows
│   ├── resources/              # MCP resources (workspace context, goals)
│   ├── gql/                    # Generated GraphQL types (yarn codegen)
│   ├── graphql/                # GraphQL operation documents
│   ├── helpers/                # OAuth, token minting, workspace selection, KV/Redis
│   └── lib/                    # Squad API client, logger, telemetry
├── railway.toml                # Railway deployment config
└── .env.example                # Environment template

🏭 Production Deployment

This is a hosted service maintained by Squad. Users connect via OAuth — no self-hosting required.

Architecture notes (for contributors):

  • Deployed on Railway with a /health readiness check
  • Redis-backed sessions and stream state for horizontal scalability
  • Follows the MCP specification for streamable HTTP transport

💬 Support

Need help with the Squad MCP server?

  • Email: support@meetsquad.ai
  • Documentation:
    • Squad MCP Guide — complete setup and integration guide
    • USAGE_EXAMPLES.md — real-world usage examples
  • Issues: GitHub Issues — bug reports and feature requests
  • Privacy Policy: meetsquad.ai/privacy-policy
  • Squad Platform: meetsquad.ai

🤝 Contributing

Contributions welcome! Pre-commit hooks run biome and vitest automatically. Please ensure:

  • yarn format passes (biome)
  • yarn build compiles without errors
  • yarn test passes
  • yarn codegen:check passes if you touched GraphQL operations
  • All tools include safety annotations

📄 License

MIT

🔗 Links

  • Squad MCP Documentation — complete setup and integration guide
  • Squad Platform
  • MCP Specification
  • Issue Tracker

GraphQL codegen

Backend access is typed via GraphQL Code Generator. schema.graphql is a committed snapshot of the Squad platform API schema; src/gql/ is generated from it plus the operation documents in src/graphql/.

  • Refresh the snapshot: copy packages/graphql/src/schema/generated.graphql from the API repo over schema.graphql (or set SQUAD_GRAPHQL_URL to introspect a live endpoint), then run yarn codegen.
  • CI runs yarn codegen:check and fails when src/gql/ is stale.
Featured
CodeRabbit
CodeRabbit
AI writes the code. CodeRabbit catches the slop.
Try For Free →
AppSignal
AppSignal
Monitor with ease. Code with confidence.
Start Free Trial →
AI notepad for back-to-back meetings
AI notepad for back-to-back meetings
Notes, actions and memory. Without a meeting bot. First month 100% off.
Download for free →
Keep your Mac awake
Keep your Mac awake
Keep your Mac awake while Claude Code and 40+ AI agents run. Sleeps when they're idle.
One time payment $9 →
Email for Agents: Free tier availableEmail for Agents: Free tier available
Email for Agents: Free tier available
Give your AI agent a complete email layer—sending, inbound inboxes, and sandbox testing.
Get 4K emails/month free →
Context.devContext.dev
Context.dev
Integrate web data into your AI product. One API to scrape website & brand data.
Get API Key Now →
CodeScene MCP ServerCodeScene MCP Server
CodeScene MCP Server
Your agent targets a perfect 10 Code Health score. Deterministic. Every commit.
Try For Free →
Make your agent a DeFi expert
Make your agent a DeFi expert
Agent, run crypto. Access onchain data & trade routes via 1inch.
Install now →
Registryactive
TransportHTTP
UpdatedFeb 12, 2026
View on GitHub