

They act as a bridge between your API and AI assistants: instead of teaching an LLM how to query your database, you expose a set of ready-made, structured tools.
Suddenly, natural language queries like:
Show me women’s shoes under 100 PLN available in the Polish channel
…turn into real, validated API calls — safely, securely, and without building a new UI or marketplace plugin.
If your company already uses GraphQL, you are closer to this future than you might think.
For e-commerce, SaaS, or any data-driven business, this means: product discovery, catalog browsing, and customer support become instantly AI-ready.
Most APIs aren’t “assistant-friendly” out of the box. They require careful typing, validation, and simplification.
That’s why we combined the Saleor GraphQL API with FastMCP Cloud — the easiest way to host and share MCP servers — and proved how quickly AI assistants can start working with real product data.
GraphQL is schema-first: your inputs and outputs are already explicitly typed. That’s exactly what an MCP server needs.
With Ariadne Codegen and FastMCP we can:
Result: You turn your GraphQL schema into an AI-ready MCP server in minutes.
To prove this in practice, we built an MCP server on top of Saleor, an open-source e-commerce platform with a rich GraphQL API.
We focused on the Products query, which is both powerful and complex:
Instead of teaching ChatGPT how to write cursor-based queries, we wrapped Saleor’s GraphQL with Ariadne Codegen + FastMCP. The assistant can now call typed, validated tools directly.
And to make it real, we used nimara.store, Mirumee’s demo Saleor storefront, as the test environment.
Your pyproject.toml does most of the heavy lifting:
That’s it. Ariadne Codegen pulls down the schema, processes your queries, and spits out a fully typed client plus models.
Example queries.graphql:
By defining a Product fragment, we are getting a reusable product type that can be shared across multiple queries in the app. This keeps both the GraphQL and the generated Python code clean, consistent, and easy to extend.
Run codegen once, and you are ready to write the MCP layer.
The graphql_client module is generated using Ariadne Codegen. We reuse the where, sort, and search definitions from the GraphQL schema, and by defining the Product fragment, we also create the corresponding Product model. In addition, the client includes methods automatically generated from GraphQL.
FastMCP makes it easy to register tools. You can describe the input for the LLM in the comments using Annotated, and provide the overall tool description through a Python docstring:
For the complete example, check our Ariadne Codegen example repository on GitHub.
To run the service, use:
You can test your MCP server directly in Postman. The Postman team has added first-class support for MCP requests, which makes it easy to call your endpoints, inspect request and response shapes, and validate everything before connecting an AI assistant. See the Postman MCP documentation for details.
You already have an MCP server, now let’s connect it to ChatGPT.
All we need is a public URL that the LLM can access. With FastMCP Cloud, this is straightforward: just push your code to a GitHub repo and register it with fastmcp.cloud. That is all it takes to deploy your server to the cloud.
Once you have a working URL, you can connect it in ChatGPT:



Once registered, your MCP tools appear directly inside ChatGPT. From there, you can search, fetch, and query products from Saleor using natural language.

Through this implementation, we learned:
Imagine your sales team, customer support, or even clients directly querying your product catalog in natural language — powered by your existing GraphQL API, no new frontend required.
Instead of expensive UI projects or brittle plugins, you turn your current schema into the control panel for AI assistants.
This approach shows how an existing GraphQL schema can be transformed into an AI-ready MCP server — quickly, safely, and without reinventing your architecture. Along the way, we’ve seen:
With these tools, your API becomes more than just an integration layer — it becomes a direct interface for AI assistants.