How the HighCohesion MCP Server works
What the HighCohesion MCP Server for AI assistants can read, what it cannot do, and how access is controlled.
The short answer
The HighCohesion MCP Server is a secure link that lets an AI assistant read your HighCohesion data on your behalf, using your existing Control Panel login. It exposes nothing you could not already see in the Control Panel, it is read-only, and it is limited to your own organisation's data.
How it works
You authenticate with your Control Panel account, including two-factor authentication; there are no separate credentials to manage. Access is scoped to your organisation: you see exactly what your Control Panel account can see, and nothing else.
The assistant can read your streams and their sources and destinations, transformations, the systems catalogue, entities and events, issues and their occurrences (each time an issue happened), and lookup tables. It never receives credential content.
What it cannot do
Change anything. No tool can create, edit, delete or trigger anything, so you cannot break a stream by asking about it.
Dump raw payloads. Beyond stream and configuration metadata there are no raw payload dumps. Occurrence and lookup-table data can still contain real customer identifiers, so treat AI conversations that include it with the same care as any customer data.
Read user accounts. The server cannot read or list users.
What this means for you
You can revoke access at any time by disconnecting the HighCohesion MCP Server in Claude.
The assistant can tell you exactly what to ask HC for, but it cannot resend an event or change a mapping. Use How to fix and resend a failed event and Requesting a mapping change for the actions themselves.
Found a wrong answer, or want a new capability? Email support@highcohesion.com.