Skip to content
GraphQL Mesh — Query anything, run anywhere
TypeScript JavaScript Other
Branch: master
Clone or download

Latest commit

Latest commit c314747 Apr 5, 2020


Type Name Latest commit message Commit time
Failed to load latest commit information.
.github/workflows Skip MacOS in CI Apr 3, 2020
.vscode align all config stuff Mar 18, 2020
examples Update TripPin example Apr 5, 2020
packages Thrift handler (#195) Apr 5, 2020
website Thrift handler (#195) Apr 5, 2020
.gitignore Remove yarn.lock Mar 27, 2020
LICENSE Add MIT LICENSE (#141) Mar 26, 2020 Thrift handler (#195) Apr 5, 2020
jest.config.js repo cleanup, added some tests, fixed ci Feb 27, 2020
lerna.json v0.0.19 Apr 2, 2020
package.json Retrigger Apr 2, 2020
renovate.json Merge branch 'master' into update-json-schema Mar 12, 2020
tsconfig.json Use canary toolkit (#181) Apr 2, 2020

GraphQL Mesh

npm version CI Discord Chat code style: prettier renovate-app badge

Note: this project is early and there will be breaking changes along the way

Mesh GIF

GraphQL Mesh allows you to use GraphQL query language to access data in remote APIs that don't run GraphQL (and also ones that do run GraphQL). It can be used as a gateway to other services, or run as a local GraphQL schema that aggregates data from remote APIs.

The goal of GraphQL Mesh is to let developers easily access services that are written in other APIs specs (such as gRPC, OpenAPI/Swagger, OData, SOAP/WSDL, Apache Thrift, and also GraphQL) with GraphQL queries and mutations.

GraphQL Mesh gives the developer the ability to modify the output schemas, link types across schemas and merge schema types. You can even add custom GraphQL types and resolvers that fit your needs.

It allows developers to control the way they fetch data, and overcome issues related to backend implementation, legacy API services, chosen schema specification and non-typed APIs.

GraphQL Mesh is acting as a proxy to your data, and uses common libraries to wrap your existing API services. You can use this proxy locally in your service or application by running the GraphQL schema locally (with GraphQL execute), or you can deploy this as a gateway layer to your internal service.

Note: GraphQL Mesh doesn’t aim to magically create your utopic public GraphQL schema - it’s just an easy-to-use proxy to your data, and you should consider implementing another layer that exposes your public data the way you need it to be.

How it works?

The way GraphQL Mesh works is:

  1. Collect API schema specifications from services
  2. Create a runtime instance of fully-typed SDK for the services.
  3. Convert API specs to GraphQL schema
  4. Applies custom schema transformations and schema extensions
  5. Creates fully-typed, single schema, GraphQL SDK to fetch data from your services.

Getting Started


GraphQL Mesh comes in multiple packages, which you should install according to your needs.

To get started with the basics, install the following:

$ yarn add graphql @graphql-mesh/runtime @graphql-mesh/cli

The, you need to install a Mesh handler, according to your API needs. You can see the list of all available built-in handlers in this README, under the Supported APIs section.

For example, if you wish to use OpenAPI handler, install the handler that matches you needs:

$ yarn add graphql @graphql-mesh/openapi

Then, this handler will be available for you to use in your config file.

Basic Usage

Supported APIs

Schema Transformations

TypeScript Support

You can’t perform that action at this time.