# content
MCP makes it easy for AI models to reach the data and tools you work with every day. Deploy this across a company of any size and two tensions surface immediately: every employee has to connect MCP clients like Claude to each tool manually, one OAuth screen at a time — and somewhere, an IT admin is wondering how many of those connections there are, who authorized them, and whether they have any say in it at all.

Enterprise Managed Auth (EMA) — built on the IETF Cross-App Access (XAA) spec — fixes this by inserting the enterprise identity provider into the middle of every MCP connection. In this session, Aaron Parecki walks through how EMA works end-to-end: from an IT admin setting up Claude.ai in an IdP and configuring which enterprise apps it can access, to an employee opening Claude in their browser and finding everything already connected — zero consent screens, zero IT tickets, full audit log. If you're building an MCP server that you want enterprise customers to actually use, EMA is the integration path that makes you IT-admin-friendly on day one.

# name
Enterprise Managed Auth: Making Your MCP Server Enterprise-Ready