Zypheron's current MCP guide is intentionally narrower than older "copy random JSON and hope it works" blog posts. The CLI now treats generated config as the source of truth.
That means the right flow is not to memorize stale paths. It is to ask Zypheron to generate the config for the client you are using, then start and verify the MCP server from the CLI.
Prerequisites
- Zypheron CLI installed
- Python 3.9+
- MCP-capable client such as Claude Desktop or Cursor
- Dependencies installed via the CLI if bootstrap did not already handle them
Step 1: Install Zypheron
curl -sSfL https://download.zypheron.net/install.sh | bash
# Or bootstrap from source
git clone https://github.com/KKingZero/Zypheron-CLI.git
cd Zypheron-CLI
bash ./setup-hybrid.sh
Step 2: Make Sure Dependencies Are Present
zypheron install-deps --all
zypheron doctor
Step 3: Generate MCP Config
The repo now recommends generated config over hand-written path examples:
zypheron mcp config
Copy the generated output into your MCP client. Treat that generated config as current truth for your install.
Step 4: Start and Verify the Server
zypheron mcp start
zypheron mcp status
Practical Advice
- Start by asking the client to list the available Zypheron tools.
- Use small, low-risk requests before attempting larger chained workflows.
- If something breaks, regenerate config instead of debugging against an old copied example.
Security Notes
MCP is a privileged integration surface. Run it only on systems you control, review the client configuration carefully, and keep provider credentials and local tooling under control.
zypheron mcp status
zypheron ai status
zypheron doctor
If you are unsure whether a failure is coming from your client config or the CLI side, regenerate config first and re-test from a clean state.