One coherent way to extend Zerynex into agent-assisted workflows: a restricted MCP interface, portable skills, and CI gates. Built for developers—not for handing transaction secrets to language models.
Use a restricted stdio MCP server that only examines approved synthetic fixtures. No wallet keys, arbitrary filesystem access or remote RPC.
ZERYNEX_CLI=/absolute/path/to/zerynex
ZERYNEX_AGENT_ALLOWED_ROOT=/absolute/path/to/synthetic-fixtures
zerynex-mcpEquip compatible coding assistants with a documented Zcash privacy-review workflow. The skill is an instruction package, not a remote service.
agent/skills/zcash-privacy-check/SKILL.md
# Configure this skill directory in your compatible agent host.Keep review deterministic. Test approved synthetic PCZT snapshots as part of a GitHub Action without sending confidential wallet data to an agent.
uses: Oluwa-Laughter/zerynex@<reviewed-commit>
with:
scenario-manifest: tests/fixtures/scenario.jsonGenerate host configuration locally. Your paths stay in the browser. Then validate the actual MCP process with the doctor command, before giving your assistant any tool access.
Replace sample paths with absolute local paths (Unix or Windows), one per line.
{
"mcpServers": {
"zerynex": {
"type": "stdio",
"command": "/absolute/path/to/.venv/bin/zerynex-mcp",
"args": [],
"env": {
"ZERYNEX_CLI": "/absolute/path/to/zerynex",
"ZERYNEX_AGENT_ALLOWED_ROOT": "/absolute/path/to/approved-synthetic-fixtures"
}
}
}
}Sample configurations for hosts that support these keys; apply in the host’s own settings. The website cannot access your filesystem, start MCP, or verify a remote agent.
See exactly the kind of sanitized finding an agent receives. This demo executes Rust/WASM in the browser; it is not an MCP connection.
zerynex-mcp-doctor --cli /absolute/path/to/zerynex --fixtures /absolute/path/to/approved-synthetic-fixtures --server /absolute/path/to/zerynex-mcplist_synthetic_fixturesanalyze_synthetic_pcztcompare_synthetic_pczt_stagesrun_synthetic_smoke_suiteexplain_zerynex_rulezerynex_policy_schemaCurrent MCP tools are read-only and return sanitized rule identifiers. This is not a wallet signer, proof verifier, or general filesystem MCP. Host-specific setup must be completed by the developer.
Read the trust model