Skip to content
Vinkius

GraphQL Fragment Merger Connector for AI agents.

1 live capability

Flatten GraphQL fragments into single, valid queries.

Live agent request GraphQL Fragment Merger / Connector

Waiting for input…

AI Agent

Why people use GraphQL Fragment Merger

GraphQL Fragment Merger fixes broken GraphQL API requests

With this MCP, you just pass the messy query through. It does the recursive work for you, leaving you with a single, flat operation that is ready to run.

  • Claude
  • ChatGPT
  • Gemini
  • Cursor
  • Visual Studio Code
  • Windsurf

What Vinkius changes

You get a clean, flat query that works anywhere.

Use it from Claude, ChatGPT, Cursor or another AI client you already have.

One account · 6,100+ Connectors

  1. Real-world use case 01

    Fixing broken agent requests

    An engineer asks Claude to fetch user data, but the generated query uses fragments that the server rejects.

  2. Real-world use case 02

    Automating API testing

    A developer uses an agent to generate test payloads for a GraphQL API.

Complete set · 1capability

The complete GraphQL Fragment Merger capability set.

These are the exact actions your AI can choose when you ask it to work with GraphQL Fragment Merger.

Capability set01 / 01

01

1 capability in this set.

Part of 1 available through GraphQL Fragment Merger.

  1. 01 Capability

    Merge graphql fragments

    Takes a query with fragments and inlines them into the main operation. This ensures your API requests are valid even if the endpoint lacks fragment support.

Set up in minutes

One URL. Then ask GraphQL Fragment Merger to work.

Claude and ChatGPT only need the Connector URL. Copy it once, add it in settings, and use GraphQL Fragment Merger from the conversation.

Choose your client

Live preview
Advanced clients IDE · CLI

Claude · Web + desktop

Official guide ↗

Connector URL · ready to paste

Streamable HTTP
https://edge.vinkius.com/vk_preview_FF6uqVOpEFqWYmM3ysP7BLOCgkZbenjL7WWaqQoA/mcp
  1. Step 01

    Open Connectors

    In Claude Web or Claude Desktop, open Settings and choose Connectors.

  2. Step 02

    Add the URL

    Choose Add custom connector, name it GraphQL Fragment Merger, and paste the URL above.

  3. Step 03

    Turn it on in chat

    Select +, open Connectors, and enable GraphQL Fragment Merger for the conversation.

Where the request belongs

Work GraphQL Fragment Merger can move forward.

Built around the request

Backend engineers and API developers who use AI agents to automate data fetching or testing.

01

API Engineer

Uses this to ensure queries generated by Cursor or Claude do not fail against legacy GraphQL endpoints.

02

Frontend Developer

Ensures that AI-generated data fetching logic works perfectly with existing API structures.

Bring your own AI

Change the model, client or framework. Keep GraphQL Fragment Merger connected.

  • Claude
  • ChatGPT
  • Gemini
  • Cursor
  • VS Code
  • Windsurf
  • ZCode
  • Cline
  • Zed
  • Continue
  • Kiro
  • Roo Code
  • Zencoder
  • Goose
  • Void
  • Augment Code
  • Amp
  • Qodo
  • Tabnine
  • Pieces
  • Sourcegraph Cody
  • JetBrains
  • Warp
  • Amazon Q
  • Antigravity
  • BoltAI
  • Raycast
  • Jan
  • LM Studio
  • AnythingLLM
  • Open WebUI
  • Msty
  • Cherry Studio
  • LibreChat
  • TypingMind
  • Chorus
  • 5ire
  • n8n
  • LangChain
  • LlamaIndex
  • CrewAI
  • Vercel AI SDK

Before you connect

Questions about GraphQL Fragment Merger.

The practical details behind the request, access and result.

How does GraphQL Fragment Merger prevent API errors?

It removes all fragment spreads and replaces them with the actual fields, so your server receives a complete query it can understand.

Will GraphQL Fragment Merger work with nested fragments?

Yes. The capability recursively follows every fragment definition until the entire query is flattened into a single layer of fields.

Can I use GraphQL Fragment Merger with Claude or Cursor?

Absolutely. Any MCP-compatible client can use this to clean up queries before they are sent to your GraphQL endpoint.

Does GraphQL Fragment Merger change the actual data returned?

No. It only changes the structure of the query string itself. The fields being requested remain exactly the same.

Is GraphQL Fragment Merger useful for legacy APIs?

It is specifically designed for this. If your older API does not support modern fragment syntax, this capability makes your agent's queries compatible.

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.

One connection away

Give your agent a direct line to GraphQL Fragment Merger.

Connect GraphQL Fragment Merger once. Keep it beside 6,100+ managed Connectors when the next task needs more.

Explore every Connector No credit card required · Free tier available