Arcade.dev Supports EMA for Enterprise MCP Agents
Sign up<br>Dashboard<br>Book a demo
Sign up<br>Dashboard
Book a demo
Arcade.dev Supports EMA
Guru Sattanathan<br>JUNE 23, 2026<br>3 MIN READ<br>MCP
The industry just took a real step toward making enterprise AI agents easier to connect. Anthropic recently adopted Enterprise-Managed Authorization (EMA), a new MCP extension that lets identity providers grant server access centrally, so users get their approved servers at login instead of one OAuth prompt at a time.
For nearly two years, Arcade.dev has secured what AI agents actually do inside enterprise tools: authorizing every action, for every user, battle-tested in production. This adoption of EMA validates the work we’ve been doing all along, and more importantly has the potential to improve the experience of anyone already running agents in production.
If you’re interested in early access, contact us.
What’s EMA and what does it enable?
Enterprise-Managed Authorization (EMA) is a now-stable extension to the Model Context Protocol (MCP), adopted by Anthropic, Microsoft, Okta, and a growing list of MCP servers. EMA does one thing well: it lets an organization manage agent access to MCP servers centrally, through the identity provider it already trusts.
Define the policy once, and users get every server their role allows on first login. No per-app consent prompts, no personal accounts slipping into workplace systems, and one place for security to decide who connects to what.
That’s clean, centralized, and better for everyone. Employees get the tools they need from day one. Security gets control.
Arcade & EMA, stronger together
Connecting an agent and governing what it does are two different jobs. EMA handles the first: it decides, once at login, that an agent can act for a user inside an approved tool. After that, the grant never weighs in again.
That’s where Arcade comes in. Arcade is the actions runtime for enterprise AI agents. Every action runs through it, authorized for the right user, on the right resource, in the moment, with a full audit trail.
EMA grants access. Arcade keeps every action in bounds. Together, we enable agents your security team approves and your employees actually want to use.
Consider before using
EMA is still early, and adoption is limited. To use it today, two things have to line up. First, your identity provider has to support it, which right now means Okta, through its Cross-App Access (XAA) implementation.
Second, the MCP server you’re connecting to has to have adopted EMA. So far that’s a short list of first-party servers: Asana, Atlassian, Canva, Figma, Granola, Linear, and Supabase, with Slack and others adding support and most still in beta.
One more limit is worth calling out. EMA depends on each provider opening the underlying grant to third parties, and so far none have. This means any custom servers you’re building for your specific business needs won’t be able to benefit from EMA yet.
Get early access
We’re glad to see the ecosystem moving toward the model we’ve built on all along and excited to track the evolution of EMA. Early access is open now for teams building on the cutting edge. If that’s you, let us know.
Connect with confidence. Act with control.
Thank you! Thanks — you're on the early-access list. We'll be in touch shortly.
Oops! Something went wrong. Please try again.
SHARE THIS POST
Last updated on June 23, 2026
Copy link
RECENT ARTICLES
JUNE 23, 2026<br>THOUGHT LEADERSHIP<br>Enterprise-Managed Authorization Is a Foundation, Not a Ceiling: Why Connected Agents Need Per-Action Authorization<br>EMA centralizes MCP access provisioning, but it was never designed to authorize each tool call. Here's why connected agents also need per-action authorization at runtime.
JUNE 22, 2026<br>THOUGHT LEADERSHIP<br>The model never needs to see the file<br>Sending a file through an AI agent shouldn't cost a million tokens or a file picker. Here's how Arcade.dev keeps file bytes out of the model's context, and why MCP's file story needs a client-resolution mode before autonomous agents hit a wall.
JUNE 18, 2026<br>THOUGHT LEADERSHIP<br>The NSA Just Handed Enterprise Buyers a Requirements Document for MCP<br>The NSA's May 2026 Cybersecurity Information Sheet on MCP is effectively an RFP for every agentic AI program in the Fortune 500.
Get early access to Arcade, and start building now.
Sign up now<br>Docs