Connect through MCP

MCP lets your AI assistant use the agents and data in your Omnimatch installation.

Connection

Add a remote MCP server in your client with Streamable HTTP transport:

http://localhost:8787/mcp

Replace the address with your installation’s HTTPS address when connecting from another device. This is the existing /mcp endpoint, not a separate service.

Authentication

Clients supporting MCP OAuth open your installation’s sign-in flow. For clients using an API key, set:

Authorization: Bearer YOUR_API_KEY

Use a key issued by your installation, not your product key.

Available tools

Your client discovers tools from the server through tools/list. Access follows the signed-in user’s permissions and your installation’s enabled capabilities.

Microsoft Teams through Copilot Studio

Your administrator can add this MCP endpoint to a Copilot Studio agent, then publish that agent to Microsoft Teams. Microsoft’s cloud must be able to reach your installation, so IT needs to configure network access and each user’s permissions.

Test the integration in your environment before rollout. Data returned to Copilot is processed by Microsoft’s cloud.

Connect MCP in Copilot Studio · Publish the agent to Teams

Inspect the connection

The official MCP Inspector can connect to this endpoint to list and test tools. It is a developer tool, not required for normal use.