Paris 12:05
New York 06:05
London 11:05
Blog

Dotfile MCP: use Dotfile from the AI tools your team already uses

Vasco Alexandre

Vasco Alexandre

October 6, 2026

Dotfile MCP: use Dotfile from the AI tools your team already uses

Most compliance teams now keep an AI tool open all day. They draft in it, summarise in it, think out loud in it. And every time the question touches a case, they leave it: open the console, find the case, read the checks, copy what matters, paste it back. The AI tool knows everything except the thing the team actually works on.

The Dotfile MCP connector is now live. It brings Dotfile into the AI tool you already use: Claude, ChatGPT, Cursor, Claude Code, or any AI tool that supports remote MCP servers. You ask in plain language, and the AI tool reads and acts on your cases, checks and portfolio for you.

What you can ask it

MCP (Model Context Protocol) is the open standard AI tools use to connect to other software. Through it, your AI tool gets the same actions as Autonomy, the agent inside Dotfile, within your permissions. In practice, that means requests like these.

Analytics questions. A count, a trend or a breakdown, answered with the numbers rather than an export.

  • "How many KYB cases are waiting for review in our main workspace, broken down by assignee?"

AI review and AML triage. Start an AI review on checks waiting for review (AML, document, ID document and identity verification checks), one at a time or across a whole selection, then read the decisions and the reasoning.

  • "Run an AI review on every AML check that needs review, then summarise the decisions and list the ones it rejected."

Onboarding from a company name. Search the registries, open a KYB case from the company you pick, apply a template, launch the checks, and email the business contact a link to your Client Portal.

  • "Open a KYB case for Acme Logistics SAS in France, apply our standard KYB template and send the business contact the Client Portal link."

Investigating a case. The AI tool reads the timeline, the checks, the controls, the notes and the emails, and tells you what matters. It can then act on what it found: add a note, assign the case, tag it, set the risk level, approve, reject or close it.

  • "Summarise the case for Acme Logistics: what is still missing, which checks failed, and what changed last week."

Company data and registry documents. Refresh a company's registry data and see what changed since the last purchase, list the official documents available, order them, and read their content once they arrive. These actions are billed exactly as they are in the console.

  • "Refresh the registry data for this company and tell me what changed since our last purchase."

Reading your configuration. Templates, controls, custom properties, Client Portals, risk engine, AML screening profiles and workspace settings. The AI tool can explain how your workspace is set up and why a case was routed the way it was. Changing that configuration stays in the console.

The AI tool also brings what Dotfile cannot: your other tools. A question that joins your compliance data with a spreadsheet, a ticket or an email thread is now one request instead of three windows.

It acts as you, and only as you

Handing an AI tool the keys to a compliance platform is a reasonable thing to be nervous about. So the connector holds no keys of its own.

  • Same permissions. Every call runs with your user, your role and your custom role permissions. If you cannot approve a case in the console, your AI tool cannot approve it either.
  • Checked on every call. Membership, MFA, SSO and IP restrictions are verified again for each request, not once at connection.
  • Nothing to leak. You sign in with your Dotfile account in the browser. There is no API key, token or client secret to create, store or rotate.
  • Revocable. Revoke the connection from your account settings, and the AI tool loses access on its very next request.

Dotfile also tells your AI tool which actions change data and which delete it, so the AI tool can ask you before running them. Keep that confirmation on for anything that approves, rejects or emails someone.

Connect in three steps

  1. In Dotfile, click your name at the bottom of the left sidebar, open Account Settings, then the Connections tab, and click Copy URL.
  2. In your AI tool, add a custom connector (or remote MCP server) with that URL, and choose Connect.
  3. Sign in with your Dotfile account and approve access. The AI tool now appears under Connected applications, where you can revoke it at any time.

One connection covers every workspace your account can access, so name the workspace in your request when you work across several. The documentation has the exact steps for Claude, ChatGPT, Cursor and Claude Code.

Read the documentation to connect your AI tool.

Ready for Anywhere?

Verify any business, enter any market, defend every decision. Every signal orchestrated, every decision traceable, from one platform.

Book a demo