Let us show you what a full enterprise MCP practice looks like end to end, built at TELUS over the past year.

The tour: IRIS, an n8n-based AI operations agent exposed as an MCP server — with a Slackbot front end — that routes real operational requests; n8n workflows that call MCP tools to automate the boring parts of running a platform; a shared "ai-dev" registry that catalogs the MCPs most useful across the org, so teams discover and reuse instead of rebuilding the same connector multiple times; and finally remote MCP hosting on Gizmos, our last-mile platform built on Cloudflare Workers — plus the OAuth wall every enterprise slams into. Dynamic Client Registration is the usual answer, and the usual disappointment; we'll cover why we went with Client ID Metadata Documents instead, and the tradeoffs behind that call. No product pitch — reusable patterns for any stack.

You'll leave with a map of the whole enterprise MCP stack — registry, workflow automation, agent front ends, remote hosting — the failure modes we hit, and where the spec and tooling are still rough.