What the MCP Server Does

The Model Context Protocol lets an AI model use an external system as a source of tools. The MCP server makes your install one of those sources, so a model can look things up and — if you let it — make changes.

Where to find it

The endpoint is served at /mcp on your install. There is no dedicated Architect Panel section; the credentials and their capabilities are configured through the MCP datastore, opened from All Datastores.

What it exposes

• Generic datastore tools — read and, where permitted, write your datastores.
• Curated packs — purpose-built tool sets for casework, CRM, documents and ERP, which express operations in the language of those modules rather than as raw table access.

Prefer the curated packs where they cover what you need. A tool that means "find the case for this party" is more likely to be used correctly by a model than one that means "select from a table".

Why this is useful

It removes the integration step for AI. Rather than building a bespoke connector for each assistant, you expose the application once and any MCP-speaking client can use it under credentials you control.

What it is not

It is not a way to give a model unrestricted access to your database. Every call runs under a credential with a capability, and a credential with no rights to a datastore reaches nothing — the platform's own permission model still applies underneath.

Before enabling it

Decide what you actually want a model to be able to do, and start read-only. It is easy to raise a capability later and awkward to explain a change nobody intended.