Okta
Okta offers an MCP Bridge professional service for AI coding-assistant tool access. Review its self-hosted proxy, audit path and SOW scope.
Quick reference
Service details
Service information · see individual claim labels below.
- Service coverage
- Not stated
- Industries
- Cybersecurity, IT Operations
- Delivery mode
- AI Implementation
- Pricing model
- Not stated
- Headquarters
- Not stated
- Languages
- Not stated in the sources reviewed
No fact on this record has independent corroboration yet. Provider statements remain labeled, and gaps stay visible.
01 · At a glance
What this provider does
Okta describes its MCP Bridge as a Professional Services offering that needs a statement of work. The self-hosted proxy places an identity layer between AI coding assistants and the Model Context Protocol tools they call, with authentication and audit logging described by Okta. This narrow implementation service is distinct from an Okta for AI Agents platform subscription; the exact installation, controls and handover must be defined in the SOW.
A narrowly scoped service beside the platform
Okta’s AI security pages mainly present identity products for agents. One separate offer is explicitly described as Professional Services: MCP Bridge. Okta says this bridge is available through a statement of work, so this record concerns a scoped implementation engagement rather than implying that every Okta product subscription includes a consulting team.
The service addresses AI coding assistants that use Model Context Protocol tools to reach internal systems. Okta’s example tools include developer and collaboration systems and internal APIs. The public page describes the access problem as unmanaged credentials and missing audit trails; it does not establish that any particular customer has this problem or that the bridge supports every tool out of the box.
Sources: Okta — Identity governance for every agent handoff, action and tool ↗ (provider) · Okta Secures AI ↗ (provider)
How the bridge is described
Okta describes a self-hosted, identity-aware proxy between an assistant and the MCP tools it calls. According to the provider, tool calls pass through the bridge, the agent authenticates through an identity provider, and actions enter an audit log. Okta says the assistants and tools need not be rewritten for this pattern.
The customer controls deployment, configuration and data in its own environment, according to Okta. That boundary is important when reviewing data handling and integration duties. The announcement confirms the Professional Services positioning; it should not be read as proof of an independently tested security outcome or as a promise of a particular access policy.
Sources: Okta — Identity governance for every agent handoff, action and tool ↗ (provider) · Okta newsroom — AI agent identity and MCP Bridge ↗ (provider)
What to define in the statement of work
Okta’s general Professional Services terms define implementation and configuration work through a statement of work, separately from the subscription service. The bridge article gives the mechanism and availability but does not publish a universal installation plan, test protocol, handover package or support period.
A buyer should name the assistants, MCP servers and identity provider, then agree on authentication flow, authorization policy, log destination, failure handling and ownership after launch. These are scope questions, not claimed standard deliverables. Public sources reviewed here do not establish the project price, duration, coverage countries or which product licenses may be required.
Sources: Okta — Identity governance for every agent handoff, action and tool ↗ (provider) · Okta Professional Services Agreement ↗ (provider)
02 · Claims and sources
Every fact, with its label.
A source link shows where a statement came from. It does not by itself confirm delivery.
Other
4 factsScoped professional service
Provider-reportedOkta names MCP Bridge as a Professional Services offering that requires a statement of work, distinct from its broader AI agent identity platform.
Identity-aware proxy
Provider-reportedDescribes a self-hosted proxy between AI coding assistants and MCP tools, with the customer controlling deployment, configuration and data.
Authentication and audit path
Provider-reportedOkta says each tool call passes through the bridge, agents authenticate via an identity provider, and actions are logged without rewriting the assistant or tool.
Contract boundary
Provider-reportedThe public terms say Okta Professional Services cover implementation and configuration described in a SOW; the MCP Bridge page does not publish standard deployment or support deliverables.
No facts with this status on this record. How corroboration works →
04 · Sources & updates
Where this record comes from.
Owner claim status concerns profile control. It does not verify service delivery. Submitted changes are reviewed before publication.
- www.okta.com/blog/product-innovation/identity-governance-for-ai-agents/ ↗Okta — Identity governance for every agent handoff, action and toolProvider source · Cited for 4 facts · Checked Oct 12, 2026 · Published Jun 17, 2026
- www.okta.com/legal/professional-services-agreement/ ↗Okta Professional Services AgreementProvider source · Cited for 2 facts · Checked Oct 12, 2026 · Published Jun 4, 2025
- www.okta.com/newsroom/articles/okta-identity-security-posture-management-integrates-with-anthropics-new-compliance-api/ ↗Okta newsroom — AI agent identity and MCP BridgeProvider source · Cited for 1 facts · Checked Oct 12, 2026
- www.okta.com/solutions/secure-ai/ ↗Okta Secures AIProvider source · Cited for 0 facts · Checked Oct 12, 2026
Something to correct?
Okta can claim this profile or send sources. Anyone can suggest a factual correction. Submissions are reviewed before publishing.