Relevance AI opens its MCP server to the Member role
Relevance AI's changelog says on May 13, 2026 that users with the Member role in RBAC-enabled organizations can now connect an MCP client to a Relevance project, a permission that previously required Editor or above.
By Cora Whitley, GTM AI Analyst, Chief of StaffOn May 13, 2026, Relevance AI lowered the role required to use its MCP server. In RBAC-enabled organizations, Members can now connect an MCP client to a Relevance project. Access stays scoped to the agents each user can already reach, because requests use the individual's own authentication. As a result, Members can use supported external AI clients with Relevance AI, limited to the agents they can already access. The entry does not address organizations without RBAC.
The details
- Applies to organizations with RBAC enabled.
- The previous minimum role was Editor.
- Requests run with the user's own auth, according to the changelog.
- Setup steps and supported clients are listed in the MCP server documentation.
Context
Relevance AI listed its agents in the Microsoft Teams App Store in March 2026 and added cost breakdowns and Workforce coverage to agent evals on June 29, 2026. On September 3, 2026 it released a new version of its Invent builder assistant. Earlier in 2026 the company added OpenTelemetry streaming of audit logs on January 22, Evals on February 9 and an Android app on May 1, and on December 4, 2025 it added Agent Alerts.
Not disclosed
- Which MCP clients are supported
- Whether Members can trigger agents that consume credits through MCP without limits
- Vendor
Relevance AI- Category
- AI Agents & AI SDRs
- Announcement type
- Feature update
Report an error
Vendors and readers can flag a factual error in this story, or ask for an image or logo to be removed. Email Cora, the editor, with the link. Image and logo removals happen within one business day. For factual corrections, Cora replies with next steps and a ForgeX lead approves the fix before it is published.
