MCP Connector Directory

Accounting Intelligence calls tools on 25 third-party MCP servers, listed below by category. Every connector here is already integrated, so there is no server address to find and nothing to build: you install and connect each one inside DualEntry, on the Connectors page under Accounting Intelligence. Each card below links to that provider’s own MCP documentation, which is where the authoritative tool list, scopes, and rate limits live. The DualEntry side of the work is documented once, in How to Connect an MCP Connector: an admin installs the connector for the organization, then every user who wants it authorizes their own account, and read-only tools become available to Accounting Intelligence while tools that write stay disabled until someone allows them. A connector you need that is not listed here can still be added by URL as a custom connector, as long as the vendor runs an MCP server you can reach.

​

Accounting

Accounting connectors cover subledgers DualEntry does not keep itself, so balances and activity from those systems can be read during close without leaving a conversation. What comes back is reference data for a question you are working through, not a posting: nothing a connector returns reaches the ledger until you draft the entry yourself.

​

Banking

A banking connector reads balances and transactions straight from the bank, which is useful for checking bank-feed health against what DualEntry has already imported. It is separate from a bank connection, which is what actually feeds transactions into Bank Match. A banking connector answers questions about the account; it does not import anything.

​

Payments

Payment connectors reach the processors and spend platforms that generate cash activity, so Accounting Intelligence can trace a payout or a card charge back to its source record. The usual question is why a deposit and an invoice disagree, which means reading fees, refunds, and settlement timing out of the processor rather than guessing at them from the bank line.

​

Email and calendar

Email and calendar connectors let Accounting Intelligence find the thread behind a transaction and draft correspondence from a live record, as in an AR dunning run. Each one authorizes per user, so drafts land in the mailbox of whoever asked and no shared organization mailbox sits behind them. Connecting a mailbox grants read access to everything in it, so connect a functional AR or billing mailbox rather than a personal inbox.

​

Communication

Communication connectors move a result out of DualEntry and in front of people, whether that is a close update posted to a channel or a transactional email sent to a customer. Anything that writes stays disabled until someone with the integrations permission allows it, and a tool that is allowed runs without a confirmation step, so treat customer-facing tools as a deliberate decision rather than a default.

​

Files

File connectors reach the document stores where support for a transaction usually sits, so a contract or a signed statement can be located without switching tools. They complement OCR document upload, which is how a document becomes a draft bill or expense: the connector finds the file, and OCR reads one you hand to DualEntry directly.

​

CRM

The CRM connector ties a customer record in DualEntry to the commercial history behind it, such as the deal that produced a contract or the owner to chase on a disputed invoice. It is a read of the sales system during a conversation, separate from a billing integration, so nothing syncs between HubSpot and your customer list as a result of connecting it.

​

Productivity and project management

These connectors cover the notes, wikis, and trackers a finance team keeps alongside the ledger: the memo that explains an accrual, the policy that sets a threshold, and the tickets that carry close work. Pulling that context into a conversation is what lets Accounting Intelligence answer with your own documented reasoning rather than a generic one. DualEntry keeps its own close checklist, so a tracker connector reaches the board your wider team works in rather than replacing it. Nothing syncs in either direction on its own: a task read from Asana or Jira stays there unless you act on it.

​

Developer

Developer connectors matter to teams running DualEntry alongside their own systems, typically for tracing an integration failure that shows up as missing or duplicated data. They are aimed at the engineers who maintain those systems rather than at the accounting team, and they pair with the DualEntry API when the fault is on your side of the integration.

​

What each connector requires

Connectors differ in what they ask of you before the first tool call, and the difference is worth checking before you promise a workflow to anyone. Most connect with nothing but the provider’s consent screen, because DualEntry registers an OAuth client with the provider automatically. Several connectors instead need an OAuth client that belongs to your organization rather than to DualEntry. The five Google connectors, Asana, and Box are the current cases, and the client has to exist in the provider’s console before anyone authorizes. SendGrid is different again: it authenticates with a static API key you supply, and its tools are DualEntry-built wrappers over the SendGrid API rather than a vendor-hosted MCP server. Credentials are always personal. Installation is an organization-level action, but every user authorizes their own account, so a connector a colleague installed does nothing for you until you connect it yourself.

​

Related reading

• How to Connect an MCP Connector
• How Accounting Intelligence Works
• Agents Panel Reference
• Scheduled Agents Reference
• How to Send Dunning Emails with Accounting Intelligence and Gmail
• DualEntry MCP