Integrations
Connect your AI tools to AI Accounting using the Model Context Protocol (MCP) or plain REST. One API key gives an agent the full accounting toolset — create accounts and contacts, post and reverse journal entries, pull reports, and close periods — the same operations a human does in the dashboard.
What you get
AI Accounting's MCP server is available over Streamable HTTP at:
https://ai-accounting-software.vercel.app/mcpIt exposes the accounting engine as MCP tools (see the full MCP tools reference). Any MCP-capable client can connect with an API key. Prefer raw HTTP? Every tool also has a REST equivalent — see REST for any agent.
Get an API key
All access — REST and MCP — is authenticated with a Bearer API key. Generate one
in the dashboard under API keys; it looks like ak_…. Keep it secret (see
Security).
Auth is an API key, not OAuth
AI Accounting's MCP server authenticates with your ak_… API key sent as an
Authorization: Bearer header — there's no OAuth sign-in flow. Each client
below shows how to attach that header.
Supported clients
- Claude Code
- Claude Desktop & claude.ai
- Codex CLI
- Cursor
- VS Code (Copilot)
- Windsurf
- Any agent over REST
Most MCP clients follow one of two patterns: a CLI command to add an HTTP server
with a header, or a JSON config block with url + headers. The per-client
pages give exact, copy-paste steps.
Setup steps vary by client version
MCP support is evolving quickly. If a client's UI differs from what's shown
here, check that client's own MCP documentation for the latest steps — the
endpoint URL and the Authorization: Bearer ak_… header stay the same.