# \[Beta\] Connect your AI agent to Auth0 via MCP — Looking for testers

**URL:** <https://community.auth0.com/t/beta-connect-your-ai-agent-to-auth0-via-mcp-looking-for-testers/199388>\
**Category:** Blog Discussions\
**Tags:** ai-agents, auth0-mcp-server, ai, mcp\
**Created:** [April 28, 2026, 2:38am UTC](https://community.auth0.com/t/beta-connect-your-ai-agent-to-auth0-via-mcp-looking-for-testers/199388 "2026-04-28T02:38:05Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![Bola](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/bola/32/73314_2.png) [@Bola](https://community.auth0.com/u/Bola)\
**Post date:** [April 28, 2026, 2:38am UTC](https://community.auth0.com/t/beta-connect-your-ai-agent-to-auth0-via-mcp-looking-for-testers/199388/1 "2026-04-28T02:38:05Z")

</div>

Hey community,  
We’re running a closed beta for Auth0 Hosted MCP Server — a way to connect your AI development environment (Claude Code, Cursor, Codex) directly to your Auth0 tenant.

Once connected, you can ask your agent to:

- Pull logs and investigate auth failures
- Create and configure applications
- Deploy Actions
- Compare settings across environments

All without leaving your IDE.

Who we’re looking for:

- You’re actively using Claude Code, Cursor, or a similar AI-assisted IDE
- You manage Auth0 tenants as part of your work
- You’re comfortable with early-stage software and willing to share honest feedback

To apply: Drop a reply or DM me. We’ll get you set up with a dedicated tenant and a setup guide.

---

<div class="post-metadata">

**Author:** ![Emily12421](https://sea1.discourse-cdn.com/auth0/user_avatar/community.auth0.com/emily12421/32/72231_2.png) [@Emily12421](https://community.auth0.com/u/Emily12421)\
**Post date:** [May 25, 2026, 5:53pm UTC](https://community.auth0.com/t/beta-connect-your-ai-agent-to-auth0-via-mcp-looking-for-testers/199388/2 "2026-05-25T17:53:14Z")

</div>

This is interesting. We run multiple agents that connect to different services via MCP and the auth layer has been one of the harder parts to get right, especially when different agents in the same workflow need different permission scopes.

One question: does the hosted MCP server support scoping access per agent within the same tenant? For example, one agent that can only read logs and another that can deploy Actions, both connecting to the same Auth0 tenant but with different authorization levels.

We have been using Auth0 for the identity side and a few external tools for the coordination between agents, including [n8n](https://n8n.io/) for routing and [teamoffsite.ai](https://www.teamoffsite.ai/) for the shared context and approval flow. The identity and coordination layers are separate concerns but they keep intersecting when agents need different permissions at different steps of the same workflow.

Happy to test the beta if you are still looking for participants running multi-agent MCP setups.
