Arcade.dev vs TrueFoundry: MCP Gateway Comparison
TrueFoundry publishes a head-to-head comparison with Arcade.dev, positioning themselves as a full AI control plane (MCP gateway + LLM routing + model deployment + governance) versus Arcade's focused play on agent authorization and MCP tooling. The comparison is unusually honest: Arcade is genuinely strong at OAuth brokering and tool catalogs (Smithery acquisition), but doesn't route models or manage budgets. TrueFoundry handles both layers. Jessica sees real product positioning clarity; Cathy questions whether the scope difference is a feature or a bloat problem, and whether Arcade's narrower focus might actually win adoption.
Transcript
Jessica So TrueFoundry just published this comparison with Arcade and it's… honestly refreshing how much they don't trash talk.
Cathy Yeah, I read it. The headline is 'Arcade is excellent at what it does, here's what it doesn't do, and here's why you might need both.' That's not a marketing post, that's a spreadsheet.
Jessica Right.
Cathy But the thing that jumped out at me is — Arcade raised sixty million dollars to be an MCP actions runtime. That is a VERY specific problem to solve. And the comparison basically says yeah, if you also need to route models or manage budgets or enforce team-level RBAC, you still need another product. So what's actually happening here?
Jessica I think that's the point though. Arcade's problem is authorization — per-action delegated OAuth, credentials never touch the agent, you broker the token at execution. That's genuinely hard and genuinely necessary if your agents are reaching systems that care about identity. But if you're already running TrueFoundry or some other gateway to route across Claude versus Grok versus whatever, you don't need Arcade for the routing part.
Cathy Okay, but then why is Arcade raising sixty million on a specialized runtime when the actual value is in the full stack?
Jessica Because the full stack is a pain to sell. You have to convince someone to rip out their existing gateway, retrain their ops team, migrate all their policies. Arcade just slots in as a—
Cathy —the actions layer. The thing that sits between the agent and the system it's trying to reach.
Jessica Exactly. And if you're already paying for a gateway, adding Arcade on top is a much easier ask than replacing the gateway entirely.
Cathy Fair. But the docs inconsistency bothers me — they claim seven thousand tools, then eight thousand, then seven thousand five hundred in the docs. You don't get to just… pick a number.
Jessica Oh, that's the Smithery acquisition. They acquired the registry in August and now own like twenty-three thousand MCP servers. So the tool count is probably real but moving fast enough that the marketing pages can't keep up.
Cathy Mm-hm.
Jessica Also, Arcade wrote the MCP authorization spec that Anthropic adopted. That's not marketing, that's standards authorship. They sit on the steering committees.
Cathy Okay, that's real. But here's what's actually interesting: the comparison says Arcade's SIEM log streaming ships today and TrueFoundry's is coming soon. So in the thing that actually matters for compliance and audit, Arcade is ahead.
Jessica Yeah. And the pricing is cleaner — usage-based, no seats. You pay per tool call, per auth event, annual bundles if you want.
Cathy But then you hit the Enterprise tier and suddenly SSO and RBAC are gated, even though the homepage says they're out of the box. That's the move where the honesty stops.
Jessica That's fair. Though the honest part is they're saying it in the comparison at all. Most vendors would just hide that.
Cathy True. So the real question is: does Arcade's narrow focus actually become a distribution advantage? Like, if your biggest problem is agent authorization and you don't want to touch your gateway, Arcade is a plug-in. TrueFoundry is a rip-and-replace.
Jessica That's the bet, right? Arcade's thesis is that enterprises already have gateways, already have governance layers, and they just need the authorization piece. TrueFoundry's thesis is that those layers are fragmented and messy and you should buy one thing that handles all of it.
Cathy Both could be right.
Jessica Exactly. And the fact that TrueFoundry just got named Frost and Sullivan's transformational innovation leader in the AI control plane category — that's enterprise validation for the full-stack play. But that doesn't kill Arcade's narrower thesis.
Cathy The thing I'd watch is adoption velocity. If Arcade's narrower scope makes it easier to integrate and justify internally, it could actually move faster despite the smaller TAM. But if enterprises end up needing both anyway, TrueFoundry wins by being the default choice.
Jessica And if the MCP ecosystem keeps growing — which it is, Smithery's now part of Arcade with twenty-three thousand servers — then owning the registry and the authorization layer together becomes a real lock-in story.
Cathy Okay, I'll give you that. Standards authorship plus registry ownership is actually a defensible position.
Jessica So we're basically saying the comparison is honest, the products are real, and the choice depends entirely on whether you're buying a specialist or a platform?
Cathy Yeah. Which is refreshing. It's not a marketing post disguised as analysis. It's two products with different scopes, both shipping, both funded, both trying to own different layers.