How to Configure MCP Client: Claude

How to Configure MCP Client: Claude

How to Configure MCP Clients like Claude Desktop using the MCP Bridge

Claude Desktop is a powerful AI client that can connect and communicate with the OAS server, which can use either the MCP Bridge configuration or the HTTP channel, however using the HTTP channel would require that you expose your OAS Server on the internet with a URL. These instructions cover using the MCP Bridge application which will still work with an OAS Server behind your corporate network.

Warning

While the following method below uses the MCP Bridge application to keep your OAS Server off a public network, using Claude in any form will send your data up to the Claude cloud infrastructure for processing. How this data is used is based on your Claude account. With an Enterprise Claude account, you can prevent Anthropic from retaining and using your data for training.

  1. Install the Claude Desktop application on your local machine. This can be found at Claude Desktop. You will need to create an account with Claude.ai before you can use the desktop application.

  2. Run the desktop app and from the user menu (lower left), select Developer and then Edit Config, which will point to the claude_desktop_config.json file.

Claude Desktop interface

Claude Desktop Developer Settings

  1. Edit the config file, locating the mcpServers section, adding the following entry:
"oas-engine": {
    "command": "C:\\Program Files\\Open Automation Software\\OAS\\MCP\\oas-mcp-bridge.exe",
    "args": [
    "--host", "localhost",
    "--port", "58730",
    "--apikey", "<YOUR_API_KEY>"
    ]
}
  • Replace localhost with the IP address of your OAS server. If you are running the OAS Server on the same machine as your client, you can keep this as localhost.
  • Change the port number to math the port configured above. If this was not changed, keep the default.
  • Replace <YOUR_API_KEY> with the MCP API Key assigned to the user you created above.
  1. Quit and restart the Claude Desktop application after saving the config file. Make sure you quit entirely. On Windows, this would require opening the system tray and quitting Claude within there as well. Unfortunately, this is required for the configuration change to take effect. After reopening the application, go back to the Developer settings and you should see something like the following, showing the OAS MCP server connection.

Claude Desktop Developer Settings Updated

  1. Return to the Claude chat and test the interface by performing some queries. A good simple test would be:

Get the values, timestamps, and data quality for the Sine, Ramp, and Random tags. Put this data in a table.

You should see something like this as a result:

Claude Desktop Results

Ready to get started?

Talk to an OAS engineer about your specific configuration and see it in action