Skip to main content

cypherwolf-mcp

CypherWolf revises Neo4j Cypher queries against a curated corpus of Neo4j engineering precedent, returning compatibility-gated precedent options plus the index/constraint validation gates to confirm before applying changes.

It ships as a single-tool MCP server (revise_query) that runs locally over stdio and proxies to the CypherWolf HTTPS service. Access is restricted to @neo4j.com users. The package holds no API key, no shared secret, and no Aura credentials — all access control is enforced server-side via an email gate plus a 30-day session token.

Get set up in about two minutes: install → sign in → add to your MCP client → cypherwolf-mcp status to confirm → ask for a rewrite.


1. Install

CypherWolf is a standalone CLI, so install it with pipx — it isolates the dependencies and puts the cypherwolf-mcp command on your PATH:

pipx install cypherwolf-mcp

Requires Python 3.10+. Dependencies are just mcp and httpx — no database driver, no cloud SDKs.

Don't have pipx? Install it (brew install pipx on macOS, or python3 -m pip install --user pipx) and run pipx ensurepath. On Homebrew/externally-managed Python, pip install cypherwolf-mcp fails with a PEP 668 error — pipx is the supported path. (A manual pip install inside an activated virtualenv also works if you prefer.)

Upgrade later with pipx upgrade cypherwolf-mcp.

2. Sign in

Sign in once in a normal terminal with your Neo4j email:

cypherwolf-mcp auth

You will see the following disclosure, then be prompted for your email and a 6-digit code sent to it:

This will email a 6-digit code to verify your @neo4j.com address. Your queries and the rewrites are saved to a Neo4j-internal folder under your email for internal use only.

The resulting session token is cached at ~/.cypherwolf/credentials.json (mode 0600) and is valid for 30 days. After it expires — or if the token is revoked — the tool will ask you to run cypherwolf-mcp auth again.

3. Add CypherWolf to your MCP client

Point your MCP client at the cypherwolf-mcp console script (installed on your PATH by the step above), then restart the client.

Cursor (~/.cursor/mcp.json)

{
  "mcpServers": {
    "cypherwolf": {
      "command": "cypherwolf-mcp"
    }
  }
}

Claude Code (settings.json)

{
  "mcpServers": {
    "cypherwolf": {
      "command": "cypherwolf-mcp"
    }
  }
}

The cypherwolf server exposes a single tool, revise_query.

4. Confirm it works

Before you rely on it, run the built-in self-test — no MCP client required:

cypherwolf-mcp status

It checks the whole chain and prints one line per stage:

CypherWolf self-test
  [PASS] version         cypherwolf-mcp 0.1.6
  [PASS] credentials     you@neo4j.com, token age 2d (re-auth at 30d)
  [PASS] shim round-trip revise_query('RETURN 1') → 200 in 0.41s (https://cypherwolf-shim-ez6emjisaa-uc.a.run.app)

All checks passed. CypherWolf is ready to use.

If any line says [FAIL], it tells you exactly what to fix (for example, run cypherwolf-mcp auth again). The command exits non-zero on failure, so you can use it in scripts.

5. First rewrite

In Cursor (or Claude Code), ask the assistant to revise a Cypher query with CypherWolf — for example:

Use cypherwolf to revise MATCH (u:User) WHERE u.id = $id RETURN u.

CypherWolf returns compatibility-gated precedent candidates plus the validation gates to confirm before applying. See The revise_query tool for the response shape.

Uninstall

Removing CypherWolf is just as simple. The only local state it writes is the credentials cache at ~/.cypherwolf/.

# 1. Remove the "cypherwolf" server entry from your MCP client config
#    (~/.cursor/mcp.json, or Claude Code settings.json), then restart the client.

# 2. Remove the package.
pipx uninstall cypherwolf-mcp        # or: pip uninstall cypherwolf-mcp

# 3. Remove the local credentials cache (the only local state CypherWolf writes).
rm -rf ~/.cypherwolf/

That is a complete, clean removal — nothing else is left on your machine.

The revise_query tool

Arg Required Description
query yes The Cypher query to evaluate against corpus precedent.
context no Schema or context details (labels, indexes, cardinalities).
neo4j_version no Target Neo4j version, e.g. "5.26".
mode no Optional tuning mode, e.g. "verbose".

Response (structured JSON):

{
  "option_a": "MATCH (u:User {id: $id}) RETURN u",
  "option_b": "…optional second rewrite…",
  "recommendation_tier": "recommend",
  "review_required": false,
  "same_domain": true,
  "validation_gates": ["Equality predicate on :User(id) — confirm CREATE INDEX …"],
  "why": ["Corpus precedent (Slack, Fauth): …"],
  "top_n": ["[0.91] Slack — Fauth: supernode pagination"],
  "guidance": ["Advice note 1", "Advice note 2"],
  "no_rewrite_reason": null
}
  • option_a/option_b are compatibility-gated precedent candidates, not guaranteed semantic equivalents of the input query. Review before applying.
  • recommendation_tier is recommend for higher-confidence candidates and draft when CypherWolf surfaces a lower-confidence but hard-safe candidate. Drafts always set review_required: true.
  • same_domain reports whether the candidate shares a label/relationship anchor with your query. A draft with same_domain: false is a structural lookalike from a different schema — the error field flags it as a pattern reference, not a rewrite. Don't adopt that option_a; use only the validation_gates and guidance.
  • On abstain responses, guidance carries 3-5 extracted advice notes from top evidence rows so users still get actionable hints when no safe rewrite is selected.
  • Abstain is a success. When confidence is too low or the corpus has no usable precedent, option_a is null and no_rewrite_reason explains why (for example "low-confidence" or "corpus-gap"). CypherWolf never bluffs.
  • Operational failures are real errors. A dead service, an expired session, or a rate limit raises a clear MCP error (for example, "CypherWolf authentication is required — run cypherwolf-mcp auth") rather than a half-answer. Run cypherwolf-mcp status to pinpoint the cause.

Configuration

Environment variable Default Purpose
CYPHERWOLF_SHIM_URL https://cypherwolf-shim-ez6emjisaa-uc.a.run.app CypherWolf service base URL.
CYPHERWOLF_SESSION_TOKEN (unset) Supply a session token directly, bypassing the on-disk cache (CI / scripted use).

Credentials cache: ~/.cypherwolf/credentials.json (mode 0600), holding {email, session_token, issued_at}.

Privacy

Your submitted queries and the returned rewrites are logged server-side to a Neo4j-internal storage location, keyed by your email, for internal use only. See the sign-in disclosure above.


Maintaining or releasing the package? See PUBLISHING.md.

Metadata

Release files for cypherwolf-mcp 0.1.7

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for cypherwolf-mcp 0.1.7
File Size Uploaded Provenance Actions
cypherwolf_mcp-0.1.7.tar.gz 33.8 kB Without provenance Details for cypherwolf_mcp-0.1.7.tar.gz

Built distribution (wheel)

Table of built distributions (wheels) for cypherwolf-mcp 0.1.7
File Interpreter ABI Platform Actions
cypherwolf_mcp-0.1.7-py3-none-any.whl Python 3 none any Details for cypherwolf_mcp-0.1.7-py3-none-any.whl

Total release size: 57.8 kB

Release files / cypherwolf_mcp-0.1.7.tar.gz

Download URL cypherwolf_mcp-0.1.7.tar.gz
Size 33.8 kB
Tags Source
SHA-256 checksum
How to use checksums
ab9a882037ca933b0f7c945f1a17f10da2042c478b9c9f150e47d9b75e1470d6
BLAKE2b-256 checksum
How to use checksums
9b07bf597684f977bbdb47d211bc3b0e49b809be9f95a937490e7ed80679d509
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/7.0.0 CPython/3.11.10

Release files / cypherwolf_mcp-0.1.7-py3-none-any.whl

Download URL cypherwolf_mcp-0.1.7-py3-none-any.whl
Size 23.9 kB
Tags Python 3
SHA-256 checksum
How to use checksums
3552b725f598da5dc627542b9184972da2b95b183e02b4c5c2e9cdad69d94bb5
BLAKE2b-256 checksum
How to use checksums
dd3f3de8a6282245b541edf0868bfd8e0ffdfc88ff8603f7e1723174448c988f
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via twine/7.0.0 CPython/3.11.10

Security for cypherwolf-mcp 0.1.7

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.

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page