zynia-mcp

Universal MCP gateway for Zynia OS agents, squads and /vibe-* commands.

Use it from Claude Code, Claude Desktop, Cursor, Windsurf, VS Code/Copilot MCP, Continue, Zed, OpenClaw and any MCP-compatible client.

Install In Your AI Apps

First, test if a backend URL is valid:

npx -y zynia-mcp doctor --url http://localhost:3001 --api-key YOUR_KEY

To generate a visible local folder with agent, squad and command files:

npx -y zynia-mcp export --url http://localhost:3001 --api-key YOUR_KEY --out zynia-os-agents

npx -y zynia-mcp install --url https://your-zynia-api.com

For local development:

npx -y zynia-mcp install --url http://localhost:3001

If your Zynia backend requires an API key:

npx -y zynia-mcp install --url https://your-zynia-api.com --api-key YOUR_KEY

For production/private use, always configure --api-key. The package talks to the protected /api/mcp-gateway backend prefix by default.

Manual MCP Config

{
  "mcpServers": {
    "zynia-os": {
      "command": "npx",
      "args": ["-y", "zynia-mcp"],
      "env": {
        "ZYNIA_SERVER_URL": "https://your-zynia-api.com",
        "ZYNIA_API_KEY": "your-private-api-key"
      }
    }
  }
}

Tools

• zynia_health: check whether the Zynia backend is reachable and count operational, registry, dynamic and vibe agents.
• zynia_ask: ask the Zynia Commander.
• zynia_list_agents: list available Zynia agents and squads. Use source: "registry" or source: "all" to inspect more than the operational runtime list.
• zynia_agent: run a specific agent by ID.
• zynia_squad: run a full squad by name or explicit agent list.
• zynia_vibe: resolve or execute /vibe-* commands.
• zynia_context_save: save important context through the Context Engineer.
• zynia_prompt: turn rough ideas into premium prompts for any AI.
• zynia_vibecode: run the Vibe Engineering Squad for any programmable system.
• zynia_design: run design, UI/UX, visual direction and motion specialists.
• zynia_website: run the Premium Website Squad for sites and landing pages.
• zynia_frontend: run React/Vite/frontend implementation specialists.
• zynia_backend: run backend/API/data/security specialists.
• zynia_fullstack: run a complete product squad end-to-end.

Local Agent Folder

zynia-mcp export creates:

• agents/: operational agent cards.
• registry/: full registry agent cards.
• squads/: squad definitions.
• commands/: /vibe-* command cards.
• config/mcp.example.json: example MCP config.
• MANIFEST.json: export metadata.

These files are for visibility, editing, planning and handoff. Editing them does not automatically change the backend runtime yet.

Common Squads

• anyProgrammableSystem: CRM, dashboards, SaaS MVPs, internal systems and generators.
• premiumWebsite: sites, landing pages, copy, SEO, UX and performance.
• productionWebApp: frontend, backend, security, QA and review.
• performanceSprint: Core Web Vitals, bundle, Lighthouse and runtime speed.
• securityHardening: auth, permissions, secrets, CORS and release blockers.

Example

{
  "tool": "zynia_vibe",
  "arguments": {
    "message": "/vibe-security audit auth, permissions, secrets and CORS",
    "execute": true
  }
}

Requirements

This package is only the MCP gateway. It needs a running Zynia OS backend:

• local: http://localhost:3001
• remote: https://your-zynia-api.com

Set it with ZYNIA_SERVER_URL.

Optional env vars:

• ZYNIA_API_KEY: private API key expected by the Zynia backend.
• ZYNIA_API_PREFIX: backend route prefix. Default: /api/mcp-gateway.