Live LabsBuildersMCP2 hours

Build an MCP gateway: one front door for your tools

Every team is adding MCP servers. Without a gateway nobody knows which agent can call which tool. We put them behind one front door with access rules and a log.

You leave with

Several MCP servers behind one gateway, with authentication and an audit log of every tool call.

How the time is spent

  1. I do30 minParam builds it live

    I show what tool sprawl looks like in a real setup, then the same setup behind a gateway.

  2. We do48 minTogether, step by step

    We register three servers and route an agent through the gateway.

  3. You do42 minOn your own code

    You write access rules per team and prove a blocked call is blocked and logged.

What you will be able to do

Run MCP behind a gateway

One endpoint for every tool an agent can call.

Scope access

Decide which team and which agent can use which tool.

Audit tool calls

Answer who called what, and when.

Starts from

Before you come

For
Platform and backend engineers rolling out agents across teams.
You need
Docker. You have used at least one MCP server.
Stack
Docker, MCP, Python
Track
Hands-on agentic AI for engineers who ship.

More builders labs