The OpenEdge Command Center MCP server is installed and started automatically with the OpenEdge Command Center server. It runs as an independent operating-system process and accepts connections from MCP clients. Starting or stopping the MCP Server does not start or stop the OpenEdge Command Center Server.

Start the MCP Server

When you start the OpenEdge Command Center server, OpenEdge Command Center MCP server also starts automatically. If it is not running, or if you stopped it, you can start it by running:

  • oeccmcpserver.bat start (on Windows)
  • oeccmcpserver start (on Linux)

The MCP Server listens on the port specified by port under the oecc_mcp section in mcpConfig.json. The default port is 8002.

Stop the MCP Server

Similarly, to stop a running MCP server, you can run the following commands:

  • oeccmcpserver.bat stop (on Windows)
  • oeccmcpserver stop (on Linux)

Stopping the MCP server prevents MCP clients from connecting to it. It does not stop the OpenEdge Command Center server.

Check the MCP Server status

To check the status of the MCP server, you can run the following commands:

  • oeccmcpserver.bat status (on Windows)
  • oeccmcpserver status (on Linux)

Use the status command after starting or stopping the MCP Server to confirm whether the process is running.

Review MCP Server logs

The MCP server writes its log files to the same logs directory as the other OpenEdge Command Center Server logs. Review the logs if the MCP server does not start, stops unexpectedly, or does not accept client connections.