4,500+ servers built on MCP Fusion
Vinkius
Zeev logo
Vinkius
Claude Code logo

How to Use the Zeev MCP in Claude Code

Automate Zeev workflows in CI/CD pipelines using Claude Code.

See Vinkius in Action

Works with every AI agent you already use

…and any MCP-compatible client

Zeev MCP on Cursor AI Code Editor MCP Client Zeev MCP on Claude Desktop App MCP Integration Zeev MCP on OpenAI Agents SDK MCP Compatible Zeev MCP on Visual Studio Code MCP Extension Client Zeev MCP on GitHub Copilot AI Agent MCP Integration Zeev MCP on Google Gemini AI MCP Integration Zeev MCP on Lovable AI Development MCP Client Zeev MCP on Mistral AI Agents MCP Compatible Zeev MCP on Amazon AWS Bedrock MCP Support
MCP Servers - Free for Subscribers
Claude Code

Connect Zeev MCP to Claude Code

Create your Vinkius account to connect Zeev to Claude Code and route execution through our secure gateway. The platform manages server hosting, runtime updates, and security layers. Configuration requires no manual server provisioning.

GDPR Free for Subscribers

Kick off workflows via scripts.

The `create_request` tool lets you script the start of a complex process. Instead of relying on an interface, your shell script hits this endpoint with parameters and triggers a full Zeev workflow instance. This is ideal for CI/CD pipelines: when code passes testing, one simple job execution can kick off an entire multi-stage approval flow in Zeev.

Inventory all available processes.

Before running any automation, you need to know what's there. Use `list_processes` to fetch a manifest of every process definition available in the system. This list lets your scripts dynamically choose which workflow ID to use. Paired with `get_process`, you can pull down the full structure and ruleset for a specific Zeev process, ensuring your script adheres exactly to the expected logic.

Monitor task state in headless mode.

When running in a Docker container or GitHub Action, you can't watch pop-ups. Use `get_request` and `list_requests` to poll for the status of your process instances. Your script checks this endpoint until it gets 'Completed,' allowing the pipeline job to proceed only when the workflow is done. If something goes wrong, use `cancel_request` in a cleanup step to ensure resources are freed up immediately.

Setup guide

Set up Zeev MCP in Claude Code

Prerequisites

  • Claude Code CLI installed (npm install -g @anthropic-ai/claude-code)
  • Active Vinkius subscription with a valid endpoint token
  1. 1

    Run the add command

    Open your terminal and run the command shown on the right. Replace [YOUR_TOKEN_HERE] with your endpoint token from cloud.vinkius.com. Use --scope user to make it available across all projects.

  2. 2

    Verify the connection

    Start a Claude Code session and type /mcp to list connected servers. You should see zeev-mcp with a green status indicator.

  3. 3

    Start using tools

    Ask Claude Code something like "Check my latest Zeev transactions." It will automatically discover and invoke the available Zeev tools.

Terminal
claude mcp add --transport http zeev-mcp https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp

Why Choose Vinkius

Vinkius connects your tools to AI with real-time monitoring and automatic cost savings — all from one dashboard.

Real-time monitoring

Live

visibility into every interaction

Connect your favorite tools to your AI and see exactly what's happening — every request, every response, in real time.

Built-in savings

60%

lower AI costs

Vinkius compresses data between your apps and your AI automatically. Lower bills every month — no configuration required.

Single dashboard

One

place for every integration

Every tool your AI connects to, managed from a single screen. One account, complete control.

Common questions about Zeev MCP in Claude Code

You use the `create_request` tool. Your shell script sends a command with initial data, which triggers the entire multi-step workflow in Zeev. The job returns an ID you can then poll for status.
Run `list_processes` to get a manifest of all defined BPMN workflows. This list shows every process definition your scripts can interact with, letting you build robust pipelines.
Use `get_task` or `get_request`. These tools let your script check the exact state of a process instance or a single human-actionable task. This is how you automate waiting for approvals.
It touches workflow state records, including process definitions, active request instances, and pending tasks within the core Zeev system.
Use `get_me` to pull your current user data. This confirms who initiated the failing job, which is critical for logging and debugging in a CI/CD environment.

Start using the Zeev MCP today

We host it, we monitor it, we maintain it. You just paste one token.

Built & Managed by Vinkius 30s setup 11 tools

We've already built the connector for Zeev. Just plug in your AI agents and start using Vinkius.

No hosting. No infrastructure. No complex setup.
All 11 tools are live and waiting. You're up and running in seconds.

Claude Claude
ChatGPT ChatGPT
Cursor Cursor
Gemini Gemini
Windsurf Windsurf
VS Code VS Code
JetBrains JetBrains
Vercel Vercel
+ other MCP clients

Vinkius gives your AI agents access to the full catalog of app connectors, all fully managed, secure, and enterprise-ready. One subscription, every tool you need.

Zero hosting required Full MCP catalog included Enterprise-grade security Auto-updated by Vinkius

Built, hosted, and secured by Vinkius. You just connect and go.