MCP gateway with OAuth, IdP groups RBAC, and SIEM logging

Try this example in Tines 3B

Import now

An MCP Gateway that sits between AI clients (like Claude Code) and enterprise MCP servers, enforcing OAuth authentication, role-based access control via IdP groups, and comprehensive audit logging. The gateway filters available tools based on user group membership, proxies requests to upstream MCP servers, and sends all interactions to a SIEM. IT teams can manage tool allowlists, user agent restrictions, and access policies through an admin panel.

The problem

Enterprise tools are rapidly adding MCP server features that extend agentic AI tools like Claude Code, but IT teams face a critical security gap: most MCP implementations lack role-based access control and audit logging. Without these controls, enabling MCP features exposes sensitive corporate tools to unmonitored, unrestricted access. Teams need a governed front door that enforces identity, filters capabilities by role, and logs every interaction before they can safely unlock MCP's potential across their organization.

Solution and impact

This gateway solves the problem by acting as a security-enforced proxy between AI clients and corporate MCP servers. Users authenticate via OAuth with device trust and group-based access policies enforced by the organization's IdP. The gateway then filters which MCP tools each user can see and use based on their IdP group memberships, proxies allowed requests to upstream servers, and logs every authentication, tool call, and admin change to the company's SIEM. IT teams gain a central admin panel to allowlist tools per group, control client access, and maintain full visibility—enabling secure, compliant adoption of MCP across the enterprise.