How does this MCP prevent data loss?

Instead of the AI rewriting the whole file, it only sends the changes. The MCP then merges those changes into the original, so no existing data is lost or skipped.

What standard does this use for merging?

This MCP uses the RFC 7396 standard for JSON Merge Patching.

Can I use this with Claude or Cursor?

Yes, you can use this with any MCP-compatible client including Claude, Cursor, and Windsurf.

How do I delete a key using this MCP?

You can delete a key by providing a patch where that specific key is set to null.

Is there a limit to the JSON file size?

This MCP is specifically designed to handle massive files that would otherwise overwhelm an AI agent's context window.

Yes, following RFC 7396, setting a key to null in the patch will remove it from the target.

Is this better than normal JS merge?

Yes, it safely handles deep object merging and null-deletions which simple object spread (...) fails at.

An astronaut overseeing a futuristic data hub

Download PDF Markdown Version

Connect JSON Merge Patch to ChatGPT, Claude and Gemini

Set it up once and it works in ChatGPT, Claude, Cursor, and any other client you love. It all runs safely in the background, so you can relax and focus on what really matters. Update large JSON files without losing data or keys.

Ask AI about this Connector

Developed, maintained, and hosted by Vinkius.

MCP VERIFIED · PRODUCTION READY · VINKIUS GUARANTEED

Waiting for input…

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

Your AI does the work. We keep it safe and sound.

No other AI tool gives you this. Your workflow runs in the client you already love, your account stays protected, and you decide what the agent can and cannot do. It is the whole reason to make the switch.

Each Connector lives inside our infrastructure, the same place where your workflow runs. The three things below are already part of it, working quietly in the background so you never have to think about them. Nothing to add, nothing to set up, nothing to worry about.

V8 Isolate01

Each Connector runs inside its own sealed environment.

Each Connector runs inside its own sealed V8 runtime — no access to your files, your system, or other servers. A Connector never sees past its own request.

Kill Switch02

One switch stops every agent. Instantly.

One action deactivates every Connector, revokes every token, and ends every session at once. AI Governance keeps the record.

FinOps per User03

Spending limits that pause instead of surprise.

Every user keeps their own connections and credentials, isolated from everyone else. Anything that would cross your spending limit is held for your approval, not billed.

Three controls, built into the layer your AI connects through.

Curated set · 1 capability

We ship only the actions that matter.

Capability set01 / 01

01

1 capability in this set.

Part of 1 available through JSON Merge Patch.

01
Apply patch
This capability applies an RFC 7396 JSON Merge Patch to a target object. It takes the original JSON and your delta patch to produce a merged result without rewriting the entire dataset.

Real work

What teams actually run

Config Management

Update a single flag in a massive application configuration file.

Database Patching

Modify specific user attributes in a large JSON-based database.

State Management

Apply incremental changes to a complex application state object.

Key Removal

Delete specific keys from a payload by sending a null patch.

Automate a task

Put JSON Merge Patch to work on one thing.

Step-by-step automations your AI runs through this Connector: the workflow, the prompts to start with, and the exact capabilities behind each move.

How to update JSON

One connector, every AI

JSON Merge Patch works with the most popular AI clients.

These are the most popular clients, each with a step-by-step guide: one link, set up once, with governance and visibility built in. And because everything runs on the MCP standard, the same connection also works in any other compatible client — nothing to rebuild.

Building your own app? The connector is yours to use.

You don't need a client to put JSON Merge Patch to work: the same hosted connection plugs into your own applications and agent code, with the same governance on every request. Build with it, chat with it — one connection for both.

Observed, not estimated

906ms average. Fast in production.

JSON Merge Patch is checked daily against the live service.

Daily averagePeak 1085ms

Oct 3Today

Fastest day: 742ms
Slowest day: 1085ms
14-day trend: Improving-21%

Connect your client

One URL. Every client.

Activate the Connector, copy your link, and paste it into the client you already use. 1 capability arrives ready to run.

Preview access · not provider authentication

The vk_preview_* token belongs to Vinkius preview infrastructure. It lets Claude discover and display the capabilities of JSON Merge Patch, so you can see the experience inside your AI.

It does not authenticate your account with JSON Merge Patch. Actions requiring credentials or live account data may not run until you activate the Connector and authorize the service.

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

Claude Desktop

Follow the steps below to connect in seconds.

1In Claude Desktop, open Settings → Connectors.
2Click “Add custom connector” and paste the connector link above as the remote MCP server URL.
3Click Add and start a new chat — JSON Merge Patch capabilities are ready to use.

Configuration · claude_desktop_config.jsonCopy

{
  "mcpServers": {
    "json-merge-patch-mcp": {
      "url": "https://edge.vinkius.com/vk_preview_jagY81WpYhec0VzgLCycaUIZKOPxhooBwDz9HBff/mcp"
    }
  }
}

Claude
ChatGPT
Cursor
VS Code
Windsurf
Claude Code
JetBrains
Cline

Step-by-step instructions for each client are in the guide. How to connect

Guided setup for Claude? Set up JSON Merge Patch in Claude and other AIs

See all the AI clients this connector works with ↑

Who it's for

Built for the work JSON Merge Patch owners hand off.

This is for developers and engineers who manage complex, large-scale JSON configurations.

01
DevOps Engineers
They hand off configuration updates to an agent to avoid manual syntax errors.
02
Backend Developers
They use it to update large database records or state objects via an AI client.
03
Data Engineers
They apply specific transformations to large datasets without full rewrites.

FAQ

Questions JSON Merge Patch owners ask.

01
How does this MCP prevent data loss?
Instead of the AI rewriting the whole file, it only sends the changes. The MCP then merges those changes into the original, so no existing data is lost or skipped.
02
What standard does this use for merging?
This MCP uses the RFC 7396 standard for JSON Merge Patching.
03
Can I use this with Claude or Cursor?
Yes, you can use this with any MCP-compatible client including Claude, Cursor, and Windsurf.
04
How do I delete a key using this MCP?
You can delete a key by providing a patch where that specific key is set to null.
05
Is there a limit to the JSON file size?
This MCP is specifically designed to handle massive files that would otherwise overwhelm an AI agent's context window.
06
Can it delete keys?
Yes, following RFC 7396, setting a key to null in the patch will remove it from the target.
07
Is this better than normal JS merge?
Yes, it safely handles deep object merging and null-deletions which simple object spread (...) fails at.