acumulus-mcp
MCP server for Acumulus — let an AI assistant (Claude Desktop, Claude Code, Cursor, …) read and modify your Acumulus administration through natural language, over the official Acumulus API.
Runs locally over stdio. Your Acumulus credentials stay on your machine; there is no telemetry and no proxy.
Install
pip install acumulus-mcp
Requires Python 3.10+.
Configure credentials
The server authenticates with your Acumulus contract code, username
and an API token (generate one in Acumulus under your profile; it travels
in the API's <password> field). Provide them as environment variables:
export ACUMULUS_CONTRACT_CODE=123456
export ACUMULUS_USERNAME=your-username
export ACUMULUS_API_TOKEN=your-api-token
# optional: validate writes without persisting them
export ACUMULUS_TESTMODE=1
Register in your MCP client
Claude Code:
claude mcp add acumulus \
-e ACUMULUS_CONTRACT_CODE=123456 \
-e ACUMULUS_USERNAME=your-username \
-e ACUMULUS_API_TOKEN=your-api-token \
-- acumulus-mcp
Claude Desktop (claude_desktop_config.json):
{
"mcpServers": {
"acumulus": {
"command": "acumulus-mcp",
"env": {
"ACUMULUS_CONTRACT_CODE": "123456",
"ACUMULUS_USERNAME": "your-username",
"ACUMULUS_API_TOKEN": "your-api-token"
}
}
}
}
Restart your client, then try: "Use the acumulus whoami tool to test the connection."
Tools
| Tool | What it does |
|---|---|
whoami |
Sanity-check the connection (lists the account picklist). |
list_picklist(picklist) |
Fetch reference data: accounts, contacts, products, vattypes, costcenters, costheadings, companytypes. |
create_invoice(customer, lines, invoice=None) |
Add an invoice (invoices/invoice_add.php). |
acumulus_request(api_path, fields=None) |
Escape hatch — call any Acumulus endpoint directly (e.g. invoices/invoice_set_payment_status.php, entry/entry_info.php). Endpoint paths match the docs at siel.nl/acumulus/API. |
The acumulus_request tool means every Acumulus function is reachable even
before it gets a dedicated wrapper — the credential/envelope is added for you;
you only pass the endpoint path and the function-specific fields.
Safety
Set ACUMULUS_TESTMODE=1 to have Acumulus validate write calls without
persisting them — do a dry run before pointing it at the live administration.
License
AGPL-3.0-or-later. For a commercial license, contact nick@easeo.nl.
Metadata
Release files for acumulus-mcp 0.1.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| acumulus_mcp-0.1.0.tar.gz | 20.9 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| acumulus_mcp-0.1.0-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 43.5 kB
Release files / acumulus_mcp-0.1.0.tar.gz
| Download URL | acumulus_mcp-0.1.0.tar.gz |
|---|---|
| Size | 20.9 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
a2205ad8b654f9a1e97fa74ed73f245746ab3064f437070a4ddbdf8ff33d5526
|
|
BLAKE2b-256 checksum How to use checksums |
f22fa4bcf5df55dc91009a561560d91e1670696e1cc3b8b69403dee60d903797
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 17, 2026.
Transparency logRelease files / acumulus_mcp-0.1.0-py3-none-any.whl
| Download URL | acumulus_mcp-0.1.0-py3-none-any.whl |
|---|---|
| Size | 22.7 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
0666533e64307629b6f4fe93a29040c5ec430a6915d1679bc2238adf9dbd9007
|
|
BLAKE2b-256 checksum How to use checksums |
3c74f59799db3261cf0f279e7b340b1728a534d77ee93953b63ee61da1a7e9d0
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 17, 2026.
Transparency log