Use this procedure when OpenEdge Command Center uses OIDC authentication.

Prerequisites

Before configuring the MCP client, ensure that:

  • The OpenEdge Command Center Server is configured to use OIDC authentication.
  • An identity provider is configured for OpenEdge Command Center.
  • A client ID is configured for OpenEdge Command Center.
  • The MCP Server is running and available over HTTPS.
  • The MCP client can trust the MCP Server certificate.

For information about configuring the identity provider, see Switch from local authentication to IdP authentication.

Configure the MCP client

Open the MCP client configuration file, such as mcp.json, and add the following server configuration. The MCP Server listens on port 8002 by default. If the port was changed, use the value specified by port under the oecc_mcp section in mcpConfig.json.

{
  "servers": {
    "oecc_mcp": {
      "type": "http",
      "url": "https://<mcp-server-host>:<mcp-server-port>/mcp",
      "oauth": {
        "clientId": "<Client ID>"
      }
    }
  }
}

Replace <mcp-server-host> with the MCP Server host name or IP address, <mcp-server-port> with the configured port, and <Client ID> with the client ID configured for OpenEdge Command Center.

Save the mcp.json file.

Do not add a PAT to this configuration when OIDC authentication is active.

Connect and verify the client

  1. Start or connect to the server entry configured in mcp.json.
  2. Complete the identity-provider authentication required by the MCP client.
  3. Wait for the MCP client to report that the MCP Server is connected.
  4. Run the following read-only request:
    List the OpenEdge Command Center databases that I am authorized to view.

OpenEdge Command Center determines which databases the authenticated user is authorized to view. The MCP Server does not provide additional permissions.