Graphql Rest Bridge
Let your coding agent call GraphQL and REST through one Cloudflare Workers MCP bridge while you wire product APIs.
Overview
graphql-rest-bridge is a MCP server for the Build phase that exposes a hosted GraphQL–REST bridge so agents can work across API styles through one remote endpoint.
What is this MCP server?
- Hosted streamable-http MCP remote at api.lazy-mac.com—no local worker deploy required to register the server.
- GraphQL–REST bridge pattern for agents that need unified access without hand-rolling converters each sprint.
- Pairs with Cloudflare Workers deployment model for edge-adjacent API glue.
- MCP server v1.0.0 with server.schema.json 2025-09-29 metadata for registry compatibility.
- Open-source implementation at lazymac2x/graphql-rest-bridge-api on GitHub for self-host or fork.
- MCP server version 1.0.0
- 1 streamable-http remote endpoint documented in server metadata
- Repository: github.com/lazymac2x/graphql-rest-bridge-api
What problem does it solve?
Your agent keeps juggling separate GraphQL and REST call patterns, and every integration task turns into bespoke adapter code.
Who is it for?
Indie builders on Cloudflare Workers who already have GraphQL or REST services and want agent-driven integration work without maintaining a local MCP binary.
Skip if: Teams that need a full managed API gateway, heavy transformation DSL, or on-prem-only MCP with no remote HTTP transport.
What do I get? / Deliverables
After you register the remote MCP server, the agent can route bridge operations through a single streamable-http connection while you focus on product logic.
- Registered remote MCP server in the agent
- Agent-callable bridge tools for mixed GraphQL/REST workflows
- Faster integration iteration without per-protocol one-off scripts
Recommended MCP Servers
Journey fit
API shape decisions and client wiring happen during Build when backends and third-party services are connected. Integrations is where solo builders translate schemas, proxies, and mixed protocol stacks into shippable endpoints.
How it compares
MCP API bridge on Workers, not a GraphQL IDE skill or database MCP.
Common Questions / FAQ
Who is graphql-rest-bridge for?
Solo builders and small teams shipping API-backed products who use Claude Code or Cursor and want one MCP entry point for GraphQL–REST bridging on lazy-mac.com infrastructure.
When should I use graphql-rest-bridge?
Use it during Build integrations when you are connecting services, prototyping BFF routes, or letting an agent exercise mixed-protocol APIs against your Workers stack.
How do I add graphql-rest-bridge to my agent?
Add the remote MCP URL https://api.lazy-mac.com/graphql-rest-bridge/mcp with streamable-http transport in your agent MCP config, then confirm the server appears in the tool list.