Practice Management MCP Server

The Model Context Protocol (MCP) is an open standard that lets AI assistants like Claude, ChatGPT, and Gemini talk to other apps. Instead of you copying data into a chat window, the AI connects straight to the source and reads what it needs.

The Sodium MCP server turns your practice management data into one of those sources - clients, tasks, deadlines, proposals, and more. Ask Claude "what's on my plate today?" and it will actually go and find out.

Choose your agent:

ClaudeChatGPTGemini CLI

On claude.ai - paid plans.

1. Open Settings → Connectors → Add custom connector
2. Name it Sodium and paste https://mcp.sodiumhq.com
3. Leave Advanced settings (OAuth Client ID and Client Secret) completely empty - Claude handles these itself
4. Click Add, then Connect. A browser window opens with the Sodium sign-in page - sign in there the same way you sign in to Sodium (Xero, Google, or email). Never type your login details into the connector form itself

Then ask: "give me a summary of my practice in Sodium". If everything is wired up, you'll get your practice details back within a few seconds.

You sign in as yourself, and the AI can only see what you can see. If you belong to one practice, it's selected automatically. If you belong to several, just say which one - "in Smith & Co, what's overdue?" - and the AI carries your choice through the conversation.

Once connected, try prompts like these in your AI assistant:

• "I'm about to jump on a call with ACME Ltd. Brief me - contacts, active services, statutory dates, and anything overdue or due this week."
• "Which proposals I sent in the last month are still sitting unsigned with the client?"
• "What's on my plate today, and what else is due this week?"
• "Show me Jane's overdue tasks."
• "What's overdue for Smith and Co?"
• "How many tasks are open across the practice?"
• "Summarise the most recent engagement letter we sent to ACME - what services, what price, and has it been signed?"
• "Give me a snapshot of the practice." - counts, integrations in use, and settings at a glance
• "What are the custom fields on Smith & Co?"
• "Find me the contact details for John Smith."
• "Show me the notes on ACME Ltd."
• "Create a new prospect called Greggs Carpentry - it's a sole trader, assign Jane as the manager."

The AI picks the right tool on its own - you just ask the question.

The connector ships with a growing set of tools covering the day-to-day questions accountants ask most - clients, contacts, tasks and deadlines, proposals and engagement letters, services and pricing, time tracking, document and questionnaire requests, workflows, reports, Companies House lookups, AML status, billing, and more.

It can also make changes for you: create clients, contacts, tasks, and notes; update tasks and workflow steps; log time; draft document requests and proposals; and keep custom fields and client details current. Changes are create-and-update only - the AI can never delete anything or run bulk operations, full stop.

• You sign in as you. The connector uses your Sodium login (OAuth) - there are no shared API keys and nothing to paste into the AI vendor's settings.
• Your permissions apply. Every request the AI makes is treated as if you made it yourself - it only ever sees your own practice's data, and that is checked on every single call.
• No destructive actions. Delete and bulk operations are not exposed to AI at all - not as an option, not behind a setting.
• Revoke any time. Remove the connector from your AI assistant's settings and access ends there and then.

Connecting an AI assistant to live client data is a normal, manageable thing to do - but your firm, not the AI vendor, stays the data controller. A few minutes of housekeeping covers it:

• Use a business tier. We recommend connecting Sodium to a business or organisational AI account rather than a personal consumer account. Consumer and business plans from Claude, ChatGPT, and Gemini can differ on model training, retention, contractual protections, and where data is processed. Business, Team, Enterprise, and API offerings typically come with clearer data-processing terms and no-training-by-default protections.
• Get the paperwork in place. Where the AI vendor processes client personal data on your firm's behalf, make sure the appropriate data processing terms are in place - including any required transfer safeguards (UK IDTA, or SCCs plus the UK Addendum) for providers hosting outside the UK.
• Update your records. Add the assistant to your record of processing and your privacy notice, and consider whether a DPIA is warranted given the volume of client personal data it can reach.
• Confidentiality sits alongside it. ICAEW, ACCA, and CIOT duties of confidentiality apply as well as UK GDPR - worth checking your engagement letters cover the use of third-party AI tools.

You choose your AI provider. Sodium does not require or appoint Claude, ChatGPT, Gemini, or any other AI assistant on your behalf. When you connect an external assistant to Sodium, your firm is responsible for making sure its use of that provider is appropriate for the client data you choose to make available to it.

On our side, Sodium acts as your processor under our Data Processing Agreement, and the connector only ever returns data your own login can already see.

For Claude Desktop, Claude Code, Cursor, and VS Code you can also run the connector on your own machine as an npm package - @sodiumhq/mcp-pm. This route has its own requirements: Node.js 20 or later on your machine, a Sodium API key, and your tenant code - it authenticates with the key instead of your login.

1. Grab your API key and tenant code. In Sodium, open the profile menu in the top right and click API Keys. Create a new key and copy it. Your tenant code is the subdomain in the URL you use to log in - if you sign in at acme.sodiumhq.com, your tenant code is acme.

2. Add Sodium to your AI client's config - for Claude Desktop that's ~/Library/Application Support/Claude/claude_desktop_config.json on Mac, or %APPDATA%\Claude\claude_desktop_config.json on Windows. Cursor and VS Code use the same JSON shape in their MCP settings:

{
  "mcpServers": {
    "sodium": {
      "command": "npx",
      "args": ["-y", "@sodiumhq/mcp-pm@beta"],
      "env": {
        "SODIUM_API_KEY": "your-api-key",
        "SODIUM_TENANT": "your-tenant-code"
      }
    }
  }
}

Claude Code - run this in your terminal:

claude mcp add sodium \
  --env SODIUM_API_KEY=your-api-key \
  --env SODIUM_TENANT=your-tenant-code \
  -- npx -y @sodiumhq/mcp-pm@beta

On the local package, write tools are off by default - add --enable-writes or set SODIUM_ENABLE_WRITES=true to opt in. The API key acts at practice level, so only enable writes with an AI client you trust.

• An active Sodium account
• An AI assistant that supports custom connectors - Claude (paid plans), ChatGPT (plans with custom plugins), or Gemini CLI

That's the whole list - no software to install and no API keys to manage.

What is an MCP server for practice management?

An MCP (Model Context Protocol) server lets AI assistants like Claude, ChatGPT, and Gemini read and act on live data in other software. Sodium's official MCP server connects them to your practice management data - clients, tasks, deadlines, proposals, engagement letters, time, and more - using your own Sodium login.

How do I connect Claude to Sodium?

In claude.ai, open Settings → Connectors → Add custom connector. Name it Sodium, paste https://mcp.sodiumhq.com, leave the Advanced settings empty, click Add, then Connect, and sign in with your Sodium account. The whole thing takes about two minutes.

Does Sodium work with ChatGPT and Gemini?

Yes. ChatGPT connects as a custom plugin once Developer mode is enabled, and Gemini CLI connects with a small settings snippet. Claude Desktop, Claude Code, Cursor, and VS Code are also supported via the @sodiumhq/mcp-pm npm package.

Is the Sodium MCP connector secure?

Yes. You sign in to the hosted connector with your own Sodium login via OAuth, so there is no shared API key to hand over. Every request the AI makes is treated as if you made it yourself - it only ever sees your own practice's data, and only what your permissions already let you see. It cannot reach anything your own login cannot, and it has no way round a permission you do not have. Delete and bulk operations are not exposed to AI at all, and you can revoke access at any time from your AI assistant's settings.

Is connecting AI to my practice management data GDPR compliant?

It can be, and most firms cover it in a few minutes. Your firm remains the data controller, and you choose your own AI provider - Sodium does not appoint one for you. We recommend a business tier of Claude, ChatGPT, or Gemini, since those typically come with clearer data-processing terms and no-training-by-default protections. Where the vendor processes client personal data on your behalf, put the appropriate terms and transfer safeguards in place, then add the assistant to your record of processing and privacy notice. Sodium acts as your processor under our DPA, and the connector only returns data your login can already see.

Do I need an API key to use the Sodium MCP server?

No. The hosted connector at https://mcp.sodiumhq.com uses OAuth sign-in with nothing to install. An API key is only needed if you choose to run the local npm package for Claude Desktop, Claude Code, Cursor, or VS Code.

The connector is evolving quickly, with new tools landing all the time. If you hit an issue or have a request, email us at hello@sodiumhq.com and we'll take a look.

Under the hood, the connector speaks to the same API that powers the rest of Sodium - so as the API grows, so does what your AI assistant can do.