contextweaver MCP server

contextweaver

<!-- mcp-name: io.github.dgenio/contextweaver -->

Capture an agent's effective capability surface, commit it, and see semantically meaningful changes before deployment.

ContextWeaver is currently testing a deliberately narrow product hypothesis: capability snapshot + semantic drift.

Given an OpenAPI document, a captured MCP tools/list response, or a native ContextWeaver catalog, the D1 experiment produces a deterministic normalized snapshot that you can inspect, verify, and compare with a later candidate. It does not require a model account, a gateway, a tool executor, or the Weaver Stack.

Status: alpha, and specifically a product experiment. The implementation works and is tested; the user-value hypothesis is not yet proven. The project is actively measuring whether independent users keep this workflow after trying it on real projects.

Try the capability-drift experiment

Clone the repository and install that checkout so the maintained example fixtures and the code under evaluation are guaranteed to match:

Commands below use python3, matching the repository's documented default (docs/agent-context/workflows.md). On Windows installations that expose Python through the launcher, replace python3 with py -3; if your environment already exposes the intended interpreter as python, use that consistently.

git clone --depth 1 https://github.com/dgenio/contextweaver.git
cd contextweaver
python3 -m pip install .

Run the maintained OpenAPI example:

python3 -m contextweaver.d1 snapshot examples/d1/openapi_before.json --source-type openapi --output ./cw-before.json
python3 -m contextweaver.d1 snapshot examples/d1/openapi_after.json --source-type openapi --output ./cw-after.json
python3 -m contextweaver.d1 inspect ./cw-after.json
python3 -m contextweaver.d1 verify ./cw-after.json
python3 -m contextweaver.d1 diff ./cw-before.json ./cw-after.json

The candidate fixture intentionally:

• makes customer_id required on the existing listInvoices capability;
• changes its description;
• adds a new getInvoice capability.

The diff separates capability additions/removals from changes to an existing logical capability and reports the structured paths that changed. Contract changes are separated from documentation-only changes. Changes involving fields such as required, type, or enum are flagged as potentially breaking for review.

That flag is intentionally conservative: ContextWeaver does not claim to be a complete JSON-Schema compatibility checker.

Full walkthrough: Capability drift experiment.

Use it on your own source

OpenAPI

python3 -m contextweaver.d1 snapshot ./openapi.yaml --source-type openapi --output ./capabilities.json
python3 -m contextweaver.d1 verify ./capabilities.json

After the API changes:

python3 -m contextweaver.d1 snapshot ./openapi.yaml --source-type openapi --output ./capabilities-candidate.json
python3 -m contextweaver.d1 diff ./capabilities.json ./capabilities-candidate.json

Shortened. The full README is on GitHub.