DualEntry
by DualEntry
Search records, trace audit trails and post journal entries to a DualEntry general ledger from your AI assistant. 15 tools, 4 of which write to the ledger the moment they are called. OAuth 2.1 sign-in, permissions inherited from your DualEntry role.
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.
Connect DualEntry via MCP
https://api.dualentry.com/mcpWorks in any MCP-compatible client. In Agentman Studio it is one click — no config file to edit.
Use in Agentman
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 StudioDualEntry Tools & Capabilities (15)
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_contractorcreate_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_scheduleandpreview_fixed_asset_scheduleexist; there is no equivalent forsave_recordorsave_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_recordreturns is the display number shown on the entry, and that passing the returnedrecord_numbertoget_record_by_numbercan resolve a different record entirely. - No published MCP rate limit. DualEntry's rate-limiting reference covers the Public API (
/public/v1/,/public/v2/) authenticated withX-API-KEY, documenting a 50-request aggregate burst refilling at 5/second and a 10-request per-endpoint burst refilling at 1/second, withX-RateLimit-Limitheaders and aRetry-Afteron 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
inputSchemaand noreadOnlyHintfor 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
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).
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).
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).
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).
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).
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).
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).
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
- DualEntry MCP developer overview (fetched 2026-09-08 as Markdown via the host's
.mdaffordance; 201 words, and it is an index page that links to the four richer guides below) · retrieved 2026-09-08 - DualEntry MCP server reference: tools, permissions and troubleshooting (fetched 2026-09-08; the 15-tool catalogue, the permission table and the troubleshooting tables) · retrieved 2026-09-08
- DualEntry Claude connector directory guide (fetched 2026-09-08; plan requirements, Owner approval, and the warning naming the four write tools) · retrieved 2026-09-08
- DualEntry MCP client quickstart (fetched 2026-09-08; per-client configuration for Cursor, Claude, Claude Code, VS Code and Codex) · retrieved 2026-09-08
- DualEntry period-end accrual worked example (fetched 2026-09-08; the immediate-posting warning, identifier behaviour and error table) · retrieved 2026-09-08
- DualEntry audit trail and compliance (fetched 2026-09-08; append-only trail, actor attribution, SOC 2 Type II statement) · retrieved 2026-09-08
- DualEntry post and reverse month-end accruals (fetched 2026-09-08; Create Reverse, the intercompany exception, and the no-delete rule) · retrieved 2026-09-08
- DualEntry idempotency and write validation (fetched 2026-09-08; Public API only, cited here to mark what the MCP surface does *not* document) · retrieved 2026-09-08
- DualEntry Public API rate limiting (fetched 2026-09-08; Public API only) · retrieved 2026-09-08
- DualEntry documentation machine index (fetched 2026-09-08). The host's
robots.txtcarriesContent-Signal: ai-train=yes, search=yes, ai-input=yes— synthesis into AI-generated output is expressly permitted by the publisher. · retrieved 2026-09-08 - Live OAuth posture check against
https://api.dualentry.com/mcp— anonymousinitializereturned HTTP 401 with aWWW-Authenticate: Bearerchallenge; the RFC 9728 descriptor at/.well-known/oauth-protected-resource/mcpand the authorization server metadata were both read (2026-09-08). An invented path under the same prefix returned 404, confirming the descriptor is not a pattern echo. No credentials were supplied and no tool was called. · retrieved 2026-09-08 - Anthropic Connectors Directory entry (fetched 2026-09-08; the 15 tool names and the partner tier) · retrieved 2026-09-08
Server Info
- Category
- Finance
- Developer
- DualEntry
- Tools
- 15
- Domain
- api.dualentry.com
Using Claude Desktop or another MCP client? Setup docs — the connection URL above works anywhere.
Similar MCP Servers for Finance
Related Resources
Ready to connect DualEntry?
Connect DualEntry once and your agents call these tools on their own — on a schedule, in a workflow, with nobody at the keyboard.