# Squadai > One config. Every AI agent. Zero drift. Idempotent setup for OpenCode, Claude Code, Cursor, Windsurf, and Copilot. - **Type:** MCP server - **Install:** `agentstack add mcp-pedromosquera-squadai` - **Verified:** Pending review - **Seller:** [PedroMosquera](https://agentstack.voostack.com/s/pedromosquera) - **Installs:** 0 - **Category:** [Developer Tools](https://agentstack.voostack.com/c/developer-tools) - **Latest version:** 0.1.0 - **License:** MIT - **Upstream author:** [PedroMosquera](https://github.com/PedroMosquera) - **Source:** https://github.com/PedroMosquera/squadai ## Install ```sh agentstack add mcp-pedromosquera-squadai ``` Requires the [AgentStack CLI](https://agentstack.voostack.com/docs/cli). Works with Claude Code, Cursor, and any MCP-compatible agent. ## About # SquadAI One local control plane for setup, context, memory, permissions, model usage, and workflows across every coding agent you use. [](https://github.com/PedroMosquera/squadai/actions) [](go.mod) [](LICENSE) --- If you've ever opened a repo and had your AI agent lose the thread — project memory, standards, MCP servers, permissions, model choices, and workflow habits — that's the problem squadai solves. You declare the local operating model once in `.squadai/project.json`, and `squadai apply` writes the right native files for every supported agent: OpenCode, Claude Code, Cursor, Windsurf, VS Code Copilot, and Pi. SquadAI is solo-first: it should make your daily agent sessions predictable on one machine and one repo. The same primitives also scale to teams through policy, verification, backup, rollback, and drift checks. --- ## Install ```sh # macOS / Linux via Homebrew (recommended) brew install PedroMosquera/tap/squadai # or via curl curl -sSL https://raw.githubusercontent.com/PedroMosquera/squadai/main/scripts/install.sh | sh # or from source go install github.com/PedroMosquera/squadai/cmd/squadai@latest ``` Linux `.deb` and `.rpm` packages are published on every [release](https://github.com/PedroMosquera/squadai/releases/latest) for Debian/Ubuntu and Fedora/RHEL users. Windows binaries (zip) are also published there. --- ## Getting started The fastest path is the interactive TUI wizard: ```sh cd your-project squadai ``` Running `squadai` with no arguments opens a terminal UI that walks you through choosing a methodology, enabling MCP servers, and selecting plugins. At the end it asks to apply the config. That's it — your agents are configured. If you'd rather script it: ```sh squadai init --methodology tdd # writes .squadai/project.json squadai apply # installs agent files for all detected editors squadai doctor # sanity-check everything looks right ``` Use a daily-driver preset when you want a ready-made operating model: ```sh squadai init --preset=solo-minimal # lightweight conventional workflow squadai init --preset=solo-power # TDD workflow with local memory/context defaults squadai init --preset=team-standard # shared governance-friendly team baseline squadai init --preset=enterprise-locked # strict SDD-oriented baseline ``` To see what `apply` would change before committing: ```sh squadai plan --dry-run squadai diff ``` --- ## How it works When you run `squadai init`, it detects which AI agents are installed on the current machine and writes `.squadai/project.json` — a config that says which methodology to use, which roles exist, which context profile is active, how memory works, and which components each agent should get. `squadai apply` reads that config, figures out which files each agent needs in its native format, and writes them. For Claude Code it updates `CLAUDE.md`. For OpenCode it writes `AGENTS.md` and individual agent files under `.opencode/agents/`. For Cursor it writes `.cursor/rules/` and `.cursor/agents/`. It never touches content outside its own marker blocks, so any customizations you've made in those files stay put. The result is a team where everyone's agents have: - **A methodology** — TDD (6 roles), SDD (8 roles), or Conventional (4 roles), each with an orchestrator that delegates to specialist sub-agents - **Consistent coding standards** — auto-detected by language (Go, TypeScript, Python, Rust, and [12 more](docs/architecture.md)) - **Shared MCP servers** — Context7 is enabled by default; others are opt-in - **Native memory defaults** — local-first project memory metadata with `docs/memory/` export/import compatibility - **Context profiles** — built-in profiles for default, debug, feature, review, docs, incident, and cheap sessions - **Usage controls** — approximate session/daily token budgets and enforcement mode metadata - **Model routing metadata** — cheap, balanced, and premium profile labels, plus methodology role overrides - **Visual branding** — an ASCII-art banner injected into agent files so devs see SquadAI is active at session start (disable with `squadai apply --no-brand`) ### Adapters and delegation Different agents handle sub-agents differently. squadai adapts: | Agent | Config file | Sub-agent strategy | |-------|-------------|-------------------| | OpenCode | `AGENTS.md` | Native agent files in `.opencode/agents/` | | Claude Code | `CLAUDE.md` | Task tool injection (prompt-based delegation) | | Cursor | `.cursor/rules/squadai.mdc` | Native agent files in `.cursor/agents/` | | Windsurf | `.windsurf/rules/squadai.md` | Solo all-in-one prompt + workflow files | | VS Code Copilot | `.github/copilot-instructions.md` | Solo all-in-one prompt | | Pi | `~/.pi/agent/AGENTS.md` | Native agent files in `~/.pi/agent/agents/` + prompts in `~/.pi/agent/prompts/` | --- ## Per-project refinement (`/squadai-init`) Agent files installed by `squadai apply` contain placeholder blocks. `/squadai-init` is a command you run inside your AI agent to fill those placeholders with project-specific context: the repo layout, which roles matter most, custom instructions per role. Agents will remind you when the refinement is stale (e.g. after a major refactor). To refresh it manually, just run `/squadai-init` in your agent again. --- ## Project memory Agents lose context between sessions. SquadAI now defaults new configs to native local memory metadata and keeps the existing `docs/memory/` folder as the shared export/import format agents can read and write, structured as indexed notes organized by topic. ```sh # From inside your agent /memory-search authentication # find prior decisions /memory-add "switched to JWT, see docs/adr/012.md" # capture a decision /memory-promote # graduate inbox drafts to permanent storage ``` ```sh # From the CLI (for scripting or CI) squadai memory search --query "authentication" squadai memory add --note "switched to JWT" squadai memory status ``` See [`docs/project-memory.md`](docs/project-memory.md) for the full protocol. --- ## Token cost Every squadai install adds agent instruction files to each session's system prompt. On a full TDD install those files add up. You can check the cost: ```sh squadai token-budget # human-readable per-component breakdown squadai token-budget --json # machine-readable ``` Example output: ``` Component Files Tokens ──────────────────────────────────────────────────────────────── agents 6 4,210 skills 6 3,890 rules 1 480 memory 1 260 mcp 1 90 ──────────────────────────────────────────────────────────────── TOTAL 15 8,930 ``` The orchestrator gets the full memory protocol; sub-agents get a two-line stub — that alone cuts roughly 1,000 tokens per session from the default TDD install. --- ## Team policy If you want to enforce a standard setup across a team and prevent individuals from overriding it, create `.squadai/policy.json`: ```json { "version": 1, "mode": "team", "locked": ["methodology", "mcp"], "required": { "methodology": "tdd", "mcp": { "context7": { "enabled": true } } } } ``` Fields listed under `locked` can't be overridden by a developer's local `~/.squadai/config.json`. `squadai doctor` reports policy violations and `squadai validate-policy` checks the file itself. See [`docs/policy.md`](docs/policy.md) for the full reference. --- ## Commands The ones you'll use regularly: ```sh squadai # launch the interactive TUI wizard (first-time setup or re-configure) squadai init # initialize or re-initialize project.json squadai apply # install agent files (idempotent — safe to re-run) squadai diff # preview what apply would change squadai doctor # run ~22 health checks; --fix auto-resolves common issues squadai status # quick view of adapters, components, managed files squadai status --daily # daily control-plane summary for the current repo squadai token-budget # per-session token cost of the current install squadai explain # explain a config field, error code, or concept squadai memory # manage project memory (search, add, promote, status) ``` Less common but good to know: ```sh squadai verify # post-apply compliance assertions squadai plan # show the action plan without applying squadai update # self-update (--check, --enable-checks, or apply latest) squadai remove --force # remove all managed files squadai backup create # snapshot managed files manually squadai restore # restore from a backup ``` For any command: `squadai --help`. --- ## Configuration `squadai init` creates `.squadai/project.json`. Most fields have sensible defaults; the ones you're likely to touch: ```json { "version": 1, "methodology": "tdd", "adapters": { "claude-code": { "enabled": true }, "opencode": { "enabled": true } }, "mcp": { "context7": { "type": "local", "command": ["npx", "-y", "@upstash/context7-mcp@latest"], "enabled": true } }, "meta": { "name": "my-project", "language": "go", "test_command": "go test -race ./..." } } ``` Config is merged from three sources in this order (last wins, unless locked by policy): ``` ~/.squadai/config.json personal defaults .squadai/project.json project config (this file) .squadai/policy.json team policy — locked fields override everything ``` --- ## Install via your AI agent If you'd rather have your agent set things up, paste this into it: > Install squadai using the best available method on this machine (`brew` if available, otherwise the curl script), verify with `squadai version`, run `squadai doctor`, and let me know if any checks failed. Don't run `squadai init` yet — I'll do that myself. --- ## More docs - [`docs/MANUAL.md`](docs/MANUAL.md) — 5-minute user manual - [`docs/project-memory.md`](docs/project-memory.md) — memory protocol deep dive - [`docs/policy.md`](docs/policy.md) — policy and team enforcement - [`docs/architecture.md`](docs/architecture.md) — internals and design decisions - [`docs/troubleshooting.md`](docs/troubleshooting.md) — common issues --- ## License MIT ## Source & license This open-source MCP server is cataloged on AgentStack and links to its original source — we do not rehost the code. - **Author:** [PedroMosquera](https://github.com/PedroMosquera) - **Source:** [PedroMosquera/squadai](https://github.com/PedroMosquera/squadai) - **License:** MIT Install and usage instructions live in the source repository linked above. ## Pricing - **Free** — Free ## Security capabilities Automated source analysis of v0.1.0 — what this tool can access: - **Network access:** yes - **Filesystem access:** no - **Shell / process execution:** no - **Environment & secrets:** no - **Dynamic code execution:** no *"Yes" means the capability is present in the source — more access means more to trust, not that it is unsafe.* ## Versions - **0.1.0** — security scan: flagged — Imported from the upstream source. ## Links - Listing page: https://agentstack.voostack.com/l/mcp-pedromosquera-squadai - Seller: https://agentstack.voostack.com/s/pedromosquera - Browse the marketplace: https://agentstack.voostack.com/browse --- Listed on AgentStack — the marketplace for AI agent skills and MCP servers. Every listing is security-reviewed. Creators keep 70%.