OpCon

You have an OpCon MCP Server that lets you interact with the OpCon REST API using the Model Context Protocol. It auto-generates MCP tools for OpCon endpoints, supports authentication, and can expose metrics for observability. You can run it locally in development or deploy it for production and connect MCP clients to automate and orchestrate OpCon tasks via a standard protocol.

How to use

Connect an MCP client to the OpCon MCP Server to call OpCon API endpoints as tools. The server can run as a local process or be started in a production environment. You will typically configure the client to invoke tools that map to OpCon REST API operations, enabling automated workflows, scheduling, and monitoring across your OpCon environment. Ensure authentication is configured so your client can securely obtain and use tokens or credentials, and enable metrics if you want visibility into tool usage and error rates.

How to install

Prerequisites you need before installation:

• Node.js 18 or higher
• Access to an OpCon API server
• OpCon API credentials (token or username/password)

Step-by-step commands to set up the server locally:

# Install dependencies
npm install

# Development mode
npm run dev

# Production mode (after building)
npm run build
node dist/index.js

Using with MCP Clients

Configure your MCP client to connect to this server. The server runs as a stdio-based MCP endpoint, meaning you start a local node process that loads the server script and exposes tools for remote invocation by the MCP client.

{
  "mcpServers": {
    "opcon": {
      "command": "node",
      "args": ["/path/to/OpyConyMcpy/dist/index.js"],
      "env": {
        "OPCON_BASE_URL": "https://your-opcon-server:9010",
        "OPCON_TOKEN": "your-token-here"
      }
    }
  }
}

Environment and tools configuration

The server is configured through environment variables. You should provide the base URL for the OpCon API and your credentials. Optional metrics can be enabled to monitor API usage and errors.

Available patterns and security

• Use HTTPS for production to protect data in transit. - Prefer token-based authentication or username/password as configured. - If TLS verification needs to be disabled for a test environment, set the appropriate flag, but re-enable it for production. - Regularly rotate credentials and monitor for suspicious activity with the included metrics.

Monitoring and metrics (Grafana)

Prometheus metrics are supported for monitoring and observability. You can enable the metrics endpoint, collect data on request counts, error rates, and tool latency, and visualize it in Grafana by wiring Prometheus to the endpoint.

Development and testing notes

You can run unit tests with the built-in test suite, linting, and formatting checks to keep code quality high during development.