4,000+ servers built on vurb.ts
Vinkius
VS Code CopilotIDE
Zeev MCP Server

Bring Bpm
to VS Code Copilot

Learn how to connect Zeev to VS Code Copilot and start using 11 AI agent tools in minutes. Fully managed, enterprise secure, and ready to use without writing a single line of code.

MCP Inspector GDPR Free for Subscribers
Cancel RequestCreate RequestDelegate TaskFinish TaskGet MeGet ProcessGet RequestGet TaskList ProcessesList RequestsList Tasks

Compatible with every major AI agent and IDE

ClaudeClaude
ChatGPTChatGPT
CursorCursor
GeminiGemini
WindsurfWindsurf
VS CodeVS Code
JetBrainsJetBrains
VercelVercel
+ other MCP clients
Zeev

What is the Zeev MCP Server?

What you can do

  • List and manage your pending tasks in real-time.
  • Start new process requests with custom form data.
  • Complete tasks and make decisions directly from your AI agent.
  • Delegate tasks to other team members and track process history.

How it works

  1. Get your Zeev domain and API Key from your profile settings.
  2. Enter your credentials in Vinkius platform.
  3. Start chatting with your Zeev agent to manage your workflows.

Who is it for?

  • Process managers looking for automated workflow control.
  • Operations teams needing quick task execution.
  • Developers integrating BPM into their AI-driven applications.

Built-in capabilities (11)

cancel_request

Cancel an active process request

create_request

Start a new process request in Zeev

delegate_task

Delegate a task to another user

finish_task

Finish/Complete a Zeev task

get_me

Get current user information

get_process

Get details of a process definition

get_request

Get details of a specific process request

get_task

Get details of a specific Zeev task

list_processes

List available process definitions

list_requests

List process requests (instances) in Zeev

list_tasks

List pending tasks in Zeev

Why VS Code Copilot?

GitHub Copilot Agent mode brings Zeev data directly into your VS Code workflow. With a project-scoped config, the entire team shares access to 11 tools. Copilot queries live data, generates typed code, and writes tests from actual API responses, all without leaving the editor.

  • VS Code is used by over 70% of developers. adding MCP tools to Copilot means your team can leverage external data without leaving their primary editor

  • Project-scoped MCP configs (.vscode/mcp.json) let you commit server configurations to your repository, ensuring the entire team shares the same tool access

  • Copilot's Agent mode integrates MCP tools seamlessly with file editing, terminal commands, and workspace search in a single agentic loop

  • GitHub's enterprise compliance and audit features extend to MCP tool usage, providing visibility into how AI interacts with external services

See it in action

Zeev in VS Code Copilot

AI AgentVinkius
High Security·Kill Switch·Plug and Play
Why Vinkius

Zeev and 4,000+ other MCP servers. One platform. One governance layer.

Teams that connect Zeev to VS Code Copilot through Vinkius don't need to source, host, or maintain individual MCP servers. Every tool call runs inside a hardened runtime with credential isolation, DLP, and a signed audit chain.

4,000+MCP Servers ready
<40msCold start
60%Token savings
Raw MCP
Vinkius
Server catalogFind and host yourself4,000+ managed
InfrastructureSelf-hostedSandboxed V8 isolates
Credential handlingPlaintext in configVault + runtime injection
Data loss preventionNoneConfigurable DLP policies
Kill switchNoneGlobal instant shutdown
Financial circuit breakersNonePer-server limits + alerts
Audit trailNoneEd25519 signed logs
SIEM log streamingNoneSplunk, Datadog, Webhook
HoneytokensNoneCanary alerts on leak
Custom domainsNot applicableDNS challenge verified
GDPR complianceManual effortAutomated purge + export
Enterprise Security

Why teams choose Vinkius for Zeev in VS Code Copilot

The Zeev MCP Server runs on Vinkius-managed infrastructure inside AWS — a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts. All 11 tools execute in hardened sandboxes optimized for native MCP execution.

Your AI agents in VS Code Copilot only access the data you authorize, with DLP that blocks sensitive information from ever reaching the model, kill switch for instant shutdown, and up to 60% token savings. Enterprise-grade infrastructure, zero maintenance.

Zeev
Fully ManagedVinkius Servers
60%Token savings
High SecurityEnterprise-grade
IAMAccess control
EU AI ActCompliant
DLPData protection
V8 IsolateSandboxed
Ed25519Audit chain
<40msKill switch
Stream every event to Splunk, Datadog, or your own webhook in real-time

* Every MCP server runs on Vinkius-managed infrastructure inside AWS - a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts optimized for native MCP execution. See our infrastructure

The Vinkius Advantage

How Vinkius secures Zeev for VS Code Copilot

Every tool call from VS Code Copilot to the Zeev MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.

< 40msCold start
Ed25519Signed audit chain
60%Token savings
FAQ

Frequently asked questions

01

Can I start any process using the AI agent?

Yes, as long as you have the process ID and the required initial form data.

02

Is it possible to delegate tasks to specific users?

Yes, you can use the delegate_task tool by providing the Task ID and the target User ID.

03

Can I see the history of a request?

Yes, the get_request tool provides details including the current status and history of the instance.

04

Which VS Code version supports MCP?

MCP support requires VS Code 1.99 or later with the GitHub Copilot extension. Ensure both are updated to the latest version. Older versions of Copilot may not expose the Agent mode toggle.

05

How do I switch to Agent mode?

Open the Copilot Chat panel and look for two mode options: "Ask" and "Agent". Click "Agent" to enable autonomous tool calling. In Ask mode, Copilot provides conversational answers but cannot invoke MCP tools.

06

Can I restrict which MCP tools Copilot can access?

Yes. VS Code shows a tool consent dialog before any MCP tool is invoked for the first time. You can also configure tool access policies at the organization level through GitHub Copilot settings.

07

Does MCP work in VS Code Remote or Codespaces?

Yes. MCP servers configured via .vscode/mcp.json work in Remote SSH, WSL, and GitHub Codespaces environments. The MCP connection is established from the remote host, so ensure the server URL is accessible from that environment.

08

MCP tools not available

Ensure you are in Agent mode in Copilot Chat. MCP tools only appear in Agent mode.

Explore More MCP Servers

View all →