What does this MCP actually do?

It takes a GraphQL query that uses fragments and inlines those fragments into a single, flat query string that is compatible with standard endpoints.

Why do I need to inline fragments?

Many GraphQL servers do not support fragment spreads. This MCP ensures your AI's queries work by removing those spreads before the request is sent.

Which AI clients can use this?

You can use this with any MCP-compatible client, including Claude, Cursor, Windsurf, and VS Code.

Is the merging process predictable?

Yes, the capability uses deterministic string manipulation to ensure the output is consistent.

Do I need to host this myself?

No, Vinkius hosts and manages the MCP for you. You just connect it to your client.

What does the merge_graphql_fragments capability actually do?

It takes a GraphQL query string with fragments and returns a single, flattened query string where all fragment spreads have been replaced by their actual field definitions.

Does it support nested fragments?

Yes, the capability recursively processes fragment definitions to ensure all levels of nesting are resolved into the final query string.

What happens if a fragment is not defined?

The capability will return the merged_query_string as processed so far, along with an unresolved_fragments list containing the names of the missing fragments.

An astronaut overseeing a futuristic data hub

Download PDF Markdown Version

Connect GraphQL Fragment Merger 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. Get valid, single-string queries for any GraphQL endpoint.

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 GraphQL Fragment Merger.

01
Merge graphql fragments
This capability takes a GraphQL query containing fragments and inlines them into a single, flat string. It replaces all spread operators with their actual field definitions.

Real work

What teams actually run

API Compatibility

Use this when your AI client generates queries that the target GraphQL server rejects due to fragment usage.

Automated Query Cleaning

Your agent can automatically flatten queries before sending them to a production API.

Debugging AI Outputs

Verify that fragmented queries can be correctly converted into standard formats.

One connector, every AI

GraphQL Fragment Merger 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 GraphQL Fragment Merger 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

691ms average. Fast in production.

GraphQL Fragment Merger is checked daily against the live service.

Daily averagePeak 927ms

Oct 3Today

Fastest day: 541ms
Slowest day: 927ms
14-day trend: Slowing+24%

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 GraphQL Fragment Merger, so you can see the experience inside your AI.

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

GraphQL Fragment Merger Connector

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

Connector linkhttps://edge.vinkius.com/vk_preview_FF6uqVOpEFqWYmM3ysP7BLOCgkZbenjL7WWaqQoA/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 — GraphQL Fragment Merger capabilities are ready to use.

Configuration · claude_desktop_config.jsonCopy

{
  "mcpServers": {
    "graphql-fragment-merger-mcp": {
      "url": "https://edge.vinkius.com/vk_preview_FF6uqVOpEFqWYmM3ysP7BLOCgkZbenjL7WWaqQoA/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 GraphQL Fragment Merger in Claude and other AIs

See all the AI clients this connector works with ↑

Who it's for

Built for the work GraphQL Fragment Merger owners hand off.

This is for developers building or using AI agents that interact with GraphQL APIs.

01
Frontend Engineers
They hand off complex queries to the AI to ensure they match API requirements.
02
Backend Developers
They use this to ensure AI-generated requests don't break standard GraphQL implementations.
03
AI Agent Builders
They integrate this MCP to handle the translation between LLM output and API input.

FAQ

Questions GraphQL Fragment Merger owners ask.

01
What does this MCP actually do?
It takes a GraphQL query that uses fragments and inlines those fragments into a single, flat query string that is compatible with standard endpoints.
02
Why do I need to inline fragments?
Many GraphQL servers do not support fragment spreads. This MCP ensures your AI's queries work by removing those spreads before the request is sent.
03
Which AI clients can use this?
You can use this with any MCP-compatible client, including Claude, Cursor, Windsurf, and VS Code.
04
Is the merging process predictable?
Yes, the capability uses deterministic string manipulation to ensure the output is consistent.
05
Do I need to host this myself?
No, Vinkius hosts and manages the MCP for you. You just connect it to your client.
06
What does the merge_graphql_fragments capability actually do?
It takes a GraphQL query string with fragments and returns a single, flattened query string where all fragment spreads have been replaced by their actual field definitions.
07
Does it support nested fragments?
Yes, the capability recursively processes fragment definitions to ensure all levels of nesting are resolved into the final query string.
08
What happens if a fragment is not defined?
The capability will return the merged_query_string as processed so far, along with an unresolved_fragments list containing the names of the missing fragments.

Explore

More in Developer Tools

Connect GraphQL Fragment Merger to Claude, Cursor, ChatGPT & more

Connect GraphQL Fragment Merger to ChatGPT and Claude

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