Squad MCP Server

Squad mcp mcp server connects Squad MCP to AI assistants that speak the Model Context Protocol. 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.

What Squad MCP does

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.

Tools it exposes

Once connected, the assistant can call these 14 tools directly:

• Prefix — Entity
• SI- — Signal
• IN- — Insight
• AC- — Action
• CL- — Cluster
• Category — Tools
• Workspace — list_workspaces, select_workspace, get_workspace_overview, update_workspace, list_members
• Search — search, get_entity
• Evidence — list_signals, find_similar_signals, list_clusters, get_cluster, list_insights
• Actions — list_actions, get_action_context, update_action, update_action_status
• Strategy — list_goals, create_goal, update_goal, update_insight, dismiss_signal, get_activity
• Knowledge — list_documents, create_document, update_document
• Ingest — ingest_signal
• Integrations — list_integrations

Installing the squad mcp mcp server

Setup follows the standard MCP pattern: clone or install the server, then register it in your client's configuration file and restart the client. The configuration snippets on this page cover Claude Desktop, Claude Code and Cursor.

Configuration

Before the server will start you need to supply 7 environment variables: PROPELAUTH_CLIENT_ID, PROPELAUTH_CLIENT_SECRET, PROPELAUTH_API_KEY, REDIS_URL, SQUAD_GRAPHQL_URL, POSTHOG_API_KEY, POSTHOG_HOST. Keep credentials in your client's env block or a secrets manager rather than committing them.

Requirements

• Node.js 22+ - pnpm - 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)

Where it fits

Developer-tool servers are usually the first ones people connect, because they turn "help me with this code" into an assistant that can actually read the repo and act on it. Squad MCP sits in that group, and the shape of its toolset — Prefix, SI-, IN- among others — tells you what it is really for. Worth comparing against the other developer tools servers in this directory before you commit to one, since several overlap in scope but differ sharply in setup cost and permissions.

Practical notes

• This is a hosted server — you point your client at an endpoint rather than running a local process, so there is nothing to keep updated on your machine.
• It will not start until its required credentials are present, so set those before wondering why the tools never appear.
• With 14 tools exposed, expect a noticeable bump in prompt size — disable it in projects that never use Squad MCP.
• Maintained by the-basilisk-ai.
• MCP clients ask for confirmation before each tool call by default. Keep that on while you learn what the squad mcp mcp server actually does with your data.
• Every entry in this directory is reviewed by hand before it goes live, and details are checked against the project's own documentation.