An astronaut overseeing a futuristic data hub

Connect LLM JSON Repair Utility to ChatGPT and Claude

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. Stop your automation from breaking due to syntax errors.

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.

ChatGPTClaudeCursorPerplexityGeminiMicrosoft CopilotRaycastMeta AI

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.

A futuristic MCP client docking bay
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 · 3 capabilities

We ship only the actions that matter.

Capability set01 / 01

01-03

3 capabilities in this set.

Part of 3 available through LLM JSON Repair.

  1. 01

    Extract JSON from text

    This capability pulls JSON objects out of conversational text or markdown blocks. It ignores the surrounding filler to find the raw data.

  2. 02

    Repair JSON string

    This capability fixes broken JSON structures like missing braces or unquoted keys. It uses a state-machine to mend the string without adding fake data.

  3. 03

    Validate JSON integrity

    This capability checks if a JSON string follows RFC 8259 standards. It identifies syntax violations before you try to parse the data.

Real work

What teams actually run

01

Automated Data Extraction

Pull structured data from a long, chatty response from your AI client.

02

Pipeline Reliability

Ensure that truncated LLM outputs don't break your downstream data processing scripts.

03

Validation Checks

Verify that a JSON string is valid before passing it to a strict parser.

04

Cleaning LLM Output

Fix single quotes or missing quotes on keys that frequently occur in model responses.

One connector, every AI

LLM JSON Repair 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 LLM JSON Repair 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

818ms average. Fast in production.

LLM JSON Repair is checked daily against the live service.

Daily averagePeak 1192ms
Oct 3Today
Fastest day
616ms
Slowest day
1192ms
14-day trend
Stable-2%

Connect your client

One URL. Every client.

Activate the Connector, copy your link, and paste it into the client you already use. 3 capabilities arrive 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 LLM JSON Repair, so you can see the experience inside your AI.

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

LLM JSON Repair Connector

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

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

Claude Desktop

Follow the steps below to connect in seconds.

  1. 1In Claude Desktop, open Settings → Connectors.
  2. 2Click “Add custom connector” and paste the connector link above as the remote MCP server URL.
  3. 3Click Add and start a new chat — LLM JSON Repair capabilities are ready to use.
Configuration · claude_desktop_config.jsonCopy
{
  "mcpServers": {
    "llm-json-repair-utility-mcp": {
      "url": "https://edge.vinkius.com/vk_preview_ZzkK2sMb63roNsDq7PgNLGQ6BP95NpuKBwpjhljI/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 LLM JSON Repair in Claude and other AIs

See all the AI clients this connector works with ↑

Who it's for

Built for the work LLM JSON Repair owners hand off.

This MCP is built for developers building automated pipelines that rely on LLM outputs.

  • 01

    Backend Engineers

    They use this to prevent JSON parsing errors from crashing their production services.

  • 02

    AI Agents Developers

    They use this to ensure the data their agents produce is actually usable by other capabilities.

  • 03

    Data Engineers

    They use this to clean up messy, unstructured text into valid JSON formats.

FAQ

Questions LLM JSON Repair owners ask.

  • 01

    How does this MCP fix JSON without hallucinating?

    It uses a deterministic state-machine approach. It only fixes structural issues like missing braces or quotes rather than inventing new data.

  • 02

    Can it fix JSON that was cut off mid-sentence?

    Yes. It handles structural truncation by closing unclosed braces or brackets to make the object valid.

  • 03

    What kind of errors does it fix?

    It fixes trailing commas, unquoted keys, single quotes, and missing closing characters.

  • 04

    Does it work with any AI client?

    It works with any MCP-compatible client, including Claude, Cursor, and Windsurf.

  • 05

    How do I get JSON out of a conversational response?

    You can use the extract_json_from_text capability to pull the JSON block out of any text containing conversational filler.

  • 06

    How does this differ from using an LLM to fix JSON?

    Unlike probabilistic LLMs, this server uses a deterministic state machine. This means it only fixes structural issues like missing brackets or trailing commas without inventing or changing the actual data content.

  • 07

    Can I extract JSON from a long chat response?

    Yes, you can use the extract_json_from_text capability to locate and isolate the JSON object or array within a larger block of conversational text.

  • 08

    What happens if the JSON is truncated due to token limits?

    The repair_json_string capability tracks the nesting depth of all open braces and brackets and automatically appends the necessary closing characters to restore structural integrity.

Connect LLM JSON Repair to Claude, Cursor, ChatGPT & more