Speakeasy

That's the difference between an MCP pilot and an MCP rollout.

No configuration per user. No manual provisioning per team. No tickets to IT. Just deploy, and your org has access.

The hardest part of rolling out MCP across an org isn't building the servers. It's everything that happens after. 🧵

We've been building an internal Claude Code plugin system at Intercom with 13 plugins, 100+ skills, and hooks that turn Claude into a full-stack engineering platform. Lots done, more to do. Here's a thread of some highlights.

If you're building MCP servers, trying to run them in production, or thinking about what it takes to make your whole org work through Claude, we'd love to talk. speakeasy.com/mcp

The infrastructure for making your entire organization AI-native exists today. The bottleneck was never the AI itself.

One week since we launched Speakeasy MCP Platform. Here's what we've seen. 🧵

And when things go wrong: error categorization, version correlation, and root cause signals. Not just a dashboard that tells you something broke. Context that helps you understand why and fix it.

Latency, error rates, and usage patterns broken down by individual tool. Understand adoption across your org and catch bottlenecks before they become incidents.

Once MCP servers hit production, most teams are flying blind. 🧵 They can see that tool calls are happening. They can't see why they're failing, which version handled a request, or whether agents are using tools the way they intended.

This is what AI-native looks like in practice.

"I don't want anyone using internal UIs or opening SaaS apps. The moment someone shifts a workflow to being AI-native it drops from a two-hour task down to minutes." Shreyas Kumar, Co-founder, Fermat

Fermat made Claude the operating system for their entire company. 100% of employees on Claude. 2 days to rollout. 500% MoM growth in AI usage. 🧵

Ok last MCP tweet I'll do for now: Imagine if we started with OpenAPI instead - would you be annoyed at people for having giant OpenAPI specs being dumped into context? No that's crazy, you'd be happy to have all the options but you'd want a better way to call them

the overindexing on CLIs is kind of insane to me it's building a primitive that's not portable, properly discoverable, has no good approval flow DCR / CIMD to APIs would go so much further but CLI is just the current hype thing