Without a Gateway
Multiple URLs, credentials, and client configurations that drift as tools change.
Connect once. Give agents every tool they need.
Combine multiple MCP deployments behind one stable endpoint. Add or remove servers as your agent’s job changes—without updating every client configuration.
Why a Gateway
Stop making every client understand your infrastructure.
With a Gateway
One URL, one access policy, and a tool surface you can evolve centrally.
How it works
From separate servers to one endpoint in three steps.
Deploy the servers you need
Run each MCP server as its own MCPLambda deployment so it keeps independent logs, analytics, secrets, and lifecycle controls.
Create a Gateway
Select up to 20 running deployments in one project, then choose OAuth, API key, or public access for the combined endpoint.
Connect your client once
Use the Gateway URL in Claude, Cursor, VS Code, or your own MCP client. Add or remove deployments later without changing that URL.
Access control
Choose who can use the combined toolset.
Authentication is Gateway-wide, so clients have one clear access path for every exposed tool.
OAuth
Each user signs in and grants access from their MCP client. Best for teams and user-specific access.
API key
Trusted clients send one expiring key in the X-API-Key header. Rotate the key from the Gateway details page.
Public
Anyone with the URL can invoke every exposed tool. Use only when all member tools are safe for anonymous access.
Gateway OAuth authenticates the MCP client to MCPLambda. It does not replace OAuth or credentials that an underlying deployment needs to call a third-party service.
Built for focused toolsets
Give each agent the tools for its job.
A coding agent toolbelt
Combine repository, issue tracker, documentation, and deployment tools behind one client entry for every developer.
An internal operations assistant
Give an agent a governed endpoint for the operational systems it needs while each underlying server stays independently manageable.
Project-specific tool surfaces
Create a focused Gateway per project so agents see the tools for the job instead of one sprawling organization-wide catalog.
Clear lifecycle boundaries
Your deployments stay independent.
- Stopping or deleting a Gateway does not stop or delete its member deployments.
- Each deployment keeps its own logs, analytics, secrets, scaling, and direct endpoint.
- Tool names are prefixed by deployment to avoid collisions in the combined tool list.
- Membership updates briefly reconnect the Gateway; clients may need to refresh tool discovery.
One connection. A toolset that keeps up.
Create a Gateway from running deployments in your MCPLambda project.
Create a GatewayQuestions before you connect
The practical details behind one URL for many deployments.
-
What is an MCPLambda Gateway?
A Gateway combines tools from multiple running MCPLambda deployments behind one stable MCP endpoint. You manage the member deployments independently while clients connect to the Gateway URL.
-
Does changing members change the Gateway URL?
No. You can add or remove deployments without changing the URL. The Gateway briefly reconnects while its tool list refreshes, and connected clients may need to reconnect to discover the updated list.
-
How does Gateway authentication work?
Authentication is configured once at the Gateway level and applies to every exposed tool. Choose OAuth, an expiring API key sent with X-API-Key, or public access. OAuth authenticates the client to your Gateway; it does not broker OAuth to third-party SaaS products.
-
What happens to member deployments when I stop or delete a Gateway?
Nothing is deleted or stopped underneath. Member deployments keep running and remain independently manageable; only the combined Gateway endpoint is affected.
-
How does MCPLambda avoid tool-name collisions?
Tools are automatically prefixed by their member deployment so similarly named tools can coexist in the same Gateway.
-
What are the current Gateway limits?
A Gateway can include up to 20 running deployments from the same project. A deployment can belong to one Gateway at a time.
