Api Composition Gateway
Give your agent a gateway MCP server to compose or orchestrate multiple backend API calls into one agent-friendly surface while you build integrations.
Overview
api-composition-gateway is a MCP server for the Build phase that helps agents work through API composition and gateway-style orchestration over streamable-http.
What is this MCP server?
- Hosted api-composition-gateway MCP on Cloudflare Workers via streamable-http
- Designed for agent-driven API composition instead of hand-writing glue routes for every combo
- Fits BFF-style patterns for solo SaaS and agent products exposing unified tool endpoints
- Remote URL registration—no local Node service to maintain
- Version 1.0.0 with MCP schema 2025-09-29 and GitHub source api-composition-gateway-api
- Version 1.0.0 MCP server
- One streamable-http remote on Cloudflare Workers
- Repository: github.com/lazymac2x/api-composition-gateway-api
What problem does it solve?
Solo builders drown in one-off scripts when every feature needs a different combination of third-party and internal API calls.
Who is it for?
Builders creating agent tools or SaaS backends that need a single MCP-mediated surface over several HTTP APIs.
Skip if: Products with a single monolithic API and no multi-service composition, or teams that require on-prem only MCP with no remote Workers.
What do I get? / Deliverables
Your agent can use composition-gateway MCP tools to design and invoke unified API flows instead of fragmenting logic across repos.
- Remote MCP gateway connection for composition workflows
- Agent-guided multi-API call patterns aligned to your product boundary
- Fewer bespoke glue scripts during integration sprints
Recommended MCP Servers
Journey fit
Composing external APIs into a product-shaped interface is core Build work, especially when wiring backends and agent tools. Gateway composition is integration plumbing—canonical on the integrations subphase rather than frontend or docs.
How it compares
MCP-backed composition gateway, not a Terraform module or a standalone API design skill.
Common Questions / FAQ
Who is api-composition-gateway for?
Solo developers and indie teams building SaaS or agent products who need to orchestrate multiple HTTP APIs through their coding agent.
When should I use api-composition-gateway?
Use it during Build integrations while you define BFF or gateway routes that combine auth, billing, and domain APIs for your app or MCP tools.
How do I add api-composition-gateway to my agent?
Configure the remote MCP server URL https://api.lazy-mac.com/api-composition-gateway/mcp as streamable-http in your agent MCP list and reload the workspace.