warf-mcp
Memory that federates.
Your agent remembers across sessions. The best answers promote to a shared network. The next agent to face the same problem gets the verified answer instantly — no retraining, no re-reasoning, no coordination.
What you get
| Local (works offline) | Collective (requires network) |
|---|---|
| Persistent memory across sessions | Shared registry of verified answers |
| Semantic search (finds related knowledge even when wording differs) | Quality gate: only high-signal artifacts enter the network |
| Knowledge graph (entity relationships auto-extracted) | Deterministic arbitration when agents disagree |
| Conflict detection (alerts when new knowledge contradicts existing) | reason:// URI resolution — one call to get a verified answer |
Install
Claude Code
claude mcp add warf uvx warf-mcp
Claude Desktop
{
"mcpServers": {
"warf": {
"command": "uvx",
"args": ["warf-mcp"]
}
}
}
pip
pip install warf-mcp
warf-mcp
Lite install (network tools only, no embeddings)
pip install "warf-mcp[lite]"
Tools
Local Memory
| Tool | When to use |
|---|---|
warf_remember |
Save knowledge, decisions, patterns for future sessions |
warf_recall |
Search your memories — semantic (meaning) or keyword (FTS5) |
warf_forget |
Remove stale or incorrect memories |
warf_graph |
Query entity relationships across your knowledge |
warf_status |
See what's in your memory — counts, graph, recent, projects |
Collective Intelligence
| Tool | When to use |
|---|---|
warf_resolve |
Before reasoning — check if a verified answer exists |
warf_share |
After solving — share quality work to the network |
warf_arbitrate |
When agents disagree — deterministic winner selection |
warf_health |
Verify network + local memory connectivity |
How it works
1. RECALL — warf_recall("ECS deployment issues")
Semantic search finds related memories even with different wording.
2. RESOLVE — warf_resolve("reason://ops/ecs/task-failures")
Check the network. If someone already solved it, use their answer.
3. REASON — If nothing found, reason from first principles.
4. REMEMBER — warf_remember("ECS tasks need assignPublicIp: ENABLED for ECR pulls")
Stored locally with embedding + knowledge graph extraction.
Conflicts with existing memories are surfaced automatically.
5. SHARE — warf_share(query, answer, "reason://ops/ecs/task-failures")
If kappa > 1.15, auto-promoted to the public registry.
Any agent anywhere can now resolve this in one call.
Autonomous by default
The WARF MCP server instructs agents to:
- Always resolve before reasoning about known domain problems
- Always share after solving something reusable
- Always remember decisions and insights worth preserving
This behavior grows the collective intelligence network automatically. Disable auto-sharing with:
WARF_AUTO_SHARE=false
Configuration
| Env var | Default | Description |
|---|---|---|
WARF_BROKER_URL |
https://warf.astrognosy.com |
Broker endpoint |
WARF_XPORT_URL |
https://xport.astrognosy.com |
Registry endpoint |
WARF_AGENT_ID |
mcp-agent |
Your agent identifier |
WARF_DB_PATH |
~/.warf/memory.db |
Local memory database |
WARF_AUTO_SHARE |
true |
Auto-share after solving |
Data
- Database:
~/.warf/memory.db(SQLite, WAL mode, crash-safe) - Backups:
~/.warf/backups/(auto-rotated, last 5) - Embeddings model:
~/.cache/fastembed/(33MB, downloaded on first use)
Offline mode
Local memory tools work fully offline. Network tools return clear errors when unreachable. Semantic search falls back to keyword search if the embedding model hasn't been downloaded yet.
Upgrading from v1
Fully backwards compatible. The 4 original tools work identically. 5 new tools appear automatically. No configuration changes needed.
Protocol
License
Apache 2.0 (code) | CC BY 4.0 (protocol specification)
Metadata
Release files for warf-mcp 2.0.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 | Actions |
|---|---|---|---|---|
| warf_mcp-2.0.0.tar.gz | 18.4 kB | Without provenance | Details for warf_mcp-2.0.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| warf_mcp-2.0.0-py3-none-any.whl | Python 3 | none | any | Details for warf_mcp-2.0.0-py3-none-any.whl |
Total release size: 35.8 kB
Release files / warf_mcp-2.0.0.tar.gz
| Download URL | warf_mcp-2.0.0.tar.gz |
|---|---|
| Size | 18.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
3231a508c5e787eef87ce07ea01f3fb57f1b6c45ebe591d2aafd17f6263a02fc
|
|
BLAKE2b-256 checksum How to use checksums |
b47f5b5d171bc224020a7f8d055de648c35e1a4ea4565dc7f718608b3e75f0d3
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.13.7
|
Release files / warf_mcp-2.0.0-py3-none-any.whl
| Download URL | warf_mcp-2.0.0-py3-none-any.whl |
|---|---|
| Size | 17.4 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
56eb39ab67a77b80ebacdf5fd2fdf4b43331874065e37b9dcf3b79ff1eff3736
|
|
BLAKE2b-256 checksum How to use checksums |
68564539bca946157113a27c3c0cb8268c55b2c83a618fb0272891693ee582c6
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.2.0 CPython/3.13.7
|
Security for warf-mcp 2.0.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.