GraphQL Mesh is an MIT-licensed TypeScript framework and gateway that exposes non-GraphQL services — REST, OpenAPI/Swagger, SOAP/WSDL, gRPC, Apache Thrift, OData, and databases — through a single GraphQL schema, and it is aimed at developers and platform teams building GraphQL Federation subgraphs or supergraphs.

What it is

GraphQL Mesh is a GraphQL Federation framework and gateway. It collects API schema specifications from source services, creates a runtime instance of a fully-typed SDK for those services, converts the specs into a GraphQL schema, applies custom schema transformations and extensions, and then produces either a Federation subgraph or a Federation-compatible supergraph. It handles both GraphQL Federation and non-GraphQL Federation subgraphs, and it also wraps non-GraphQL services such as REST and gRPC, plus databases such as MongoDB, MySQL, and PostgreSQL.

The concrete problem it solves is the cost of reaching data that does not speak GraphQL. Developers who need data from gRPC, OpenAPI/Swagger, OData, SOAP/WSDL, Apache Thrift, Mongoose, PostgreSQL, Neo4j, or GraphQL sources would otherwise hand-write clients and mapping layers for each one, and would inherit whatever typing, legacy, or specification gaps those backends carry. GraphQL Mesh replaces that per-service glue with a GraphQL query and mutation surface, and it lets developers modify output schemas, link types across schemas, merge schema types, and add custom GraphQL types and resolvers. It acts as a proxy to the data, using common libraries to wrap existing API services.

Key capabilities

• Converts API specifications into a GraphQL schema and generates a runtime instance of a fully-typed SDK for the wrapped services.
• Generates a Federation subgraph, or a Federation-compatible supergraph, from collected source schemas.
• Supports source APIs including gRPC, OpenAPI/Swagger, OData, SOAP/WSDL, Apache Thrift, Mongoose, PostgreSQL, Neo4j, and GraphQL.
• Applies custom schema transformations and schema extensions, and allows custom GraphQL types and resolvers.
• Merges schema types and links types across schemas, so records from separate backends can be joined in one schema.
• Runs in two shapes: a local GraphQL schema inside a service or application (with GraphQL execute), or a deployed gateway layer in front of internal services.

Who uses it and how

• Platform teams that need one GraphQL Federation supergraph or subgraph in front of a mix of gRPC, REST, SOAP, and OData backends.
• Application developers who embed the schema locally in their own service and query remote non-GraphQL APIs through GraphQL execute, rather than shipping dedicated clients.
• Teams modernising legacy API services whose chosen schema specification is rigid or non-typed, using transformations to reshape output without touching the backend.
• Gateway deployments where Mesh sits as the internal service layer, proxying to existing APIs and databases rather than replacing them.

Getting started

The command-line tool ships as the npm package @graphql-mesh/cli, and setup follows the Getting started guide at the-guild.dev/graphql/mesh, with separate reference pages for Supported Source APIs and Schema Transformations.

How it compares

No paid products replaced by this project are listed among the facts, and no comparable tools are named either, so GraphQL Mesh stands alone in this registry on that axis.

When to use it

Choose it when the backend estate is genuinely mixed — gRPC, OpenAPI, SOAP, OData, Thrift, or databases — and a Federation subgraph or supergraph must sit on top, since that is exactly the wrapping and transformation work it removes. The honest caveats are that the README excerpt here is sparse and defers nearly all detail to the external documentation site, and that running it as a gateway means operating another hop in front of internal services, which some teams will not want. The MIT licence is unambiguous, and the project is actively maintained with a recent push, so the uncertainty is in operating surface rather than in licensing.