Which MCP Servers Connect to Finance and Accounting Platforms?

Finance servers connect AI agents to the platforms where teams manage invoices, reconcile transactions, track expenses, and query banking data. Independent evaluations of every significant server in this category, covering Xero, QuickBooks, Mercury, Spendesk, and Dynamics 365, not directory listings or vendor documentation.

Model Context Protocol (MCP) lets AI clients query ledgers, create invoices, reconcile bank transactions, and pull financial reports through a standardized JSON-RPC 2.0 interface. Anthropic introduced MCP as an open standard in November 2024. The Linux Foundation’s Agentic AI Foundation (AAIF) now governs the specification (Linux Foundation, “Agentic AI Foundation Launch,” December 9, 2025). Finance is the earliest-stage MCP category. Most accounting software vendors have not shipped official servers as of mid-2026. The servers that exist establish the patterns the rest of the market will follow.

The full MCP server directory covers all 14 server categories. This page focuses on finance and accounting servers alone. Payment processing (Stripe MCP) is covered in the CRM and marketing server hub.

What Does a Finance MCP Server Do?

A finance MCP server exposes accounting records, invoice management, bank transaction data, expense tracking, or financial reporting as callable tools. The AI client queries ledgers, creates invoices, reconciles transactions, and generates reports through a standardized JSON-RPC interface.

Finance servers operate on the most sensitive business data in any MCP category: bank balances, transaction amounts, customer payment records, tax calculations, and compliance documents. The default access model for finance is read-only. Most teams query and analyze financial data through MCP but trigger write operations (creating invoices, processing payments) through separate, audited paths.

4 finance functions define this category:

• Accounting platforms connect to Xero, QuickBooks, and similar ledger systems. Tools expose invoice management, contact records, bank transactions, journal entries, payment tracking, and financial reporting.
• Spend management connects to Spendesk, Norman Finance, and similar platforms. Tools expose payables, supplier management, purchase orders, budget variance analysis, and expense categorization.
• Banking connects to Mercury and similar platforms. Tools expose account balances, transaction history, card management, and recipient operations.
• Enterprise finance connects to Microsoft Dynamics 365 Finance and similar ERP (Enterprise Resource Planning) systems. Tools expose financial operations, supply chain management, and compliance workflows at organizational scale.

Finance MCP adoption is earlier-stage than CRM, monitoring, or design. Xero and QuickBooks have shipped official servers. Most other accounting vendors have not.

How Do You Evaluate Finance Servers?

Evaluate finance servers on 5 criteria: finance function, read/write boundary enforcement, auth model, audit trail support, and compliance compatibility. These dimensions determine whether a server is safe for production financial data.

Finance Function

Accounting servers manage the general ledger. Spend management servers manage payables and expenses. Banking servers manage cash positions. Enterprise servers manage cross-functional financial operations. Match the server to the finance function the team needs automated.

Read/Write Boundary Enforcement

Finance servers that separate read from write at the tool level are safer than servers that expose both through the same permissions. Spendesk MCP is read-only by design. Xero MCP scopes read and write access through OAuth scope parameters. QuickBooks MCP exposes full CRUD (Create, Read, Update, Delete) operations. Read-only access is the default starting point for finance data.

Auth Model

Xero uses OAuth 2.0 with configurable scopes (accounting.invoices, accounting.contacts, accounting.settings). QuickBooks uses OAuth through Intuit’s developer platform. Mercury uses API keys. OAuth-based servers provide granular permission control. API key servers grant account-level access.

Compliance and Audit Trail

Financial operations require traceable records and regulatory compliance. Servers that log every tool call support GAAP (Generally Accepted Accounting Principles) and IFRS (International Financial Reporting Standards) requirements. Servers that respect existing platform permissions inherit the compliance controls already configured in the accounting platform. Spendesk’s read-only design eliminates write-side audit concerns entirely.

The rubric above applies to every server profiled in the next section.

Which Servers Connect to Finance Platforms Through MCP?

5 finance servers expose MCP-compatible tools as of mid-2026. Xero provides the most mature accounting integration with official OAuth support. QuickBooks provides 2 implementation paths. Mercury provides banking data access. The category is earlier-stage than CRM or monitoring, with most accounting vendors yet to ship official servers.

Xero MCP (Official)

Xero maintains the official MCP server at @xeroapi/xero-mcp-server on npm. Auth: OAuth 2.0 with configurable scopes. Transport: local (stdio via npx). Tools expose contacts, invoices, accounts, bank transactions, journals, organisations, payments, and quotes.

OAuth scopes control access granularity: accounting.invoices for invoice operations, accounting.contacts for contact management, accounting.settings for organization configuration. Teams configure the minimum scopes required for their workflow.

Xero completed an API scope migration in early 2026. Apps created after March 2, 2026 use updated scope definitions. The MCP server provides both @latest and @beta npm tags during the transition period. Xero MCP is the most mature accounting MCP server with direct vendor support.

QuickBooks MCP (Official + Community)

QuickBooks provides 2 implementation paths. Intuit maintains an official MCP server on GitHub with approximately 20 tools covering CRUD operations on core accounting entities: customers, vendors, invoices, bills, payments, and estimates. Auth: OAuth through Intuit’s developer platform. Transport: local (stdio).

MCPBundles provides a community alternative with 34 tools, adding financial reports, batch operations, and a hosted deployment option. The community server works with any MCP client (Claude Desktop, Cursor, ChatGPT). The official server connects via stdio only.

QuickBooks supports a SQL-like query dialect for data retrieval. Agents write queries like SELECT * FROM Invoice WHERE TotalAmt > 100 ORDERBY DueDate to search accounting records. The query interface covers WHERE clauses, ordering, and pagination without requiring full SQL (Structured Query Language) support.

Mercury MCP (Official)

Mercury maintains the official MCP server for banking data. Auth: API key. Transport: local. Tools expose account balance queries, transaction history retrieval, card management, and recipient operations. The server provides real-time cash position data, pending transaction visibility, and card-level spending breakdowns.

Mercury MCP provides the banking layer that accounting servers do not cover. Xero and QuickBooks track ledger entries after bank transactions clear. Mercury provides the real-time view: current balances, in-flight transfers, and card authorization details. The server complements accounting servers by connecting the live banking position to the historical ledger record. Mercury targets startups and growing companies that use Mercury as their primary business banking platform.

Spendesk MCP (Official)

Spendesk maintains the official MCP server for spend management. Auth: connected through AI assistant integration settings. Transport: remote. The server is read-only by design: it queries and analyzes spend data but cannot create payments, modify invoices, or change any records. No write operations exist regardless of agent behavior.

Read-only capabilities include cash position queries, overdue accounts payable analysis, spend-by-department breakdowns, payment status tracking, invoice matching, budget variance analysis, and supplier intelligence. Spendesk integrates with Xero, Sage, QuickBooks, and NetSuite through its own platform integrations. The MCP server exposes Spendesk’s consolidated spend view across all connected accounting platforms. The read-only architecture makes Spendesk the safest finance MCP server for compliance-sensitive environments.

Dynamics 365 Finance MCP (Microsoft)

Microsoft provides MCP support through Dynamics 365 Finance and Operations. Auth: Microsoft identity platform. Transport: remote. The server covers enterprise-scale financial operations, supply chain management, and compliance workflows.

Dynamics 365 targets organizations running Microsoft’s ERP stack. The server complements HubSpot or Salesforce CRM servers by connecting the financial operations layer to the same agent conversation.

Server selection follows the accounting platform. Xero teams install Xero MCP. QuickBooks teams install QuickBooks MCP. Mercury adds banking data. Spendesk adds spend management. Dynamics 365 covers enterprise ERP.

The sections above define finance MCP servers, provide an evaluation rubric, and profile every significant server in the category. The sections below address the read-only default for financial data and answer the questions that surface during platform selection.

Why Is Read-Only the Default for Finance Servers?

Financial data carries the highest consequence for incorrect write operations in any MCP category. An agent that creates a wrong invoice, miscategorizes a transaction, or modifies a payment record produces audit trail contamination that requires manual correction. Read-only access eliminates this risk.

Spendesk enforced read-only at the architectural level. The server cannot modify data regardless of agent behavior. Xero MCP achieves read-only through OAuth scope restriction: omit write scopes and the server rejects modification requests. QuickBooks MCP exposes full CRUD by default, requiring teams to implement application-level controls.

The recommended progression: start with read-only access for financial analysis and reporting. Add write access only for specific, low-risk operations (creating draft invoices, categorizing expenses). Route high-risk operations (processing payments, modifying tax records) through human approval workflows. The questions below address the remaining selection decisions.

Frequently Asked Questions

Which Accounting Server Is Most Mature?

Xero MCP is the most mature accounting MCP server with direct vendor support, OAuth 2.0 with configurable scopes, and a completed API scope migration. QuickBooks MCP provides a broader tool surface (34 tools via MCPBundles) but the official Intuit server is more limited (~20 tools).

Can Finance Servers and CRM Servers Work Together?

Xero or QuickBooks MCP runs alongside HubSpot or Salesforce MCP. A common workflow: query CRM for a customer’s deal history, then query the accounting server for invoices and payment records associated with that customer. Each server authenticates independently. Financial context combined with CRM context produces more accurate customer analysis.

Why Have Most Accounting Vendors Not Shipped MCP Servers?

MCP adoption in finance lags behind CRM and developer tools by 12 to 18 months. Xero, Intuit (QuickBooks), Spendesk, and Microsoft (Dynamics 365) have shipped. Sage, FreshBooks, Wave, and NetSuite have not as of mid-2026. The regulatory sensitivity of financial data and the compliance requirements for write operations slow vendor adoption compared to categories where read-only access is sufficient.

Does Spendesk MCP Connect to Other Accounting Platforms?

Spendesk integrates with Xero, Sage, QuickBooks, and NetSuite through its own platform integrations. The MCP server exposes Spendesk’s spend data (payables, suppliers, purchase orders) but does not directly query the connected accounting platform. 

How Does Xero’s Scope Migration Affect MCP Setup?

Xero updated its API scopes in March 2026. Apps created after March 2, 2026 use the new scope definitions. The Xero MCP server provides @latest (pre-migration) and @beta (post-migration) npm tags during the transition. Teams installing for the first time use @beta. Teams with existing installations continue on @latest until Xero consolidates the tags. The migration affects which accounting data scopes are available, not the MCP protocol itself.