How to Configure MCP for LLM Integration

What is MCP?

The Model Context Protocol (MCP) is an open standard that lets AI models securely connect to external tools, data sources, and services through a common interface. Instead of requiring custom integrations for every application, MCP provides a standardized way for AI clients to discover available capabilities, exchange context, and invoke actions, making it easier to build interoperable AI systems.

The OAS MCP service exposes common, read-only operations for analyzing live and historical data within an OAS server. The AI client can load data and synthesize it into just-in-time insights on your installation. Current MCP tools include:

• Browsing and enumerating Tags
• Reading live Tag properties
• Reading live Tag values
• Reading live Alam data
• Reading live Trend data
• Reading current system status

1 - Configure MCP Options

The MCP service uses two different ports in order to support different clients connecting to the OAS server. This allows a wide variety of clients to access the MCP tools, such as Claude Desktop, AnythingLLM, and more.

Within the OAS Configuration application, navigate to Configure -> Options, select the Networking tab, and locate the REST API and MCP TCP Port fields.

HTTP Streaming

The HTTP endpoint for MCP uses the same port as the OAS REST API (default 58725) and can be configured to any available port on your server. This connection method allows for a direct connection between the client and server.

TCP

The MCP TCP Port is separately configured if you are using the OAS MCP bridge application, which utilizes stdio for interfacing with your client, and TCP to communicate directly with your OAS server installation.

2 - Configure MCP Security

Access to OAS data is predicated on a security credential, along with explicit access to MCP tools. Configuration of Security Groups and Users is performed within the OAS Configuration Application.

1. Create a Security Group for your MCP clients by selecting Configure -> Security, fill in the Group Name with something like "MCP Clients" and then click Add Group in the left column.

2. By default, "Enable All Features" is selected on the Security Group which also enables all MCP tools. If you would like to restrict access to any tools or disable MCP access entirely from a Security Group, uncheck "Enable All Features", navigate to the MCP tab, and enable/disable tools for the group.

3. Create a User for your MCP clients by selecting Configure -> Users, fill in the User Name field with something like "MCPUser", set a Password, select the newly created "MCP Clients" for the Security Group, and click Add User.

4. After the user is created, check the Show MCP API Key to display the unique key for this user and copy the text. This will be the key used within the connection configuration for your MCP client.

3 - Next Steps: Configure MCP Client

There are two options for communications between your MCP client and the OAS MCP server, and these depend entirely on the tool you choose. The OAS Server supports both communications channels:

• MCP Bridge: using a thin bridge application that uses stdio for input and output, then speaks TCP directly to the OAS Server (e.g. Claude Desktop)

Learn how to configure a client using the MCP Bridge: Claude Desktop

• HTTP: using the streaming HTTP protocol, your MCP client can connect directly to the OAS Server (e.g. AnythingLLM). These are typically self-contained clients with self-hosted LLMs

Learn how to configure a client using HTTP: AnythingLLM