Connect an AI assistant
Let Claude, Cursor or VS Code work in AlphaCount through the Model Context Protocol.
AlphaCount's MCP server gives an AI assistant two things: tools to read the books directly, and AlphaCount's own agent for everything that changes them — the agent that books, invoices and files tax returns in the app, with the same approvals.
The server speaks Streamable HTTP at https://mcp.alphacount.ai/mcp.
Which assistants
| Assistant | How it signs in |
|---|---|
| Claude Code | API key |
| Cursor | API key |
| VS Code (GitHub Copilot) | API key |
| claude.ai, Claude Desktop, ChatGPT | sign-in with OAuth — coming next |
Assistants that connect from a website or an app store need a sign-in in the browser instead of a key. Until that is there, use one of the first three.
Create a key
In AlphaCount: Integrations → Connect AI assistants (MCP) → New access.
- Permissions: Read only lets the assistant look; Read and write lets it ask the agent to act — booking, reversing and other significant changes still wait for your approval. Choose individually for scopes.
- Legal entities: all you can reach, or a selection. The key never sees more than you do, and loses a company the moment you do.
- Valid for: no expiry, or a number of days.
The key is shown once. The dialog shows the configuration with the key already in it.
Connect
claude mcp add --transport http alphacount https://mcp.alphacount.ai/mcp \
--header "Authorization: Bearer ab_..."First steps
If the key reaches more than one company, the assistant calls list_entities and select_entity first; the
selection holds for the session. Then try:
- "Which invoices are overdue, and by how much?"
- "Show me the documents that need review this month."
- "Book the open Hetzner invoices like last month." — the agent prepares it and asks before it books.
- "What does AlphaCount let you do with this key?" — the assistant calls
alphacount_capabilities.
How the assistant is kept in bounds: Security and approvals. Every tool: Tools.