DualEntry

Search records, trace audit trails and post journal entries to a DualEntry ledger.

Add to Agentman Studio

Opens Agent Studio, where connecting is one click. The connector URL below works in any MCP client.

Paste it into any MCP client. Setup docs

Resources

What the DualEntry connector does

The DualEntry MCP server connects a DualEntry general ledger to Claude, ChatGPT and any MCP-compatible agent. Eleven of its 15 tools read — searching records, tracing audit history, matching bank lines — and four write, creating journal entries, bills, entities, revenue recognition contracts and fixed assets. Writes commit immediately. Sign-in is OAuth 2.1 through DualEntry's own login.

Verified connector

Listed by Anthropic as a partner connector in its Connectors Directory.

Connection checked by Agentman on .

Anthropic states this reflects the level of review a connector received, not a security audit.

DualEntry tools (15)

  • create_contract
  • create_fixed_asset
  • get_contract_detail
  • get_record_by_number
  • get_record_detail
  • get_record_history
  • get_related_records
  • list_bank_match_suggestions
  • list_companies
  • preview_contract_schedule
  • preview_fixed_asset_schedule
  • save_entity
  • save_record
  • search_entities
  • search_records

Tool names from Anthropic's directory listing. This server requires sign-in, so we could not read tool descriptions or parameter schemas.

Limits

  • Writes commit immediately, and there is no undo in the connector. DualEntry documents no draft stage, no preview and no confirmation prompt on save_record, save_entity, create_contract or create_fixed_asset. Its own troubleshooting entry for "Claude posted before you were ready" is to reverse the entry in DualEntry and add "do not post yet" to future prompts.
  • Nothing in the surface edits, voids or deletes. All four write tools create. There is no tool to correct a bad post — correction is a dashboard action.
  • The dry run covers two tools, not four. preview_contract_schedule and preview_fixed_asset_schedule exist; there is no equivalent for save_record or save_entity.
  • Permissions are a hard ceiling, and gate per type. DualEntry checks per record type and per entity type, so the same tool can succeed for one type and fail for another. A failed check returns a message beginning Missing permission: and writes nothing.
  • Subscriptions are a second gate. Revenue recognition and some record types require the corresponding subscription enabled for the organization, which returns a subscription error rather than a permission one. DualEntry directs that to your account team.
  • Locked periods reject postings. A posting date in a closed period fails.
  • Records are indexed for search asynchronously, so an entry posted seconds ago may not be findable by number yet, and a number search during that window can return a different record. DualEntry advises reading back by ID instead.
  • Identifiers do not line up the way you would expect. DualEntry documents that neither value save_record returns is the display number shown on the entry, and that passing the returned record_number to get_record_by_number can resolve a different record entirely.
  • No published MCP rate limit. DualEntry's rate-limiting reference covers the Public API (/public/v1/, /public/v2/) authenticated with X-API-KEY, documenting a 50-request aggregate burst refilling at 5/second and a 10-request per-endpoint burst refilling at 1/second, with X-RateLimit-Limit headers and a Retry-After on a 429. That page does not cover the MCP server, and our unauthenticated probe returned no rate-limit headers, so no MCP quota is documented either way.
  • No parameter schemas or safety annotations here. The endpoint requires authentication, so we read no inputSchema and no readOnlyHint for any tool. Names come from Anthropic's directory listing; behaviour comes from DualEntry's published catalogue.
  • The connector does not supply accounting judgement. DualEntry's own worked example states the assistant does the arithmetic and the grouping, "not the accounting judgment". Revenue recognition and fixed assets are regulated areas; nothing on this page is accounting advice, and DualEntry's compliance statements are its own.

Frequently asked questions

Does the DualEntry MCP server post records as drafts or straight to the ledger?

Straight to the ledger. DualEntry's own documentation warns that save_record posts a real record immediately, with no draft stage, no preview and no confirmation prompt between the model deciding to call it and the entry hitting your general ledger. The same warning covers save_entity, create_contract and create_fixed_asset (DualEntry, 2026).

Can an entry an AI agent posted to DualEntry be reversed?

Yes, but not through the connector. DualEntry documents Create Reverse in the dashboard, which posts a linked offsetting entry dated on or after the original. No MCP tool reverses, edits, voids or deletes anything. DualEntry also states journal entries cannot be deleted at all, so archiving is the only retirement path (2026).

What do save_entity and save_record actually do — create, update, or both?

They create. DualEntry documents save_record as creating an accounting record and save_entity as creating an entity, and the permission table gates both on Create rather than Edit permission on the record or entity type. Neither tool is documented as updating an existing record, so treat the verb save as create-only (DualEntry, 2026).

Is preview_contract_schedule a real dry run before anything is committed?

Yes. DualEntry documents preview_contract_schedule and preview_fixed_asset_schedule as computing the schedule a payload would produce without creating anything, and states that the preview tool takes the same payload as create_contract. That makes it a genuine dry run you can run against the exact object you intend to commit (DualEntry, 2026).

Will the DualEntry connector let Claude see records I cannot see myself?

No. DualEntry states that MCP permissions match your DualEntry role, so if you cannot see something in the dashboard you cannot see it through MCP either. Checks run per record type and per entity type, and a tool you lack permission for returns a message beginning Missing permission: rather than returning the data (2026).

Do you need a paid Claude plan to add the DualEntry connector?

Yes. DualEntry documents that connectors require a Claude Pro, Max, Team or Enterprise plan, and that free plans cannot add them from the directory or as custom connectors. On Team and Enterprise plans an Owner or Primary Owner must add DualEntry for the organization first, and every member then signs in individually (2026).

Does an agent's posting show up in the DualEntry audit trail?

Yes. DualEntry documents an append-only audit trail capturing record creation, field-level before and after values, and status changes, each stamped with the actor that caused it. Neither users nor administrators can modify or delete audit events. The connector also exposes get_record_history, which returns the audit trail for a single record (2026).

Why does a DualEntry revenue recognition or fixed asset tool return a subscription error?

The feature is not enabled for your organization. DualEntry documents this as a subscription question rather than a permission one, and directs it to your account team. Permissions are not the only gate: revenue recognition and some record types need the corresponding subscription enabled before the tool returns anything (2026).

Sources

More Finance connectors

  • Affinity

    Search your CRM, prep for meetings and update deal records from your AI assistant.

  • Aiera

    Pull earnings-call transcripts, event calendars, SEC filings and company publications into your AI assistant.

  • Airwallex Developer

    Search Airwallex documentation and exercise a sandbox account from an AI agent.

Browse all MCP connectorsClaude and ChatGPT setup guideBrowse AI skills

Product names and logos belong to their owners. Agentman is not affiliated with a connector's maker unless the page says the connector is built and run by Agentman.

Use it in an agent

Put DualEntry to work.

Connect DualEntry once and your agents call these tools on their own: on a schedule, in a workflow, with nobody at the keyboard.

Open in Agentman Studio
Call (650) 285-1019Our AI receptionist answers.