Use these checks when an MCP client cannot connect to the OpenEdge Command Center MCP Server or a tool request fails.

Issue Resolution
The MCP Server does not start
  • Check the MCP Server status. On Windows, run oeccmcpserver.bat status. On Linux, run oeccmcpserver status.
  • Review the MCP Server messages in the same logs directory used by the other OpenEdge Command Center Server logs. Check for invalid configuration settings, missing certificate files, private-key errors, or other startup errors.
  • If the MCP Server is not running, start it with oeccmcpserver.bat start on Windows or oeccmcpserver start on Linux. Check its status again.
The MCP client cannot reach the MCP Server
  • Confirm that the client can reach the MCP Server host and that the port specified by oecc_mcp.port is available. The default port is 8002.
  • Use the configured host and port with the /mcp path in the client endpoint:

    https://<mcp-server-host>:<configured-port>/mcp

  • Confirm that the host name or IP address used in the MCP client endpoint is included in allowedHosts under oecc_mcp in mcpConfig.json.
  • If you change oecc_mcp.port or allowedHosts, restart the MCP Server. If you change the port, update the endpoint in the MCP client configuration. Check that network and firewall rules allow the connection.
The MCP client cannot establish a TLS connection
  • Confirm that the MCP client trusts the certificate presented by the MCP Server. Check the certificate and private-key paths under oecc_mcp in the MCP Server configuration. If the certificate or key has been replaced, confirm that the configuration points to the replacement files and restart the MCP Server.
  • For remote connections, confirm that the certificate is valid for the host name used in the client endpoint. Keep certificate verification enabled.
The OpenEdge Command Center Server is unreachable
  • Confirm that the OpenEdge Command Center Server is running and that the MCP Server host can reach it. Check the oecc.host and oecc.port settings in the MCP Server configuration. The default OpenEdge Command Center Server port is 8000.
  • If the logs indicate an upstream TLS failure, check the root and intermediate certificates configured under oecc. The oecc.nohostverify setting applies to the MCP Server’s connection to the OpenEdge Command Center Server; it does not control whether an MCP client trusts the MCP Server certificate. Keep host-name verification enabled in production.
Authentication fails

Use the client configuration that matches the authentication mode active on the OpenEdge Command Center Server:

  • Local authentication: Confirm that the personal access token (PAT) in the client configuration is valid and has not expired or been revoked.
  • OpenID Connect (OIDC) authentication: Confirm that the client ID is configured correctly and that the required identity-provider authentication completes.

Do not use a PAT when OIDC authentication is active.
Authorization fails OpenEdge Command Center Server determines what the authenticated user can access. Confirm that the user has permission to view the information requested by the tool. In local mode, check the PAT owner’s roles and permissions. In OIDC mode, check the roles provided through the configured identity provider.
A tool request fails Review the error shown by the MCP client and the corresponding MCP Server log messages. Depending on the error, check the tool inputs, server availability, certificate trust, active authentication mode, and user permissions. Correct the identified issue and run the request again.