swarm-kb
Shared knowledge base for the Swarm AI suite: ReviewSwarm, FixSwarm, DocSwarm, ArchSwarm.
Provides centralized session storage, cross-tool references, and code mapping so all swarm tools share a single knowledge layer at ~/.swarm-kb/.
Installation
pip install swarm-kb
MCP Server Setup
Claude Code
claude mcp add swarm-kb -- swarm-kb serve --transport stdio
Cursor / Windsurf / Cline (SSE)
swarm-kb serve --port 8788
Then add to your MCP config:
{
"mcpServers": {
"swarm-kb": {
"url": "http://localhost:8788/sse"
}
}
}
Manual .mcp.json (per-project)
{
"mcpServers": {
"swarm-kb": {
"type": "stdio",
"command": "swarm-kb",
"args": ["serve", "--transport", "stdio"]
}
}
}
CLI
swarm-kb status # Show KB health: session counts, storage root
swarm-kb serve # Start MCP server (SSE on port 8788)
swarm-kb serve --transport stdio # Start MCP server (stdio for Claude Code)
Storage Layout
~/.swarm-kb/
├── sessions/
│ ├── review/ # ReviewSwarm sessions
│ ├── doc/ # DocSwarm sessions
│ ├── arch/ # ArchSwarm sessions
│ └── fix/ # FixSwarm sessions
├── code-maps/ # AST-based code analysis per project
└── xrefs.jsonl # Cross-tool references
Migration
On first startup, swarm-kb automatically migrates data from legacy tool-specific directories:
~/.review-swarm/->~/.swarm-kb/sessions/review/~/.doc-swarm/->~/.swarm-kb/sessions/doc/.archswarm_sessions/->~/.swarm-kb/sessions/arch/
Suite Overview
| Tool | Package | Purpose |
|---|---|---|
| swarm-kb | swarm-kb |
Shared knowledge base & code maps |
| ReviewSwarm | review-swarm |
Collaborative AI code review |
| DocSwarm | doc-swarm-ai |
Documentation generation |
| FixSwarm | fix-swarm-ai |
Automated fix planning & application |
| ArchSwarm | arch-swarm-ai |
Architecture analysis & debate |
Install the full suite:
pip install swarm-kb review-swarm doc-swarm-ai fix-swarm-ai arch-swarm-ai
License
MIT
1 maintainer
Metadata
1 maintainer
Release files for swarm-kb 0.4.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| swarm_kb-0.4.0.tar.gz | 141.0 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| swarm_kb-0.4.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 266.8 kB
Release files / swarm_kb-0.4.0.tar.gz
| Download URL | swarm_kb-0.4.0.tar.gz |
|---|---|
| Size | 141.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
649660d05df6d04435a5d57dd03f84f0d8a1750f82116ef22da231e18ae2c707
|
|
BLAKE2b-256 checksum How to use checksums |
42702a9e5b9fa25692e939498055a1ad3e2b7b74b4d2d15b46ee4b8d820e6a9a
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.12.7
|
Release files / swarm_kb-0.4.0-py3-none-any.whl
| Download URL | swarm_kb-0.4.0-py3-none-any.whl |
|---|---|
| Size | 125.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
4fc19105b05389e033045adb2d991ce4c1f35625832da98ea956b7d3f0b64020
|
|
BLAKE2b-256 checksum How to use checksums |
057722e9dec153dd3a506bdbe6bb722a8b43ffa96bf35b5beb4102be0457df54
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.12.7
|
Security for swarm-kb 0.4.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.
