Context layer for employees
Set up Agent Handler for employee use - SSO, Group-based tool access, full audit, managed through the IdP you already operate.
Set up Agent Handler for employee use - SSO, Group-based tool access, full audit, managed through the IdP you already operate.
Agent Handler is the access-control layer for employee AI. Your employees plug an MCP URL into the AI surface they already use - ChatGPT, Claude, Cursor, Claude Code, any MCP-compatible client - or into agents they build themselves for their own work. You decide which enterprise tools they can reach from inside it, scoped to their role and governed through your existing identity stack.
There’s a clean split: your IdP owns users and Group memberships; Agent Handler owns the mapping from Groups to tool access. SCIM syncs users and Groups in automatically - no separate user database for IT to maintain - and you assign Tool Packs to those Groups inside Agent Handler. Employees sign in once through SSO; their AI assistant inherits a token scoped to the tools their Group has been granted. Every call is captured in the Audit Trail.
If you’re embedding an agent inside a product where users come in through your UI - whether for customers or employees on an internal tool - see Building an agent instead. For a side-by-side, see Use cases.
By the end of this guide:
You manage the policy in Agent Handler. Employees only see their AI assistant connected to the right tools.
Technical surface: an OAuth-authenticated MCP server at https://ah-api.merge.dev/mcp. Employees configure their AI client to use the URL; the server authenticates them through your IdP and issues a scoped token.
Open Settings → SCIM in the Agent Handler dashboard. Configure default access for newly-provisioned employees and generate a SCIM token. You’ll paste this token into your IdP in the next step.
In your IdP (Okta, Azure AD, Google Workspace, others), assign employees to the Agent Handler SCIM application. As they’re provisioned, Agent Handler creates the records it needs internally - you don’t manage these directly.
Push the Groups you’ll use for tool access - your existing “Sales”, “Engineering”, “Finance” Groups, or whatever maps to roles in your org. These sync into Agent Handler and become the unit of authorization.
Back in Agent Handler under SCIM → Group mappings, configure each Group’s access:
Settings apply to every employee in the Group. Members of multiple Groups get the union of their tool sets.
The first time an employee connects their AI client, they sign in through your IdP and approve the tools their Group has been granted. After that, their AI assistant calls those tools without further interaction.
If they ask the assistant to do something outside their tool set - say, an Engineering employee asks for billing data - the call returns an error and a violation entry in the Audit Trail. From the dashboard, you can review the request and approve, decline, or extend the employee’s access.
403 mid-conversation on a tool. The AI client should auto-retry through OAuth to grant the missing scope. If the missing tool is outside the employee’s allowed set, an admin gets a request notification.For more, see Troubleshooting.
Head to ah.merge.dev to start the SCIM setup, or read Tool Packs for how to shape what each Group can call.