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
What you can do with Moss MCP
You can use Moss MCP for the questions that would usually require an export, filter, and spreadsheet. The examples below are grouped by the finance task they help with. Copy a prompt, then change the period, entity, or supplier to fit your case.
Reviewing expenses before export
Reviewing expenses before export
Catch coding and VAT mistakes in Moss, before they reach your accounting system and need a correction.
Use case | Example prompt | What you get |
Find expenses that aren't ready to export | "Which invoices submitted in the last seven days are missing a GL account, cost centre, or VAT rate?" | A list of expenses to complete. |
Check coding against past bookings | "For our 20 most frequent suppliers, show the GL account and cost centre we usually use, and flag recent invoices that differ." | Bookings that don't match how you've coded the supplier before. |
Check VAT on card spend | "Check last quarter's card spend for transactions where the VAT rate doesn't fit the merchant's country." | Transactions where input VAT may be wrong. |
Compare receipts with charges | "Find card transactions from last month where the receipt amount differs from the charged amount." | Mismatches to review before export. |
Accounts payable
Accounts payable
Plan payment runs, keep invoices moving, and answer supplier questions.
Use case | Example prompt | What you get |
Prepare a payment run | "Show unpaid supplier invoices due in the next 14 days, grouped by entity and supplier." | The invoices to include in your next payment run. |
Follow up on overdue invoices | "Which supplier invoices are overdue? Sort them by days overdue." | An ageing view of what's late. |
Read an invoice | "Find the PDF of our most recent office rent invoice and show me the net amount, VAT, and service period." | Figures read directly from the attached document. |
Cards and employee expenses
Cards and employee expenses
Keep card spend documented and spot spend that shouldn't be there.
Use case | Example prompt | What you get |
Chase missing receipts | "List card transactions older than 14 days that still have no receipt, grouped by employee." | Who to remind, and for which transactions. |
Find duplicate subscriptions | "Are we paying for the same software tool on more than one card?" | Duplicate tools and the cards paying for them. |
Summarise travel spend | "Summarise last month's travel spend by team, with receipt status." | A travel and expense summary you can share. |
Cash management
Cash management
Know your available cash across entities without logging in to each one.
Use case | Example prompt | What you get |
Check balances across entities | "What's the current balance of each Moss Account? Flag any below EUR 2,500." | Balances per entity and currency, with low balances highlighted. |
Build a daily cash overview | "Build a daily overview with each Moss Account balance and yesterday's card spend." | An overview your assistant can refresh on request. |
Spend analysis and budgets
Spend analysis and budgets
Answer questions from management and budget owners about where money goes.
Use case | Example prompt | What you get |
Size spend with a vendor | "How much did we spend with our cloud hosting providers this year, by month and entity?" | Totals across all supplier accounts for the same vendor. |
Rank suppliers by spend | "Show the top 10 suppliers by net spend last quarter, across all entities." | A ranked list for supplier reviews or negotiations. |
Compare periods | "Compare marketing spend this quarter with the same quarter last year, by cost centre." | The change per cost centre and what drove it. |
Track budget usage | "Show consumed and available amounts for each budget this month." | Budget vs actual per budget. |
See what's using a budget | "Which expenses count towards the team offsite budget so far?" | The invoices and card transactions behind the consumed amount. |
Audit and internal controls
Audit and internal controls
Answer auditor requests and check your controls without pulling exports.
Use case | Example prompt | What you get |
Review approvals | "Who approved invoices over EUR 10,000 last quarter?" | Each large invoice with its approver. |
Verify supplier bank details | "For invoices from suppliers added this quarter, does the IBAN on the attached invoice match the bank details stored in Moss?" | Mismatches to check before you pay, a common sign of invoice fraud. |
Pull supporting documents | "Get all invoices from our legal advisers for last year and total the fees per entity." | The documents and a total per entity. |
To open or download files, your assistant may need extra network access. See possible errors if a download fails.
Recurring checks
Recurring checks
Run a check once, then ask your assistant to repeat it.
Use case | Example prompt | What you get |
Weekly pre-export check | "Every Monday, list new invoices with missing coding." | A recurring check, if your assistant supports scheduled tasks. |
Tips for better results
Name the period, entity, and currency. For example "September 2026, UK entity, in EUR"
Include whether you want net or gross amounts
Ask for totals at invoice or transaction level. Split expenses have several lines, and adding up every line can double-count
For large requests, ask for a summary first, then drill into the detail
If a number looks off, ask your assistant which filters it used
Check AI answers before you book or pay anything based on them
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.comCheck 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 Codex
In your terminal, run:
codex mcp add moss-server --url https://mcp.getmoss.com/mcp
Run codex mcp login moss-server to open your browser, sign in to Moss, and complete the OAuth flow.
Codex registers itself with Moss automatically so you will not need a Client ID.
Connect with Microsoft Copilot Studio
Copilot Studio connects to Moss MCP through its MCP onboarding wizard. Moss's MCP server requires manual OAuth 2.0 configuration (not dynamic client registration), so use the Manual authentication option.
In Moss, go to Settings > MCP and click on Microsoft Copilot Studio
In Copilot Studio, go to your agent's Tools page, select Add a tool > New tool > Model Context Protocol
Enter a Server name and Server description, and set Server URL to:
https://mcp.getmoss.comUnder authentication type, select OAuth 2.0, then Manual
Fill in the fields using the values from Moss's MCP settings page: Client ID, Client Secret, Authorization URL, Token URL template, Refresh URL, Scopes (optional)
Select Create. Copilot Studio generates a callback URL
Copy that callback URL and add it back on the Moss MCP settings page, so Moss's identity provider recognises Copilot Studio's redirect
Click on Connect
Select Next, choose Create a new connection (or an existing one), then Add to agent to finish
You can learn more about connecting with Microsoft Copilot studio in their help centre: https://learn.microsoft.com/en-us/microsoft-copilot-studio/mcp-add-existing-server-to-agent
Connect with Langdock
In Moss, go to Settings > MCP and click on Langdock
In Langdock, add a new MCP integration and enter the server URL:
https://mcp.getmoss.com/mcpSelect OAuth 2.0 Manual (Authorisation Code + PKCE) as the authentication method
Copy the OAuth redirect URL Langdock shows you, and add it back on the Moss MCP settings page
Enter the Client ID and Client Secret from Moss into Langdock
Add the Authorization URL and Token URL from Moss
Enter the Scopes from Moss's settings page (space- or comma-separated).
Leave Send resource parameter enabled
Select Test connection to confirm access and see available tools, then Save
You can learn more about connecting with Langdock via their help centre: https://docs.langdock.com/en/using-langdock/guides/integrations/mcp/mcp#oauth-2-0-manual-authorization-code-%2B-pkce
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.
Access expires automatically 30 days after you connect, regardless of how often you use it. This is a security measure. When it expires, your assistant will lose access to your Moss data and needs to reconnect and log in again to refresh it.
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
MCP access expires automatically 30 days after you connect, even if you've been using it regularly during that time. If it's been about a month since you last logged in, this is the likely cause. Reconnect to refresh it
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) with any MCP client that supports remote HTTP servers and OAuth 2.1.
FAQ
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. Simply 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.