The OpenEdge Command Center MCP Server lets an MCP-compatible AI client retrieve authorized information from OpenEdge Command Center by using read-only tools and prompts.

The MCP Server runs as a separate process and communicates with MCP clients over HTTPS through the /mcp endpoint. The MCP server requests information from the OpenEdge Command Center Server REST API and returns the results to the AI client.

Each client connection is authenticated separately. The authentication method depends on the mode configured for OpenEdge Command Center Server:

  • Local authentication: In this authentication mode, you create a personal access token in OpenEdge Command Center and use it to connect the MCP client.
  • IdP authentication: In this, you configure an external identity provider for OpenEdge Command Center. Then use the credential issued by the configured identity provider to connect the MCP client. For more information, see Learn about external identity provider (IdP) authentication.

OpenEdge Command Center Server remains responsible for authorization. The MCP server does not provide additional permissions. The tools and prompts return only the information that the authenticated user is authorized to access.