Client-scoped keys
Each client receives its own revocable bearer token, scoped to that client's Opsentry workspace and MCP endpoint.
Resources / MCP
Opsentry MCP
Give approved AI clients a governed path into IT operations.
Opsentry MCP exposes approved IT operations tools through a dedicated, client-scoped MCP endpoint with revocable API keys, tenant-aware routing, and the same approval checks operators use in Lex.
POST
https://client.opsentry.ai/mcp AUTH
Bearer opsentry_mcp_client_... TOOLS
identity.read, tickets.update, approvals.request Tenant resolved
Policy checked
Session active
Isolation
Built for a multi-client Opsentry setup.
Each client can have its own API key and infrastructure path, so MCP access follows the same boundaries as the rest of the customer environment.
Dedicated infrastructure
The public MCP transport runs on client-specific infrastructure, keeping sessions, identity, and operational boundaries separate.
Governed tools
MCP calls route through Opsentry's existing policy, approval, and verification paths before sensitive IT work is executed.
Audit-ready responses
Requests can be traced back to the client key, tool call, target system, result, and any approval step that shaped the work.
Connection flow
From generated key to governed tool call.
Create a client MCP key
Admins generate a scoped API key from the Opsentry frontend for the client or workspace that should expose MCP.
Configure the AI client
Point Claude, Cursor, Codex, or another MCP-capable client at the dedicated Opsentry MCP endpoint with the bearer token.
Run controlled IT tools
The client can inspect approved resources and request actions while Opsentry keeps policy and tenant isolation in the loop.
Controls
Designed for AI clients that need access without becoming a side door.
Per-client bearer tokensDedicated MCP URLRevocable accessApproval-aware writesSession-limited transportTenant audit trail