One local source for the MCP servers, tools, and memory your AI coding agents share, synced into each tool's native config with a review gate and a receipt for every change. No daemon, no lock-in.
MCPpedia last refreshed this data
Brigade is an MCP server that one local source for the MCP servers, tools, and memory your AI coding agents share, synced into each tool's native config with a review gate and a receipt for every change. No daemon, no lock-in. Its tool list has not been published yet over stdio, sse and http, requires no API key, and scores 93/100 on MCPpedia's security, maintenance and efficiency rubric.
Config is the same across clients — only the file and path differ.
{
"mcpServers": {
"brigade": {
"args": [
"-y",
"skills"
],
"command": "npx"
}
}
}Are you the author?
Add this badge to your README to show your security score and help users find safe servers.
You run more than one agent CLI. Each one keeps its MCP servers in its own config file, its memory in its own silo, and writes to both without review. Brigade is the local layer that fixes that. You keep one canonical source for your MCP servers, your tool and skill catalog, and your memory, and Brigade merges each into the tools you actually use: MCP servers into each tool's native config, tools and skills projected into each harness, and one shared memory owned in one place. A review gate sits
This server supports HTTP transport. Be the first to test it — help the community know if it works.
Five weighted categories — click any category to see the underlying evidence.
No known CVEs.
Checked skills against OSV.dev.
Click any tool to inspect its schema.
Be the first to review
Have you used this server?
Share your experience — it helps other developers decide.
Sign in to write a review.
Others in other
Compress tool outputs, logs, files, and RAG chunks before they reach the LLM. 60-95% fewer tokens, same answers. Library, proxy, MCP server.
Transport for TMCP using STDIO
The graph based agentic IDE
Buddhist canon tools: search, passages, cross-canon parallels, dictionaries — all URN-cited.
MCP Security Weekly
Get CVE alerts and security updates for Brigade and similar servers.
Start a conversation
Ask a question, share a tip, or report an issue.
Sign in to join the discussion.
Brigade keeps coding-agent work trackable across tools, repos, and sessions: tasks, receipts, shared memory, and synced tools.
Install · Docs · Compare · Quickstart
Published v0.26.1 is the stable install (brigade-cli==0.26.1). Current main / 0.27 beta adds per-repo parallel-safe work waves, cross-repo ready-work campaigns with query-time wave composition, Memory Operations, activity and cloud status, code-graph views, bounded recall, and declared budgets. Cells below mark that split.
Learning in Brigade is outcome-based skill scoring, promotion, and rollback from captured verification receipts. It is not autonomous reflective memory learning.
Install with pipx install brigade-cli or uv tool install brigade-cli, then follow the install guide, QUICKSTART.md, or give first 10 minutes and docs/agents-guide.md to your coding agent.
Stable channel: published v0.26.1. Preview channel: brigade update --channel beta for 0.27.0.devYYYYMMDD wheels. Details: update channels.
Brigade overlaps several categories. Most adjacent projects specialize in one layer. Brigade connects those layers around trackable coding-agent work. Where a neighbor is stronger, that cell says so. Dated sources and longer notes: docs/comparison.md (2026-08-13).
Comparison key: Supported ·
Partial ·
Not documented
| Project | Ready work | Claim safety | Parallel and run control |