Skip to main content
DualEntry is in Anthropic’s connector directory. Search for it, sign in, and Claude is connected to your ledger. No URLs to paste, no config files to edit. This is the recommended path for anyone using Claude on the web, desktop, or mobile. If you are connecting Cursor, VS Code, Codex, or another client, use the configuration blocks in Quickstart: DualEntry MCP Server instead.

​
Before you start

Two accounts have to be in place before the connection works: a Claude plan that allows connectors, and a DualEntry login with the access you expect Claude to have. Connectors require a Claude Pro, Max, Team, or Enterprise plan. Free plans cannot add them from the directory or anywhere else. You also need your normal DualEntry credentials. There is no API key to create and nothing to request from DualEntry: you sign in through the same browser flow you use for the dashboard. Your MCP access mirrors your DualEntry role, company access, and subscriptions. If you cannot see a record type in the dashboard, Claude cannot see it either, and a tool that needs a permission you do not hold returns a Missing permission: message rather than the data.
On a Claude Team or Enterprise plan, an Owner or Primary Owner has to add DualEntry for the organization before it appears for members, and each member then authenticates individually. Start with Get the connector approved on a Team or Enterprise plan if that is your situation, because the directory search returns nothing useful until that step is done. Anthropic documents the organization side in Authorize MCP connectors for your entire organization.

​
Connect from the connector directory

Adding DualEntry from the directory takes about a minute and ends with a browser sign-in. These steps are the same on Claude for web, desktop, and mobile.
  1. Open Claude and go to Customize > Connectors. The older Settings > Connectors entry point redirects here.
  2. Choose Add, then Browse connectors.
  3. Search the directory for DualEntry and select the verified listing, which carries the DualEntry logo and a verification badge. Custom connectors your organization added itself can appear alongside it in the results.
  4. Choose Connect. Claude opens a browser window for the DualEntry sign-in.
  5. Sign in with your DualEntry credentials and approve the access request.
  6. Return to Customize > Connectors and confirm DualEntry shows as Connected.
You can also reach the same place from inside a conversation: choose the + button, hover Connectors, and select Manage connectors. Adding the connector for your organization and connecting your own account are separate actions on Team and Enterprise plans. An Owner adds it once, and every member still signs in individually. Nobody inherits a colleague’s session, and nobody sees data their own DualEntry role does not already reach.

​
Get the connector approved on a Team or Enterprise plan

On Team and Enterprise plans, an Owner or Primary Owner adds DualEntry for the whole organization, and members connect to it afterwards. The Admin role does not carry this permission, so admins and standard members both have to ask an Owner. An Owner or Primary Owner completes the organization-level step:
  1. Go to Organization settings > Connectors.
  2. Choose Browse connectors at the bottom of the page.
  3. Select DualEntry from the directory list and choose Add to your team.
Members who do not have permission to enable connectors see a Request button on the DualEntry listing in the directory. Choosing it sends the request to the organization’s Owners, who see it under Requested by your team in Organization settings > Connectors. Once the connector is added for the organization, every member repeats Connect from the connector directory for themselves to authenticate. Organization-level approval makes the connector available; it does not grant anyone access to your ledger on its own. Enterprise Owners who want members provisioned through their identity provider instead can set up managed authorization on the connector’s Configuration tab, which controls the roles and scopes members receive. Anthropic documents both paths in Authorize MCP connectors for your entire organization and in Use connectors to extend Claude’s capabilities.

​
Confirm the connection works

A connector listed as connected is not proof that the tools are reaching the conversation, so ask Claude for live data before you rely on it. Ask a question that can only be answered from your ledger, for example:
“Show me all invoices from last month over $5,000”
A working connection returns real records from your organization. If Claude answers from general knowledge or says it has no access to DualEntry, open Customize > Connectors and check that DualEntry is connected rather than merely added. You can also ask Claude directly what it can reach: “what DualEntry tools do you have?” returns the tool list it can see in that conversation. An empty answer points at the connection rather than at your permissions, because a connected account always exposes at least the read tools your role allows. An access denied response means something different from a broken connection. It means the tool reached DualEntry and your role was refused, which is a permissions question for your DualEntry administrator rather than a setup problem. The permissions table lists which permission each tool checks.

​
What Claude can do once connected

The connector exposes 15 tools covering record lookup, entity search, record creation, revenue recognition, fixed assets, and bank match suggestions. Every one of them runs under your own DualEntry role. The MCP integration reference lists every tool by name with the permission it checks. For a worked example that ends in a posted journal entry, see how to post a period-end accrual from Claude.
The tools that write are not previews. save_record, save_entity, create_contract, and create_fixed_asset commit as soon as Claude calls them, with no draft stage and no confirmation prompt. Ask Claude to show you the figures before you tell it to post, and use preview_contract_schedule or preview_fixed_asset_schedule when you want to see a schedule without creating anything.

​
Connect a client other than Claude

The directory is a Claude feature. Cursor, VS Code, Codex, and other MCP clients connect to the same server by configuration, and they reach the same tools with the same permissions. Use the per-client configuration blocks in Quickstart: DualEntry MCP Server. Every client points at https://api.dualentry.com/mcp/ over Streamable HTTP and signs in through the same OAuth browser flow, so the only difference is where the URL goes. Claude Code is the exception among Claude clients. It reads the same server but is configured from the terminal with claude mcp add --transport http dualentry https://api.dualentry.com/mcp/, and it opens the browser sign-in the first time you use a DualEntry tool. The manual path also applies to Claude itself when the directory is not an option, such as an Enterprise organization that blocks directory connectors but allows a custom one. In that case an Owner adds https://api.dualentry.com/mcp/ as a custom connector, and members connect to it exactly as they would to the directory listing.

​
Troubleshooting

Most failures at this stage are plan or approval problems rather than connection problems. The table below maps what you see to what to do about it.
Last modified on September 3, 2026