01
MCP
Connect compatible agents
Use the MCP server and published tool definitions to give compatible clients access to accounting capabilities.
Explore MCPAccountsOS / API & MCP
Your agents.
Your workflows.
Connected to the books.
Give your software access to accounting tools and structured financial data. Connect through MCP, call the API over HTTP, or work from the command line.
AccountsOS / Tool interface
POST /api/mcp
{
"type": "tool",
"name": "get_transactions",
"arguments": {
"limit": 10
}
}Your agentYour company’s books
Example request. Company data requires an authorised API key.
MCP / HTTP / CLIBuild with AccountsOS
01 / One accounting foundation
Work where you work.
Connect to the same books.
AccountsOS exposes tools for accounting data and actions. Choose the connection that fits your agent, application or internal workflow.
02
HTTP API
Call from your own software
Send JSON tool requests to the accounting endpoint. Authenticate company requests with a Bearer API key.
Explore HTTP API03
Command line
Work from the terminal
Use the AccountsOS CLI for terminal workflows and scripts. Follow the setup guide to install and authenticate.
Explore Command line02 / Start with a request
A tool name.
A clear set of arguments.
Discover the available tools, then call the ones your workflow needs. These examples show public discovery and authenticated reading of company transactions.
Request explorer / curl
curl https://accounts-os.com/api/mcpPublic tool discovery. No API key required. This page does not run requests.
Start with an API key
Create a key in Settings for the relevant company. Use read access for reporting workflows. Keep the full key in your environment or secret store.
Manage API keysAccess stays with the company
Key validation establishes the company context and scopes. Revoked or expired keys are rejected, and tools check the required access scope.
Writes wait for the owner
A write from a new key is held, and the call returns 202 with status held_for_approval. The owner approves or rejects it in Settings, and nothing changes in the books until then. An owner can set a key they trust, such as an automation, to write directly. Every call is logged either way.
03 / Accounting capabilities
Useful data.
Meaningful actions.
The published tool catalogue describes available arguments. Build around the tools you need and the permissions you intend to grant.
94
Published MCP tools
Explore the current catalogue for transactions, documents, reporting and supported accounting actions.
4
Published MCP resources
Discover the resources exposed by the server alongside its tool interface.
Your own workflows
Use structured accounting data in custom reports, internal dashboards or agent workflows. Review available tool schemas before implementing.
04 / Built to be discovered
Find the interface.
Read the contract.
Tool catalogue Public server information and tool schemas.MCP manifest Machine-readable connection and capability information.Agent instructions Request formats and accounting tool examples.Setup guides Connection instructions for MCP clients, HTTP and the CLI.Agent connections Explore the ways agents can work with AccountsOS.Security & access Understand company boundaries and credential controls.
05 / Connection details
Before you connect.
Do I need an account to explore the API?
Public server and tool discovery do not require a key. Reading or changing company records requires an authorised API key with the relevant scope.
Does every AI connection have the same permissions?
No. Capabilities depend on the connection and its permissions. The dedicated Finn ChatGPT app is read-only. API key integrations can have read or write access. Review your chosen connection’s setup instructions.
Where are the existing client setup instructions?
They are available in the setup guide, including Claude Desktop, Claude Code and CLI instructions.
AccountsOS / Connected accounting