Tool Runtime MCP Gateway
Route agent tools through an MCP gateway with telemetry you can actually review.
Built for: Platform and security-minded engineering teams that need observable, routed agent tool access—not a pile of unmanaged MCP servers.
Key takeaways
- 01A gateway is the control plane for many tools—not a substitute for product thinking.
- 02Telemetry makes agent loops reviewable: what was called, when, and with what outcome.
- 03Least-privilege allowlists beat auto-approve defaults in enterprise environments.
- 04This pattern pairs with large API surfaces like Procore and P6 that need routing discipline.
Technical overview
Why a gateway
When agents call many tools across environments, ad-hoc MCP servers become unmanageable. You need a control plane: routing, policy, and visibility.
Tool Runtime demonstrates an MCP gateway with telemetry—so you can see what the agent invoked, keep the loop observable, and package construction-facing tool surfaces with more confidence.
What you will learn
- Gateway responsibilities vs individual MCP servers
- Why telemetry is non-negotiable for production agent loops
- How routing supports safer, more deliberate tool exposure
Delivery note
Build Flows designs and implements gateway patterns suited to your identity, logging, and tool packs. Start a project brief to adapt this reference to your stack.
Build this in your environment
This is a proven pattern—not a product SKU. Tell us what you need and we'll scope how to deliver it in your stack.
Access & governance
Gateway telemetry should show which tools agents call. Restrict auto-approve lists; prefer least privilege per environment.
Full governance posture →Reproduce in 30 minutes
Reproduce (30 minutes)
- Clone the linked Tool Runtime construction repo.
- Run the gateway against a sandbox tool pack.
- Invoke two tools from an MCP client and inspect telemetry.
Video description
Source listing for the published walkthrough—useful for search and context.
Transcript(captions unavailable)
Captions were not available when this reference was published. Re-run publish after enabling YouTube captions to backfill transcript text for SEO and accessibility.
More like this
Nearby builds by capability and stack—useful context before you scope yours.
- Procore MCP ArchitectureRoute thousands of Procore API operations through MCP without drowning the model.
- Oracle Primavera P6 MCP ServerExpose 585 P6 operations over MCP—with offline XER analysis agents can actually use.
- Construct.Chat AgentsAI agents on live project data—MCP tools working against Procore in the open.
Source repository: github.com/charley-forey/toolruntime-construction-management
Need this capability in your environment?
Tell us the outcome you need. We will adapt the pattern—or design beyond it—across the systems you already run, with access and operability suitable for enterprise delivery.