13 Enterprise Manager Model Context Protocol Server

Grounded in Enterprise Manager telemetry and operational metadata, the Enterprise Manager Model Context Protocol (MCP) server enables MCP-compatible AI applications and agents to securely discover and invoke supported Enterprise Manager operations through a standard protocol.

Note:

Starting with Enterprise Manager 24ai Release 1 Update 12 (24.1.0.12), the MCP server is built directly into Enterprise Manager and is available out of the box.

The MCP server enables AI agents, such as Codex, to access management context, retrieve insights, and assist with routine operational workflows through natural-language interactions. This helps teams accelerate troubleshooting, simplify administration, and build intelligent automations.

The MCP server runs in the Oracle Management Service (OMS), where it complements existing Enterprise Manager REST APIs rather than replacing them. It uses existing Enterprise Manager security, governance, and operational capabilities.

Topics:

• MCP Client Workflow
• Connecting MCP Clients to Enterprise Manager
• Supported MCP Operations
• Security and Access Control
• Current Limitations

MCP Client Workflow

MCP-compatible AI clients connect to the MCP server, discover available tools, and invoke supported Enterprise Manager operations.

A typical MCP client interaction follows these steps:

1. Connect to the MCP server.
2. Initialize the MCP session.
3. Discover the available tools.
4. Invoke the appropriate tool.
5. Receive an MCP-compliant response for the requested Enterprise Manager operation.

Connecting MCP Clients to Enterprise Manager

Connect MCP-compatible AI clients to the MCP server by using the MCP endpoint and supported HTTP transport.

Configure your MCP client to connect to the following endpoint:

https://<subdomain>.<domain>.com:<EM_CONSOLE_HTTPS_PORT>/em/api/mcp

The MCP server uses JSON-RPC 2.0 over HTTP POST with application/json content. Server-Sent Events (SSE) streams through HTTP GET requests are not supported.

The MCP server supports MCP protocol versions 2025-06-18 and 2025-11-25.

Authenticating MCP Clients

OAuth is not supported for authenticating with the MCP server. MCP clients authenticate using Basic Authentication through the Authorization header.

Supported MCP Operations

Discover and invoke supported Enterprise Manager operations by using MCP tools.

After initializing an MCP session, an MCP client can discover available tools and invoke the appropriate tool for an Enterprise Manager operation.

The MCP server provides ExecuteSql, a custom tool that runs SQL queries through the Enterprise Manager Free Query API. You can run queries against the Enterprise Manager repository or an Enterprise Manager monitored target.

The remaining MCP tools expose existing Enterprise Manager REST API operations through MCP.

Security and Access Control

Enterprise Manager security controls determine which MCP operations an authenticated user can access.

The MCP server uses the existing Enterprise Manager security model. Authentication, authorization, validation, auditing, and business rules are enforced by the underlying Enterprise Manager REST APIs.

An MCP client can perform only operations for which the authenticated Enterprise Manager user is authorized.

Current Limitations

The MCP server does not support certain protocol capabilities in this release.

The MCP server currently has the following limitations:

• SSE transport
• OAuth authentication
• Resource subscriptions or unsubscriptions
• Completions, logging, roots, sampling, elicitation, or tasks
• Cline compatibility

  Due to a compatibility issue, the MCP server does not work in the latest versions of Cline.

Note:

Although clients can list prompts, resources, and resource templates, the MCP server currently exposes none of them; the corresponding list requests return zero items.