> ## Documentation Index
> Fetch the complete documentation index at: https://docs.dualentry.com/llms.txt
> Use this file to discover all available pages before exploring further.

# MCP Connector Directory

> Every third-party MCP connector available to Accounting Intelligence, grouped by category, each linking to that provider's own MCP documentation.

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](https://app.dualentry.com/home/accounting-intelligence/connectors) 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](./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](./connect-an-mcp-connector#add-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.

<CardGroup cols={2}>
  <Card title="Cryptoworth" icon="https://cdn.dualentry.com/integration-logos/cryptoworth.png" href="https://developer.cryptoworth.com/docs/getting-started">
    Crypto subledger: portfolio value, realized and unrealized gains and losses, cost basis, DeFi positions, and wallet reconciliation status.
  </Card>
</CardGroup>

## 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](../core-financials/bank-connections), which is what actually feeds transactions into Bank Match. A banking connector answers questions about the account; it does not import anything.

<CardGroup cols={2}>
  <Card title="Mercury" icon="https://cdn.dualentry.com/integration-logos/mercury.png" href="https://docs.mercury.com/docs/what-is-mercury-mcp">
    Read-only access to Mercury balances, transactions, cards, recipients, and statements.
  </Card>
</CardGroup>

## 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.

<CardGroup cols={2}>
  <Card title="Stripe" icon="https://cdn.dualentry.com/integration-logos/stripe.png" href="https://docs.stripe.com/mcp">
    Stripe payments, customers, subscriptions, and invoices.
  </Card>

  <Card title="Ramp" icon="https://cdn.dualentry.com/integration-logos/ramp.png" href="https://support.ramp.com/ramp-mcp">
    Ramp expenses, cards, reimbursements, and transactions.
  </Card>

  <Card title="Brex" icon="https://cdn.dualentry.com/integration-logos/brex.png" href="https://developer.brex.com/docs/mcp">
    Brex expenses, card transactions, and user data.
  </Card>

  <Card title="PayPal" icon="https://cdn.dualentry.com/integration-logos/paypal.png" href="https://developer.paypal.com/ai-tools/mcp-server">
    PayPal payments, invoices, subscriptions, and disputes.
  </Card>

  <Card title="Square" icon="https://cdn.dualentry.com/integration-logos/square.png" href="https://developer.squareup.com/docs/mcp">
    Square payments, orders, customers, and catalog data.
  </Card>
</CardGroup>

## 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.

<CardGroup cols={2}>
  <Card title="Gmail" icon="https://cdn.dualentry.com/integration-logos/google-gmail.png" href="https://developers.google.com/workspace/guides/configure-mcp-servers">
    Read, search, and draft Gmail messages. Requires a Google Cloud OAuth client your organization owns.
  </Card>

  <Card title="Google Calendar" icon="https://cdn.dualentry.com/integration-logos/google-calendar.png" href="https://developers.google.com/workspace/guides/configure-mcp-servers">
    Read and update Google Calendar events. Requires a Google Cloud OAuth client your organization owns.
  </Card>
</CardGroup>

## 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.

<CardGroup cols={2}>
  <Card title="Slack" icon="https://cdn.dualentry.com/integration-logos/slack.png" href="https://docs.slack.dev/ai/slack-mcp-server/">
    Search Slack messages, list channels, and post as the connecting user.
  </Card>

  <Card title="Google Chat" icon="https://cdn.dualentry.com/integration-logos/google-chat.png" href="https://developers.google.com/workspace/guides/configure-mcp-servers">
    Read and post Google Chat messages. Requires a Google Cloud OAuth client your organization owns.
  </Card>

  <Card title="Intercom" icon="https://cdn.dualentry.com/integration-logos/intercom.png" href="https://developers.intercom.com/docs/guides/mcp">
    Search Intercom conversations, contacts, and help center articles.
  </Card>

  <Card title="SendGrid" icon="https://cdn.dualentry.com/integration-logos/sendgrid.png" href="https://www.twilio.com/docs/sendgrid">
    Send transactional email, search recent activity, and check delivery status. Authenticates with a SendGrid API key rather than OAuth.
  </Card>
</CardGroup>

## 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](./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.

<CardGroup cols={2}>
  <Card title="Google Drive" icon="https://cdn.dualentry.com/integration-logos/google-drive.png" href="https://developers.google.com/workspace/guides/configure-mcp-servers">
    Browse, read, and update Google Drive files. Requires a Google Cloud OAuth client your organization owns.
  </Card>

  <Card title="Box" icon="https://cdn.dualentry.com/integration-logos/box.png" href="https://developer.box.com/guides/box-mcp/setup">
    Browse, read, and update Box files and folders. Requires a Box OAuth app your organization owns.
  </Card>

  <Card title="Dropbox" icon="https://cdn.dualentry.com/integration-logos/dropbox.png" href="https://help.dropbox.com/integrations/connect-dropbox-mcp-server">
    Browse, search, and read Dropbox files.
  </Card>
</CardGroup>

## 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.

<CardGroup cols={2}>
  <Card title="HubSpot" icon="https://cdn.dualentry.com/integration-logos/hubspot.png" href="https://developers.hubspot.com/docs/apps/developer-platform/build-apps/integrate-with-the-remote-hubspot-mcp-server">
    HubSpot CRM contacts, companies, deals, and tickets.
  </Card>
</CardGroup>

## 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](../core-financials/close-management/month-end-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.

<CardGroup cols={2}>
  <Card title="Notion" icon="https://cdn.dualentry.com/integration-logos/notion.png" href="https://developers.notion.com/guides/mcp/overview">
    Read and write Notion pages, databases, and comments.
  </Card>

  <Card title="Linear" icon="https://cdn.dualentry.com/integration-logos/linear.png" href="https://linear.app/docs/mcp">
    Browse and update Linear issues, projects, and cycles.
  </Card>

  <Card title="Asana" icon="https://cdn.dualentry.com/integration-logos/asana.png" href="https://developers.asana.com/docs/mcp-server">
    Asana projects, tasks, and teams. Requires an Asana OAuth app your organization owns.
  </Card>

  <Card title="Atlassian" icon="https://cdn.dualentry.com/integration-logos/atlassian.png" href="https://www.atlassian.com/platform/rovo-mcp">
    Search and edit Jira issues and Confluence pages through Atlassian's Rovo MCP server.
  </Card>

  <Card title="Google Contacts" icon="https://cdn.dualentry.com/integration-logos/google-people.png" href="https://developers.google.com/workspace/guides/configure-mcp-servers">
    Read and update Google Contacts. Requires a Google Cloud OAuth client your organization owns.
  </Card>
</CardGroup>

## 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](../../developers/guides/index) when the fault is on your side of the integration.

<CardGroup cols={2}>
  <Card title="GitHub" icon="https://cdn.dualentry.com/integration-logos/github.png" href="https://github.com/github/github-mcp-server">
    GitHub repositories, issues, pull requests, and Actions.
  </Card>

  <Card title="Sentry" icon="https://cdn.dualentry.com/integration-logos/sentry.png" href="https://mcp.sentry.dev/">
    Sentry errors, issues, and performance data.
  </Card>

  <Card title="Cloudflare" icon="https://cdn.dualentry.com/integration-logos/cloudflare.png" href="https://developers.cloudflare.com/agents/model-context-protocol/">
    Cloudflare zones, DNS, Workers, R2, and analytics.
  </Card>
</CardGroup>

## 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](./connect-an-mcp-connector)
* [How Accounting Intelligence Works](./ai-accounting-intelligence)
* [Agents Panel Reference](./agents-panel)
* [Scheduled Agents Reference](./scheduled-agents)
* [How to Send Dunning Emails with Accounting Intelligence and Gmail](./send-dunning-emails-with-copilot-and-gmail)
* [DualEntry MCP](./mcp/index)