Squad

Name: Squad
Author: the-basilisk-ai

by the-basilisk-aiversion 4.3.3i★ –iRuns in the cloud

Registry nameai.meetsquad/squad

Install

Overview

Description from the maker (original English)

Decision intelligence for product teams. Turn scattered feedback into signal you can act on.

PopNx MCP’s three pillars

These three are never merged into one score: opinions, measurements and popularity are different things.

User voiceiNo reviews yetReviews open together with accounts in a later step
Our basic checksi2 of 3 passedChecked from public information; code not scanned yet
UsageiNot measured yet★ –

What you can do with it

We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.

Connection: Runs in the cloud
Transport: Streamable HTTP
Category: Other

Install

Pick the AI app you use, then copy the settings.

Before you install

Basic checks: 2 of 3 passed
Runs on the maker’s server: what you ask it goes through their server.
The registry lists no key to fill in.

You need

Runs in the cloudNothing to install; it connects over the internet

Which app do you use?

ClaudeClaude CodeCursorVS CodeChatGPT

Pick your app above. We remember it, so next time the button says “Install in …”.

Works in Claude on the web, desktop and mobile:

Open Settings → Connectors
Press Add custom connector
Paste the address below and press Add
If it asks you to sign in, sign in with the maker

https://mcp.meetsquad.ai/mcp

Run this in your terminal

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

Open in Cursor

Or copy the settings yourself

Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json

{
  "mcpServers": {
    "squad": {
      "url": "https://mcp.meetsquad.ai/mcp"
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

Open in VS Code

Or copy the settings yourself

Paste into .vscode/mcp.json in your project

{
  "servers": {
    "squad": {
      "type": "http",
      "url": "https://mcp.meetsquad.ai/mcp"
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

ChatGPT connects only to servers on the internet:

Open ChatGPT on the web → Settings → Connectors (Apps)
Press Create or Add (some plans need Developer mode under Advanced first)
Paste the address below, give it a name and save
If it asks you to sign in, sign in with the maker

https://mcp.meetsquad.ai/mcp

Menu names can differ slightly by plan and over time.

Your choice stays on this device in a cookie; no account needed.

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

What it can do

The server asks you to sign in before it lists its tools.

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 6, 2026

! Caution
Maker matches the repo
The publisher (meetsquad.ai) is not the repo owner (the-basilisk-ai); someone else may have listed it
… Not checked yet
Still maintained
We have not read this repo from GitHub yet
… Not checked yet
Has a licence
We have not read this repo from GitHub yet
✓ Pass
Endpoint responds
Responded in 690 ms (HTTP 401)
✓ Pass
Sign-in with OAuth
Declares OAuth sign-in, so your AI app can take you to log in
… Not checked yet
No hidden instructions in tool descriptions
Not checked yet; we read the tool list when we check the endpoint

Compared with others in Otheri

More stars than 0% of the other 32505 servers in this category
Published to the registry more recently than 89% of the other 32505 servers in this category
Basic checks equal to or better than 37% of the other 32505 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is Squad safe?

It passed 2 of 3 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.

What keys or codes does it need?

The registry does not list a required key, though some servers ask you to sign in on first use.

Does it run on my computer or in the cloud?

It runs in the maker’s cloud. Connect over the internet with nothing to install, but what you send passes through the maker’s servers.

Is it still maintained?

The GitHub repo last changed –, and the latest version (4.3.3) reached the registry 4 days ago.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. It connects by URL, so apps that accept remote MCP servers work too, such as ChatGPT in developer mode.

What can I use instead?

In the same category: Spec Driven Development, Remote Desktop Commander, topo^alpin

Alternatives

Servers in the same category from other makers, sorted by stars.

Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

Spec Driven Development

by formulahendry

MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.

Runs on your computer★ 440MITUpdated 14 months ago

Install

Remote Desktop Commander

by desktop-commander

Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.

Runs in the cloud★ 211Updated yesterday

Install

topo^alpin

by topoalpin.app

Avalanche bulletins and mountain weather forecasts for any place in the Alps.

Runs in the cloudUpdated today

Install

README from the maker

Open the README

Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.

Squad MCP Server

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 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 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](./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 brief — "Generate a 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:

Prefix	Entity	Prefix	Entity
`SI-`	Signal	`GL-`	Goal
`IN-`	Insight	`BR-`	Brief
`AC-`	Action	`DC-`	Document
`CL-`	Cluster

Tools

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

list_workspaces — List every organisation and workspace you can access, with the current selection marked.
select_workspace — Select which organisation and workspace subsequent tools operate on.
get_workspace_overview — One-call orientation: mission and description, top goals, recent signal activity, evidence-chain health, and open work counts.
update_workspace — Update the current workspace's name, description, mission statement or logo.
list_members — People in the current organisation with their user IDs.
search — Keyword search across signals, insights, actions, goals, documents and clusters.
get_entity — Fetch any entity by display ID (SI-1, IN-1, AC-1, GL-1, BR-1, DC-1, CL-1) or UUID. Also how you check on async work.
list_signals — Browse raw feedback signals with filters for source, type, sentiment, cluster and date range.
find_similar_signals — Semantically related signals for a given signal — "has anyone else said this?".
list_clusters — Browse signal clusters (recurring themes in feedback) with sizes and labels.
get_cluster — A cluster's label, stats, member signals and linked insights.
list_insights — Browse distilled insights ranked by combined score, with category/score/status filters or scoped to a goal.
list_actions — Ranked actions (what the evidence says to do next) filtered by status, assignee, priority or parent insight.
get_action_context — Everything needed to execute an action in one call: the action, the parent insight, the customer evidence behind it, and the goals it serves.
update_action — Edit an action's priority, effort, category or notes; assign it; or link it to an insight or brief.
update_action_status — Move an action through its lifecycle: start, complete, dismiss or snooze.
list_goals — Strategic goals ordered by importance.
create_goal — Create a strategic goal.
update_goal — Update a goal's title, description or importance.
update_insight — Curate an insight: set category or status, and link/unlink the goal it supports.
dismiss_signal — Permanently remove a signal from the workspace (noise, spam, or mis-ingested content).
get_activity — The workspace change feed (humans and Squad agents), newest first.
list_documents — Browse workspace knowledge documents (and briefs) with their paths and tags.
create_document — Create a knowledge document from markdown (research summaries, meeting notes, analyses).
update_document — Replace a document's markdown body and/or title, and manage tags.
list_briefs — Briefs with their status (building/draft/in_review/finalised/failed) and recommendation.
generate_brief — Kick off AI generation of a brief from an action or insight.
update_brief_status — Move a brief through its review lifecycle: draft, in_review, or finalised.
ingest_signal — Pipe user feedback into the evidence chain (1–50 items, deduplicated server-side).
list_integrations — Connected feedback sources for this workspace and their sync health.

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 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 → workspace selection + tokens │ │ │ │ MCP handler → tools / prompts / res. │ │ │ │ PostHog → tool-call telemetry │ │ │ └────────────────────────────────────────┘ │ └──────────────────────────────────────────────┘ │ │ Squad API Calls (minted JWT) ▼ ┌──────────────┐ │ Squad API │ └──────────────┘

The server is built on mcp-use v2 and talks to the Squad platform API over GraphQL. Each request is served statelessly: the MCP layer holds no session, and every call re-introspects its own bearer token. Redis stores the durable per-user state (workspace selection and minted-token cache), so any instance can serve any request. 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+
pnpm
Nix (optional, for a reproducible dev environment via flake.nix)
PropelAuth credentials (OAuth 2.1 client + backend API key)
Redis (optional locally; workspace selection falls back to in-memory)

Local Setup

# Clone repository

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

Install dependencies

pnpm 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

pnpm dev

Server available at http://localhost:3232

Environment Variables

Variable	Required	Purpose
`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_ENV`		`dev` or `production` (default `production`) — selects auth/API/app URLs
`PORT` / `MCP_URL` / `BASE_URI`		Server port and externally-advertised base URL
`REDIS_URL`		Redis connection for deploy-safe workspace selection and token cache (in-memory if unset). Deployed as the restricted `mcp` user, see Redis access control
`SQUAD_GRAPHQL_URL`		Override the Squad GraphQL endpoint (also used by codegen)
`POSTHOG_API_KEY` / `POSTHOG_HOST`		Enable tool-call telemetry
`LOG_LEVEL`		Logger verbosity

Available Commands

pnpm dev                # Start dev server with hot reload (mcp-use)

pnpm build # Build the server (mcp-use) pnpm start # Start the built server pnpm deploy # Deploy via mcp-use pnpm test # Run unit tests (vitest) pnpm format # Lint/format check (biome) pnpm format:fix # Auto-fix lint/format issues pnpm codegen # Regenerate GraphQL types from schema.graphql pnpm 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

Check server-card discovery (SEP-2127)

curl -H 'Accept: application/mcp-server-card+json' \ http://localhost:3232/mcp/server-card curl http://localhost:3232/.well-known/ai-catalog.json

Test with the built-in inspector

pnpm dev # then open the inspector and connect to http://localhost:3232/mcp

Project Structure

squad-mcp/

├── server.ts # MCP server entry point (OAuth, 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 b

Only the beginning is shown; read the rest in the repo

Squad

Overview

PopNx MCP’s three pillars

What you can do with it

Install

Before you install

What it can do

Basic checksi

Maker matches the repo

Still maintained

Has a licence

Endpoint responds

Sign-in with OAuth

No hidden instructions in tool descriptions

Compared with others in Otheri

Common questions

Alternatives

Spec Driven Development

Remote Desktop Commander

topo^alpin

README from the maker

Squad MCP Server

🚀 Quick Start

For Users

📖 Usage Examples

Tools

Prompts

Resources

Tool Capabilities

🏗️ Architecture

🛠️ Development

Prerequisites

Local Setup

Install dependencies

Configure environment

Edit .env with your PropelAuth credentials (and SQUAD_ENV=dev to target the dev platform)

Start development server with hot reload

Server available at http://localhost:3232

Environment Variables

Available Commands

Testing the Server

Check OAuth discovery

Check server-card discovery (SEP-2127)

Test with the built-in inspector

Project Structure