AI assistant connector (Claude, ChatGPT, Le Chat, Copilot, Gemini Enterprise) — docs

What it does

The Doctilla connector lets an AI assistant that supports the Model Context Protocol (MCP), such as Claude or ChatGPT, read, search, create and update your Doctilla records on your behalf. You sign in with your own Doctilla account, so the assistant works with exactly your role and permissions, in the organisation you choose.

Connector address	`https://mcp.doctilla.co.uk/mcp`
Authentication	OAuth 2.1 with PKCE; each person signs in to Doctilla
Transport	Streamable HTTP
Who can use it	Any member of an organisation with an active or trial licence

Add it to Claude

Open Doctilla in the Claude directory (or search for “Doctilla” in Claude's connectors directory). If you can't find it, open Settings → Connectors, choose Add custom connector, and enter the name Doctilla and the address https://mcp.doctilla.co.uk/mcp.
Choose Connect. A Doctilla window opens; sign in as usual.
On the consent screen, pick the organisation and whether Claude may make changes, then choose Allow.
In a conversation, turn on the Doctilla connector from the tools menu and ask away.

On Claude Team and Enterprise plans, an owner may need to add or allow the connector for the organisation first.

Add it to Claude Code

claude mcp add --transport http doctilla https://mcp.doctilla.co.uk/mcp

Then run /mcp in Claude Code and choose Authenticate next to Doctilla. Your browser opens the Doctilla sign-in and consent screen; once you allow it, you're returned to Claude Code.

Add it to ChatGPT

Where your ChatGPT plan allows custom connectors, add a connector with the address https://mcp.doctilla.co.uk/mcp and OAuth authentication, then sign in to Doctilla when prompted.

Add it to Le Chat (Mistral)

In Le Chat, open Connectors, choose Add connector, then Add a custom connector.
Enter the name Doctilla and the server https://mcp.doctilla.co.uk/mcp. Le Chat detects OAuth 2.1 by itself; leave the advanced settings alone.
Choose Add connector, sign in to Doctilla, pick the organisation and whether Le Chat may make changes, then choose Allow.
Start a chat with the Doctilla connector selected. Le Chat runs Doctilla's read-only tools freely and asks before any change.

Add it to Microsoft Copilot Studio

Open or create an agent in Copilot Studio. Your environment needs Dataverse and your account a Copilot Studio licence or trial.
In the agent's Settings → Generative AI, choose Yes for generative orchestration and save. Agents on classic orchestration never call connector tools.
Go to Tools → Add a tool → Model Context Protocol. Enter the name Doctilla, a short description and the server URL https://mcp.doctilla.co.uk/mcp. Choose OAuth 2.0, type Dynamic discovery, then Create.
Under Connection choose Create new connection, sign in to Doctilla in the window that opens and choose Allow. Then Add and configure.
Ask the agent “What needs my attention in Doctilla?” in the test pane.

Add it to Microsoft 365 Copilot

For IT teams building a declarative agent for Microsoft 365 Copilot. You need Visual Studio Code with Microsoft 365 Agents Toolkit, and a tenant where custom app upload and Copilot are enabled.

In Agents Toolkit, create a new agent: Declarative agent, then Add an action → Start with an MCP server.
Enter the server URL https://mcp.doctilla.co.uk/mcp and choose the Doctilla tools to include.
For authentication choose OAuth (with dynamic registration). No client ID or secret is needed; Microsoft registers itself with Doctilla.
Provision the agent. The first time someone uses it, Copilot asks them to sign in to Doctilla, pick the organisation and whether the agent may make changes.

Add it to Gemini Enterprise

For Google Cloud administrators. Gemini Enterprise doesn't register itself, so Doctilla publishes a client ID for it.

Allow custom MCP connectors for the project that hosts your Gemini Enterprise app (organisation policy disableCustomMcpServerConnector set to off).
In your app, open Connected data stores → Create data store → Custom MCP server and choose OAuth 2.0.

Fill in:

MCP server URL	`https://mcp.doctilla.co.uk/mcp`
Authorization URL	`https://app.doctilla.co.uk/oauth/authorize`
Token URL	`https://mcp.doctilla.co.uk/oauth/token`
Client ID	`doctilla-gemini-enterprise`
Client secret	Leave blank
PKCE	On
Scopes	`doctilla:read doctilla:write` (or just `doctilla:read`)

Choose Verify Auth and sign in to Doctilla, then Continue and Create.
On the connector's Actions tab, enable the Doctilla tools. Each person who uses them signs in to Doctilla with their own account.

MCP Registry

Doctilla is listed in the official MCP Registry as uk.co.doctilla/doctilla, so tools that read the registry can find it by name.

Read only (doctilla:read) lets the assistant search and read records you can see.
Allow changes (doctilla:write) also lets it create and update records. Viewers can only grant read access, and if your role later becomes viewer, write access stops at once.
Every call runs as you, under the same database permissions as the app. If you leave the organisation, or its licence lapses, the connection stops working.
Access tokens last an hour and refresh automatically for up to 30 days of inactivity.

Tools

Tool	Does	Type
`doctilla_overview`	Headline counts: open and overdue CARs and actions, open NCRs, overdue and upcoming audits, open risks, documents due for review, pending effectiveness checks, proposed mappings	Read
`doctilla_search`	Find records by text across record types	Read
`doctilla_describe`	A record type's fields, filters, writable fields, and the values only a person may set	Read
`doctilla_list`	List records of one type with filters and pagination	Read
`doctilla_get`	One record, optionally with its traceability links	Read
`doctilla_create`	Create a record	Write
`doctilla_update`	Change fields on a record	Write
`doctilla_link`	Link two records for traceability	Write

Field names, types and allowed values for each record type are in the API reference, and the assistant can ask doctilla_describe for them at any time.

What it can't do

Delete anything. There is no delete tool.
Make decisions Doctilla reserves for people: close a CAR, complete an 8D step, record an effectiveness result, set a supplier's status or an evaluation outcome, set an objective's status, approve a document, management review minutes, a concession or a product change, conclude a technical review, accept a mapping, or mark a claim as supported. The assistant is told to ask you to do these in Doctilla.
Change a locked or finalised record.
See anything you can't see in the app.

Mappings to a standard created through the connector are marked as AI-created and start as proposals for a person to accept.

Things to ask

“What needs my attention in Doctilla this week?”
“Find every open NCR about moisture in the intumescent compound and summarise what they have in common.”
“Raise an NCR for 40 cartons printed without the fire rating, from today's goods-in check, and link it to CAR-0002.”
“Draft D2 of CAR-0005 from these notes: …”
“Which suppliers have certificates expiring in the next two months?”
“List the claims on FireSeal 20 and the evidence behind each.”

Disconnecting

In Doctilla, open Settings → Integrations → Connected appsto see every assistant you've connected and disconnect any of them. An owner or admin sees and can disconnect every connection in the organisation. You can also remove the connector in the assistant's own settings. Leaving an organisation disconnects everything you linked in it.

Using an API key instead

For automations where nobody signs in, an owner or admin can create an API key in Settings → API keys and send it as Authorization: Bearer dq_live_…. Everyone using that key acts as the person who created it, so prefer personal sign-in for people, and a read-only key unless changes are needed. Never put a key in a URL.

Troubleshooting

What you see	What to do
The sign-in window says the organisation can't be used	Its licence may have lapsed, or you may not be a member. Check with an owner.
Changes are refused but reading works	You allowed read-only access, or your role is viewer. Reconnect and allow changes, or ask an owner to change your role.
“A person must set this in Doctilla”	That field is a decision Doctilla reserves for people. Open the record in Doctilla to do it.
The record is locked	It has been finalised, for example a locked audit or approved minutes. Changes become amendments or new records.
The connection stopped working	Reconnect from the assistant's settings. Connections end if unused for 30 days, if you leave the organisation, or if someone disconnects them.

Still stuck? Email [email protected].

Data and privacy

Doctilla stores only hashes of the connection's tokens, and its logs record the method, route, status and timing of each request, never record contents. Records the assistant fetches are sent to the assistant's provider, whose privacy policy applies to them. See our privacy policy.

Claude and ChatGPT connector