Compatible with every major AI agent and IDE
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
- Get your Zeev domain and API Key from your profile settings.
- Enter your credentials in Vinkius platform.
- 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 an active process request
Start a new process request in Zeev
Delegate a task to another user
Finish/Complete a Zeev task
Get current user information
Get details of a process definition
Get details of a specific process request
Get details of a specific Zeev task
List available process definitions
List process requests (instances) in Zeev
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
Zeev in VS Code Copilot
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.
Raw MCP | Vinkius | |
|---|---|---|
| Server catalog | Find and host yourself | 4,000+ managed |
| Infrastructure | Self-hosted | Sandboxed V8 isolates |
| Credential handling | Plaintext in config | Vault + runtime injection |
| Data loss prevention | None | Configurable DLP policies |
| Kill switch | None | Global instant shutdown |
| Financial circuit breakers | None | Per-server limits + alerts |
| Audit trail | None | Ed25519 signed logs |
| SIEM log streaming | None | Splunk, Datadog, Webhook |
| Honeytokens | None | Canary alerts on leak |
| Custom domains | Not applicable | DNS challenge verified |
| GDPR compliance | Manual effort | Automated purge + export |
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.

* 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
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.
Frequently asked questions
Can I start any process using the AI agent?
Yes, as long as you have the process ID and the required initial form data.
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.
Can I see the history of a request?
Yes, the get_request tool provides details including the current status and history of the instance.
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.
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.
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.
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.
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 →
Bilibili Live
10 toolsAutomate VTuber interaction parsing via Bilibili Live — monitor super-chats, extract danmaku streams, and manage host rooms natively from any AI agent.

Papermark (Docsend Alternative)
6 toolsSecurely share documents, track engagement, and manage links with Papermark — the open-source DocSend alternative for your AI agent.

Cloud BOT
7 toolsRun automated browser tasks in the cloud with scriptless bots that extract data, fill forms, and navigate websites on autopilot.

Join
10 toolsManage recruiting, jobs, and candidates via JOIN API.
