Repository navigation
v0.1.0-spec — Public ANF Spec Launch
ACP v0.1.0-spec — Public Spec Launch
Agent Context Protocol — one API call, complete execution context, minimal tokens.
ACP sits on top of MCP. The agent sends one intent; ACP returns one scoped manifest with auth pre-injected, ordering pre-computed, and security boundaries declared. Existing MCP servers keep working — ACP ingests their tools/list and produces token-minimal manifests for execution.
Why this matters
| MCP today (raw) | ACP on top of MCP | |
|---|---|---|
| Round trips before first action | 3–21 (measured) | 1 |
| Tokens for representative workflows | 373–9,223 | 111–359 (64–97% reduction) |
| Auth in agent context | yes | never |
| Execution ordering | agent infers | server declares |
Full benchmarks: results/2026-05-02-week3-summary.md · Full positioning: docs/positioning.md.
Install (pick one)
# Go binary, no clone (requires Go 1.25+)
go install github.com/Clawdlinux/ninevigil-acp/cmd/acp-server@v0.1.0-spec
ACP_AUTH_TOKEN=dev-token acp-server --addr :8080
# Docker (no toolchain needed)
docker run --rm -p 8080:8080 -e ACP_AUTH_TOKEN=dev-token \
ghcr.io/clawdlinux/ninevigil-acp:v0.1.0-spec
# or, from Docker Hub:
docker run --rm -p 8080:8080 -e ACP_AUTH_TOKEN=dev-token \
goodra007/acp-server:v0.1.0-spec
# Source build
git clone https://github.com/Clawdlinux/ninevigil-acp && cd ninevigil-acp
make build
ACP_AUTH_TOKEN=dev-token ./bin/acp-server --addr :8080Python adapters (pip from git, no PyPI required)
pip install "git+https://github.com/Clawdlinux/ninevigil-acp.git@v0.1.0-spec#subdirectory=adapters/python/acp_common"
pip install "git+https://github.com/Clawdlinux/ninevigil-acp.git@v0.1.0-spec#subdirectory=adapters/python/acp_langgraph"
pip install "git+https://github.com/Clawdlinux/ninevigil-acp.git@v0.1.0-spec#subdirectory=adapters/python/acp_openai"
pip install "git+https://github.com/Clawdlinux/ninevigil-acp.git@v0.1.0-spec#subdirectory=adapters/python/acp_crewai"Quickstart
curl -sS -X POST http://localhost:8080/v1/context \
-H "Authorization: Bearer dev-token" \
-H "Content-Type: application/json" \
-d '{"intent":"query customer data, render report, email the team","agent_id":"demo"}' \
| python3 -m json.toolWhat's included
- Spec (
SPEC.md, CC BY 4.0) — protocol definition, manifest format, threat model. - Go server (
cmd/acp-server, Apache-2.0) — intent resolver (keyword + embedding), manifest builder, auth-injection proxy. - Go SDK (
pkg/acp, Apache-2.0) —acp.NewClient(...)with token + manifest helpers. - Python adapters (Apache-2.0) —
acp_common(shared client + types),acp_langgraph,acp_openai,acp_crewai. - Benchmark harness (
benchmark/) — 5 scenarios × 50 runs/scenario,tiktoken/cl100k_base.
Status
PoC. The protocol surface is stable for v0.1; the resolver and adapters are alpha-quality and will move with feedback. File issues at Clawdlinux/ninevigil-acp/issues.
Image digest
sha256:804051ad391d2dc398b24f9f50930257672d6ada9771cf36ff5863433a1432b3 — same digest for all three tags (v0.1.0-spec, v0.1, latest).