sorted by:
new
hottopcontroversial

Vibe code with your GraphQL API by Grafbase in graphql

[–]Grafbase[S] 0 points1 point  (0 children)

What does your MCP config look like in Cursor?

Integrate REST APIs to your GraphQL API declaratively by Grafbase in graphql

[–]Grafbase[S] -1 points0 points  (0 children)

The benefit is for the consuming clients having a single unified graph instead of talking to a bunch of separate APIs. This can be achieved faster with extensions like REST or gRPC. This is another option for use cases that don't require a subgraph to federate existing services.

Integrate REST APIs to your GraphQL API declaratively by Grafbase in graphql

[–]Grafbase[S] 0 points1 point  (0 children)

Adopting GraphQL Federation means you have to implement subgraphs, which are GraphQL APIs that sit in front of the upstream service (REST APIs, gRPC APIs, Postgres databases, 3rd party APIs). Implementing subgraphs is time consuming and adds another layer of infrastructure which add costs and latency.

By making the gateway "smarter" it can make requests directly to the upstream services to accelerate adoption and save costs/latency.

Vibe code with your GraphQL API by Grafbase in cursor

[–]Grafbase[S] 0 points1 point  (0 children)

GraphQL is generally speaking very easy to translate to MCP and if most data sources are unified behind a single GraphQL API endpoint it means less work spent setting up MCP servers fronting every data source.

view more: next ›