Authentication
You don’t need an API key. You sign in with the same DualEntry credentials you use for the dashboard.- On first connection, your MCP client opens a browser for sign-in.
- Sessions refresh automatically.
- Your permissions match your DualEntry role. If you cannot see something in the dashboard, you cannot see it through MCP either.
Available tools
The server exposes 15 tools. They respect your organization’s permissions and company-level access restrictions, so a tool returns only what your role can already see in the dashboard.Finding records
search_records returns a transaction_id on every result, and that is the identifier the detail, history, and related-records tools expect.
Entities and companies
Writing records
Revenue recognition
Preview before you create.
preview_contract_schedule takes the same payload as create_contract, so you can confirm the schedule matches what you intend before committing a contract that drives recognition for its whole term.
Fixed assets
The same preview-then-create pattern applies, which matters more here than elsewhere because a depreciation schedule is tedious to correct once entries have posted against it.
Bank matching
Example conversations
Once connected, you can ask your AI assistant questions like:- “Show me all invoices from last month over $5,000”
- “Look up journal entry JE-412 and show me its line items”
- “What payments are linked to invoice IN-1089?”
- “Search for vendors matching ‘Acme’”
- “Create a bill for vendor Acme Corp, $500 for office supplies”
Permissions
Your DualEntry role governs MCP access. Every tool checks permission before it runs. The check is per record type or per entity type rather than per tool, so the same tool can succeed for one record type and fail for another.
If you lack a required permission, the tool returns a message beginning
Missing permission: and names the permission it wanted. A create tool that fails this check writes nothing.
Permissions are not the only gate. Revenue recognition and some record types also require the corresponding subscription to be enabled for your organization, which returns a subscription error rather than a permission one.
Troubleshooting
General
Cursor
Claude
Custom MCP clients
These issues apply when connecting via third-party clients that use OAuth 2.1 to authenticate with the MCP server.Related
- Connect MCP Clients: connect a client and confirm it works.
- Claude Connector Directory: Connect DualEntry: the directory path for Claude, including Owner approval on Team and Enterprise plans.
- How to Post a Period-End Accrual from Claude: a worked example that prepares an accrual in Claude and posts it with
save_record. - DualEntry Public API: the REST API behind the same accounting data.