Squad AI

by the-basilisk-ai

245 downloads
Not rated
GitHub

About

Product‑discovery and strategy platform integration. Create, query and update opportunities, solutions, outcomes, requirements and feedback from any MCP‑aware LLM.

Details

Author
the-basilisk-ai
Downloads
245
Categories
Productivity, Community, Other, AI

- Exposes tools for opportunities, solutions, outcomes, requirements, knowledge, workspaces, and feedback.
- Outcome‑driven roadmaps tie every feature to a measurable business goal.
- AI‑powered discovery surfaces high‑impact opportunities from raw feedback.
- One‑click documentation generates PRDs, BDD requirements, and test cases.
- Automates the grunt‑work of product management with an LLM co‑pilot.

Setting up with Highlight

This MCP is not yet compatible with Highlight’s one-click setup. However, you can still use it with Highlight by following these steps:

  1. Download and install Highlight from highlightai.com/download
  2. Navigate to the plugins tab and select "Add Custom Plugin"
  3. Configure the plugin with the settings below
    Plugin Name Squad AI
    Command (node, npx, python, etc.)

    Please refer to the README for specific instructions on how to obtain API keys or other required environment variables.

  4. Enable "Start Automatically" if you want the plugin to start when Highlight launches

From the repository

1. Get an API key from meetsquad.ai (Settings → API Keys).
2. Run the server either as a stand‑alone executable (./squad‑mcp) or via Docker (docker run --rm -i -e SQUAD_API_KEY=<your‑key> mcp/meet-squad).
3. Register the server with an MCP‑enabled client (e.g. Claude Desktop, Cursor, or Glama) by adding the command, args, and environment variables to the client config.

Claude Desktop / Cursor

Paste into your MCP client config file to install this server.

{
    "mcpServers": {
        "squad\u202fai": {
            "meet-squad": {
                "command": "docker",
                "args": [
                    "run",
                    "-i",
                    "--rm",
                    "-e",
                    "SQUAD_API_KEY",
                    "mcp/meet-squad"
                ],
                "env": {
                    "SQUAD_API_KEY": "YOUR_API_KEY_HERE"
                }
            }
        }
    }
}

McpServers

{
    "meet-squad": {
        "command": "docker",
        "args": [
            "run",
            "-i",
            "--rm",
            "-e",
            "SQUAD_API_KEY",
            "mcp/meet-squad"
        ],
        "env": {
            "SQUAD_API_KEY": "YOUR_API_KEY_HERE"
        }
    }
}

A remote MCP server that bringsSquad— 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 intosignals, distils it intoinsights, and links it to theactionsandgoalsthat 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.

Connect Squad to your AI assistant in seconds:

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.

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

SeeUSAGE_EXAMPLES.mdfor 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 shortdisplay IDsso the assistant can cite its evidence:

The server exposes ~35 tools. Write tools require a token minted with thewrite:workspacescope; read tools only needread:workspace.

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.

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.

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

┌─────────────┐ 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 onmcp-usev2 and talks to the Squad platform API overGraphQL. Each request is served statelessly: the MCP layer holds no session, and every call re-introspects its own bearer token.Redisstores 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 (seeGraphQL codegen).

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

- Node.js 22+
- pnpm
- Nix (optional, for a reproducible dev environment viaflake.nix)
- PropelAuth credentials (OAuth 2.1 client + backend API key)
- Redis (optional locally; workspace selection falls back to in-memory)

# 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
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
# 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 pnpm dev # then open the inspector and connect to http://localhost:3232/mcp
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 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, activity │ │ ├── strategy-write.ts # create/update goals, insights, dismiss signals │ │ ├── knowledge.ts # documents + briefs │ │ ├── ingest.ts # ingest new signals │ │ └── integrations.ts # list connected sources │ ├── prompts/ # MCP prompt workflows │ ├── resources/ # MCP resources (workspace context, goals) │ ├── gql/ # Generated GraphQL types (pnpm codegen) │ ├── graphql/ # GraphQL operation documents │ ├── helpers/ # OAuth provider, token minting, workspace selection, KV/Redis │ └── lib/ # Squad API client, logger, telemetry ├── railway.toml # Railway deployment config └── .env.example # Environment template

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

- Deployed on Railway with a/healthreadiness check
- Stateless request handling, with Redis holding the per-user workspace selection and token cache, so instances scale horizontally
- Follows the
MCP specificationfor streamable HTTP transport

- Email:support@meetsquad.ai
- Documentation:

- Squad MCP Guide— complete setup and integration guide
-
USAGE_EXAMPLES.md— real-world usage examples

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

- pnpm formatpasses (biome)
- pnpm buildcompiles without errors
- pnpm testpasses
- pnpm codegen:checkpasses if you touched GraphQL operations
- All tools include safety annotations

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

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

- Refresh the snapshot: copypackages/graphql/src/schema/generated.graphqlfrom the API repo overschema.graphql(or setSQUAD_GRAPHQL_URLto introspect a live endpoint), then runpnpm codegen.
- CI runspnpm codegen:checkand fails whensrc/gql/is stale.

AnkiConnect MCP server for interacting with Anki via AnkiConnect.

An MCP Server Integration with Apple Shortcuts

Add smart Backup ability to coding agents like Windsurf, Cursor, Cluade Coder, etc

This server enables LLMs to use calculator for precise numerical calculations.

A CalDAV MCP server to expose calendar operations as tools for AI assistants.

MCP server for easy access to education data through your Canvas LMS instance.

Tools to the query and execute of Dify workflows

Excel manipulation including data reading/writing, worksheet management, formatting, charts, and pivot table

No reviews yet — be the first

Sign in to leave a review

Use Google, GitHub, or an email account so ratings stay tied to real people.

Email sign in

No reviews posted yet.