🎉 Beta feature: Fathom's MCP is currently in beta, so you must turn on the beta flag to access it. If you run into any issues or have feedback, please reach out to our team at support@fathomhq.com.

What is an MCP?

A Model Context Protocol (MCP) provides your AI tool with access to your Fathom data and the context the tool needs to understand the data.

By connecting Fathom’s MCP, your AI tool has the logic behind how the data relates to one another, not just the hard-coded numbers. MCPs help AI tools, like large-language models (LLMs), understand your data when you ask a natural language question, so the tool can retrieve and reference the correct data.

What can you do with Fathom's MCP?

With Fathom’s MCP, you can use natural language to interrogate and analyse your Fathom data in your chosen AI tool (Claude, Cursor, Windsurf, VS Code, etc.).

📝 Note: We've heard from users that the "free version" of Claude does not allow you to use PAT tokens to connect to MCPs, including Fathom's MCP.

You can bring your Fathom data into your connected AI tool, but you cannot send instructions or data back into Fathom.

Fathom's MCP will provide the connected AI tool with the following types of data:

The Fathom organisations or accounts you are a member of
The companies connected to your Fathom organisation(s) that you can access
P&L data for your entities
Balance Sheet data for your entities
KPI data for your entities
Cash flow statement data for your entities
Chart of accounts data for your entities

Forecast and budget data currently cannot be accessed via Fathom's MCP.

How to connect to Fathom's MCP

You can connect your AI tool to Fathom’s MCP with a Personal Access Token (PAT). The PAT will provide your AI tool with read-only access to your data in Fathom.

Because PATs are specific to the individual, your PAT will be able to read data according to your personal role and permissions in Fathom. You cannot access additional data in Fathom with your PAT.

📝 Note: OpenAI's ChatGPT and Google's Gemini do not support PAT connection, so it is currently not possible to connect them to Fathom's MCP.

Instructions for AI tools vary, so we recommend asking your tool for the most up-to-date instructions.

You can enter the following prompt in your AI tool to get it to generate instructions for you:

I use a tool called Fathom to track and analyse financial data. I want to give [AI tool’s name] access to my data in Fathom via Fathom’s MCP. Fathom provides me with a Personal Access Token (PAT) to access the Fathom MCP. The URL to connect to Fathom’s MCP is https://api.fathom.dev/mcp. Please give me step-by-step instructions for connecting Fathom’s MCP to [AI tool’s name].

Once you have the instructions from your AI tool, you're ready to create a PAT token for Fathom (make sure you have the appropriate permissions).

To get a PAT for Fathom:

Click the User icon in the top right of the ‘My Companies’ page.
Select Personal Access Tokens from the dropdown menu.

📝 Note: If you do not see the ‘Personal Access Tokens’ option, you may not have permissions to create them in Fathom. An Admin-level user in your Fathom organisation will have to provide you with the ‘Setup > Create Access Tokens’ advanced user permission.
Click Create a token.
1. Name the token. Make the name specific for easier identification later if you need to manage or revoke access.
2. Select an expiry date for the token (30, 60, or 90 days). The token will automatically expire and cannot be renewed. Instead, you will generate a new token when needed.
Copy the token immediately. The token is only shown when it’s created, so if you navigate away from the page or refresh the page without copying it, you will have to create a new token.

Be careful and treat your PAT like a password, as anyone who has access to it can access your Fathom data.
As part of the MCP connection process, your AI tool may ask you for the following when you create the MCP connection:
1. A URL to connect to Fathom. You can enter the following URL when needed: https://api.fathom.dev/mcp.
2. A name for the Fathom MCP connection. Name it something simple and easy to identify, like 'Fathom'.
3. Your PAT token.

Managing or revoking access

Manage or revoke your own MCP connections

You can view and remove your own PATs from the Personal Access Tokens page. Removing a PAT will remove the MCP connection/access provided to the associated AI tool.

To manage or remove your PATs:

Click the User icon on the top right of the ‘My Companies’ page.
Select Personal Access Tokens from the dropdown menu.
You will see your PATs. If you are part of multiple Fathom organisations, you will be able to see which Fathom organisation is associated with a PAT.
To revoke a PAT, click Revoke access. In the pop-up modal, click Revoke token.

User permissions needed for MCP

To use a PAT token to connect to Fathom's MCP, two advanced user permissions are needed:

External Connectivity > Create Access Tokens
External Connectivity > Connect MCP

For Admin-level users, both permissions are enabled automatically.

For Advisor/Editor- or Client/Viewer-level users, you must enable these permissions before they can create PAT tokens and use them to access the Fathom MCP.

Manage or revoke others' MCP connections

Admin-level users in a Fathom account can manage and revoke MCP access for others in the Organisation Settings.

To manage or revoke other users' PAT tokens:

Click the Cog/Gear icon in the top right corner of the ‘My Companies’ page.
Select Organisation Settings from the dropdown menu.
On the left sidebar, click Security > Access Token Management.
You will see the PATs created for your Fathom organisation and who created each PAT.
To revoke a PAT, click Revoke access. In the pop-up modal, click Revoke token.

If you want to revoke all the PATs for a specific user, you can turn off the ‘External > Create Access Tokens’ advanced user permission, and that will automatically revoke all the PATs for that individual user.

Learn more

Fathom's Report Commentary Writer