This feature is currently in early access.
Moss's MCP (Model Context Protocol) server lets AI assistants such as Claude and ChatGPT access your Moss data. This means you can ask questions, build reports or automate workflows from your Moss data, through your AI assistant.
Server URL
Environment | URL |
Production |
|
Setup steps for specific AI assistants can be found below:
How the Moss MCP works
Ask Moss anything. Query your spend data directly from the AI assistants your team already uses. Run natural-language queries across your Moss data, with no need for manual exports or spreadsheets
Multi-entity, out of the box. Connect once and query across every organisation you administer. There’s no per-entity setup, so cross-entity reporting is possible from the first query. Ideal for admins managing multiple organisations
Data access on your terms. Connect to your organisation's data, and query only what you're already permitted to see in Moss. Each query retrieves only the data relevant to the question, which ensures a more reliable response, and minimises token cost
What's available today
Moss MCP groups data for you to query via your AI Assistant, and will continue to add new data over time. Moss MCP currently supports:
Expenses. Look up expenses across all expense types
Attachments. Look up attachments held in Moss
Moss Accounts. Check Moss account balances and transactions
Budgets. Look up budget data
Suppliers. Look up supplier data
All data is read-only. Your assistant can look up data, but cannot create, edit, or delete anything in Moss.
Important things to note
Access to data still depends on your admin permissions in Moss. If you can't see something in the product, your assistant won't see it either
We will continue to add new data groups over time for you to query. You may need to disconnect and reconnect your AI Assistant to see the latest list of supported data
The list above reflects what data is supported today, and more will become available over time. Reach out to us if you need data that isn't listed here
Connecting to AI Assistants
Before you start
You'll need:
A Moss admin account. MCP access is limited to admin users
An MCP-compatible AI assistant
Connect with Claude
These setup instructions are for individual Claude plans. For managed Claude plans, follow the instructions for Claude for Teams or Enterprise below.
Claude Desktop or claude.ai
Go to Settings > Connectors
Select Add custom connector
Enter the server URL:
https://mcp.getmoss.com/mcpSelect Add, then log in to Moss when prompted and choose which organisation(s) to share with your assistant
Claude Code
Run this in your terminal:
claude mcp add --transport http moss-server https://mcp.getmoss.com/mcp
Then start a Claude Code session and run /mcp to complete the login.
Claude for Team or Enterprise
On managed Claude plans, an Owner or Primary Owner adds the connector for the organisation first. Individual admins then connect their own account.
Set-up steps for owner (one-time setup):
Go to Organisation settings > Connectors
Select Add, hover over Custom, then select Web
Enter the server URL:
https://mcp.getmoss.com/mcpSelect Add to finish
Set-up steps for each Moss admin:
Go to Customise > Connectors
Find the Moss connector, labelled Custom
Select Connect, then log in to Moss and choose which organisation(s) to share
Possible errors
Downloading an attachment fails with a "sandbox network proxy" error
Claude is able to look up your expense and attachment data through the Moss MCP. To open or save the file, Claude has to reach out to the internet from a separate, locked-down environment. By default, that environment can only reach a short list of approved websites. If mcp.getmoss.com is not on that list, the download fails with the "sandbox network proxy" error.
Your Claude admin is able to fix this problem. To resolve:
Go to Organization settings > Capabilities > Code execution.
Under Additional allowed domains, add
mcp.getmoss.com.Check the Domain allowlist dropdown: set it to Package managers only. (If it's already set to All domains, there's nothing else to change.)
Once that's saved, ask Claude to try the download again. You don't need to reconnect or re-authorise the Moss MCP.
For more information on why Claude separates "looking up data" from "downloading files" this way, see Anthropic's Use Claude Cowork on Team and Enterprise plans.
Connect with ChatGPT
ChatGPT connects to custom MCP servers through a beta feature called Developer mode. OpenAI changes this menu fairly often, so if these steps don't quite match what you see, check OpenAI's help centre for the current path.
Open ChatGPT and go to Settings > Apps
Under advanced settings, turn on Developer mode
Open Plugins, select the + button, and add a new connection
Enter the server URL, including the path:
https://mcp.getmoss.com/mcpComplete the login prompt to connect your Moss account and choose which organisation(s) to share
On Business, Enterprise, or Edu workspaces, a workspace admin needs to enable Developer mode and custom apps for the workspace first, from Workspace settings > Apps, before members can add the Moss connector themselves.
Connect with another MCP client
If your tool takes a JSON configuration instead of a URL field, add:
{
"mcpServers": {
"moss-server": {
"type": "http",
"url": "https://mcp.getmoss.com/mcp"
}
}
}
The wrapping key (mcpServers, servers, and so on) and the type field vary by tool. Check your AI Assistant's own MCP setup instructions if this snippet needs adjusting.
Authorising access
The first time you connect, Moss will ask you to log in and pick which organisation(s) your assistant can see. Only organisations where you are an admin appear in that list, and only the ones you select become visible. Nothing else in your Moss account is exposed by default.
You can grant access to more than one organisation and query across all of them at once, with no extra setup per entity. To remove access later, go to the MCP settings page in your Moss settings and revoke it there.
Data and security
Access is read-only. Your assistant can look up data but cannot make changes in Moss
Access is limited to admin users and scoped to the organisation(s) you authorise. Your assistant cannot see data from any organisation you haven't granted access to
Access follows your existing Moss permissions. You only see what you're already permitted to see in the product, nothing more
Every connected AI assistant shows up on the MCP settings page in your Moss settings, so you can see and manage what's connected at any time
Login uses a secure OAuth flow. For supported clients like Claude, you never need to handle or paste an access token yourself
Troubleshooting
Your assistant says it has no access, or returns empty results. Reconnect and make sure you selected the correct organisation(s) during login
The connection fails or drops. Disconnect and reconnect the connector in your assistant's settings. Some clients cache an old session
Your client isn't listed here. Use the server URL (
https://mcp.getmoss.com/mcp) or the JSON snippet above with any MCP client that supports remote HTTP servers and OAuth 2.1.
FAQ
How do I get access to Moss MCP? During early access, contact your CSM to enable this feature for your Moss organisation.
Is this read-only? Yes. Your assistant can look up data in Moss but cannot create, edit, or delete anything.
Do I need to be an admin? Yes. MCP access in Moss is limited to admin users.
Can I connect to more than one organisation? Yes, you choose which ones during authorisation, and your assistant can query across all of them without any per-entity setup.
Do I need a developer to set this up? No. Paste the URL (or JSON snippet) into your AI assistant's connector settings and log in.
Where can I see what's connected? The MCP settings page in your Moss settings lists every connected AI assistant.
Does my access expire? Yes. For security, MCP access expires 30 days after you connect, regardless of usage. You will need to log in through your assistant's connector settings to reconnect.