Z.ai

How to give Z.ai access to JSON Merge Patch

Set up in seconds, once. From then on, Z.ai gets things done for you: JSON Merge Patch becomes an HTTP MCP server in ZCode, ready in every workspace.

Ask AI about this guide

JSON Merge Patch Connector

You're all set. Choose your MCP client and follow the setup instructions.

Connector linkhttps://edge.vinkius.com/vk_preview_jagY81WpYhec0VzgLCycaUIZKOPxhooBwDz9HBff/mcp

Connecting JSON Merge Patch to Z.ai

About a minute, in ZCode settings

  1. 1Open Settings, MCP Servers, then click New MCP Server in the upper-right corner.
  2. 2Choose the User scope, name it, and keep the type as HTTP. Paste your JSON Merge Patch link as the service URL. The link above is the URL.
  3. 3Click Add and confirm the server is enabled in the list, then ask something real. JSON Merge Patch is now part of Z.ai.
Configuration · claude_desktop_config.jsonCopy
{
  "mcpServers": {
    "json-merge-patch-mcp": {
      "url": "https://edge.vinkius.com/vk_preview_jagY81WpYhec0VzgLCycaUIZKOPxhooBwDz9HBff/mcp"
    }
  }
}

Z.ai + JSON Merge Patch

One chat. Your JSON Merge Patch, live inside Z.ai.

Real prompts, answered with live data. This is the kind of session you will have in Z.ai once the server is in.

Waiting for input…

Works with modern AI clients that support MCP, including ChatGPT, Claude, Cursor, and more.

ChatGPTClaudeCursorPerplexityGeminiMicrosoft CopilotRaycastMeta AI

These prompts ship with the JSON Merge Patch Connector. Once yours is connected, they work in your sessions.

The full capability set, the prompts and the observed latency live on the JSON Merge Patch Connector page.

Mission Control

See everything your Z.ai agents do in JSON Merge Patch.

When Z.ai runs a tool in JSON Merge Patch, it happens on Z.ai's side: you see the result, but not the request itself, what data it carried, or whether a rule was broken.

Now every move lands on your screen.

Every execution is recorded, enforced, and shown to you: what ran, what it returned, what was blocked, and why.

AI Briefing
Upgrade to unlock

Know exactly what needs your attention before you even look at the charts. One briefing. The full picture. The next move.

Requests
0
Total in this period
Avg Latency
0
API 88ms · Overhead 54ms
Vinkius Reliability
0
Agent 280 · Upstream 47 · Vinkius 15
Tokens
0
AI tokens processed
DLP Protected
0
Sensitive data redacted
Cost Saved
0
FinOps truncations applied

AI Agents Activities

last 30 days
30d agotoday

Request Volume & Latency

requests latency

Every request your Z.ai agents make through JSON Merge Patch is logged, enforced and auditable. See how AI Governance turns agent activity into accountability, and what it means for your JSON Merge Patch workflows.

What sets us apart

It's not just the Connector that stays safe. Everything your agents do through it is.

Connecting JSON Merge Patch to your AI is step one. But an open line between your agents and JSON Merge Patch is only half the story: without protection, every action they take runs unguarded.

That's why protection doesn't stop at the door.

Every action your agents take through the Connector runs inside our infrastructure: signed activity logs, automatic key rotation, spending limits that pause instead of surprise, and a sandbox that isolates every execution.

01

Tamper Proof Activity Log

Every request your agents make in JSON Merge Patch is recorded and signed, so any change to the history becomes detectable.

02

Automatic Key Rotation

We rotate security keys every 24 hours. Your JSON Merge Patch connection stays protected without any manual work.

03

Spending Protection

We enforce the spending limit you choose and pause actions that exceed it until approval is received. Your JSON Merge Patch actions never surprise you.

04

Isolated Sandbox

Every execution through JSON Merge Patch runs isolated, with 34+ security rules covering memory, CPU, network access, file handling and execution.

05

Security Event Streaming

Security events flow to Splunk, Datadog or your own webhook, so JSON Merge Patch activity lands in the tools you already rely on.

06

Instant Resume

Idle connections resume in 3 to 5 ms while preserving their state, keeping your Z.ai sessions responsive.

07

Malicious File Protection

We detect compressed files designed to exhaust system resources and block them before they ever reach JSON Merge Patch.

08

Credential Validation

We test your JSON Merge Patch credentials before saving them. Invalid credentials are rejected instead of being stored.

09

Separate Usage Limits

Usage stays isolated per account, so activity in one connection never consumes another account's allowance.

One Connector, one link, and the whole operation is protected. Not just the connection: everything your agents do through it.

These guarantees are not add-ons: they are the infrastructure every JSON Merge Patch connection runs on. Read how our infrastructure protects everything your Z.ai agents do, end to end.

Inside Vinkius

Get JSON Merge Patch ready for your AI. It's easy.

You choose JSON Merge Patch from the Vinkius Catalog and get one connection link. That's it.

  1. You choose JSON Merge Patch

    You find JSON Merge Patch in the Catalog and install the Connector with one click.

    JSON Merge Patch

    Active

    Enable Connector
    Activating…

  2. You add the link in Z.ai

    Vinkius gives you one connection link. In ZCode, you add an HTTP MCP server in Settings with the link as the service URL, and the connection is ready.

    Token generated successfully

    MCP Connection URL

    https://edge.vinkius.com/vk_preview_jagY81WpYhec0VzgLCycaUIZKOPxhooBwDz9HBff/mcp

    Connection Token

    vk_live_••••••••
    Go to Dashboard

Set it up once. Use JSON Merge Patch with the AI you already use.

FAQ

Z.ai access questions.

  • 01

    Does this work across my workspaces?

    Yes. Choose the User scope when adding the server and it's available in every workspace; Workspace scope keeps it in the current project only.

  • 02

    If I connect JSON Merge Patch to Gemini, can I use the same connection in Claude or ChatGPT later?

    Yes, and that's the point: the connection is yours, not Gemini's. You paste the same link in any AI you use, and there's nothing new to set up or pay again. Connect a new AI and JSON Merge Patch is already there.

  • 03

    What does ZCode need to connect to JSON Merge Patch?

    Just the link. The hosted Connector handles access on our side, so you don't configure headers or tokens in ZCode. For remote services, the type is HTTP and the URL is your link.

  • 04

    What can I actually ask Gemini to do with JSON Merge Patch?

    Whatever the Connector covers: check data, run actions and bring answers back. The Connector page lists every capability your AI gains, with real examples you can copy.

  • 05

    Gemini doesn't show the Connector. What do I check?

    Open Settings, MCP Servers and check the server is enabled, confirm the URL was pasted exactly as copied, and confirm the Connector is active in your Vinkius account. A deactivated Connector stops responding.

  • 06

    Can I remove the access later?

    Remove the server in Settings, MCP Servers and it's out of your work. Your Vinkius account keeps the connection and its history either way, ready for the next AI.

  • More questions about JSON Merge Patch? The Connector page answers them. See everything the JSON Merge Patch Connector can do

About the Connector

What JSON Merge Patch adds to your AI.

Once you connect it, your AI can take real actions in JSON Merge Patch when you ask. The Connector page lists every capability in detail, alongside the latency we measure in production and prompts worth trying first.

See everything the JSON Merge Patch Connector can do