E Arveldaja MCP logo

E Arveldaja MCP

Connect AI assistants to Estonia’s e-arveldaja accounting API for client, product, credential, and journal management.

Install E Arveldaja MCP

Pick your client, then add it in one click or paste the config.

STDIONode.js
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "e-arveldaja-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "e-arveldaja-mcp"
      ],
      "env": {
        "EARVELDAJA_SERVER": "YOUR_VALUE_HERE",
        "EARVELDAJA_EXPOSE_GRANULAR_TOOLS": "YOUR_VALUE_HERE"
      }
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

Values are written into the snippet above so you can paste it as is. They never leave your browser.

Install not yet sandbox-tested— the server itself is confirmed live (we called its tools/list endpoint). The stdio install command is a separate, ongoing check.

Overview

e-arveldaja-mcp connects AI assistants to the Estonian e-arveldaja (RIK e-Financials) REST API. It supports credential setup, connection management, client and product records, journal entries, caching, and audit logs, including create, update, deactivate, and delete operations. Reach for it when an agent needs to inspect or maintain accounting data through e-arveldaja, with preview-first handling for credential imports and destructive credential actions. The package is experimental and interacts with live financial records, so operations should be verified and tested against the demo server first.

Use cases

  • Manage e-arveldaja clients and suppliers
  • Maintain products and services
  • Create and inspect journal entries
  • Switch accounting connections
  • Review credential and mutation audit logs

Key features

  • Estonian e-arveldaja REST API access
  • Preview-first credential import and removal
  • Client and product lifecycle management
  • Journal listing, retrieval, and creation
  • Connection switching and cache clearing
  • Mutation audit-log management

Tools130

What E Arveldaja MCP lets your agent do. Expand a tool for its parameters.

Verified live~26.5k tokens of context

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked 3d ago

Recent health check succeeded.

7/7 checks healthy over the last 55d

What it can do

From the 130 tools this server returned when we ran it; 130 declare their own safety hints.

Runs commands · 7Can delete or modify data · 30Handles credentials · 5Makes network requests · 22Read-only tools · 98
Unusual tool instructions. 3 tool descriptions contain text aimed at the AI model rather than at you (reaches for local secrets). Read the tool descriptions before connecting.
Network at startup3 connections
Files written at startupNone
Install scriptsNone
npm provenanceSigned build
Package age212 days
Maintainers1

Observed 2026-10-15 in an isolated sandbox. A description of reach, not a security audit.

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 11d ago via OSV.dev · e-arveldaja-mcp (npm)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

GitHub stars39Stargazers on the source repository.
npm downloads5.5kPackage downloads in the last 30 days.
Last commit6d agoMost recent push to the default branch.
Tools exposed130Callable tools this server registers over MCP.
Directory activity3 viewsConfig copies, upvotes, and views on AllMCPs.

How E Arveldaja MCP works

What e-arveldaja-mcp does

e-arveldaja-mcp exposes accounting operations from the Estonian e-arveldaja (RIK e-Financials) REST API through MCP. Its tools cover connection and credential administration, client and product master data, journal entries, cached reference data, and operation logs.

The server can list, inspect, create, update, deactivate, reactivate, and delete clients and products. It can also list journals, retrieve a journal with its postings, and create a journal entry with postings. Deletion is guarded by accounting-record references: clients or products used by invoices, journals, transactions, or other records cannot be permanently removed and should generally be deactivated instead.

How it works

Credentials are supplied through e-arveldaja API key files. The service uses the configured connections and tracks an active connection index. list_connections shows those connections, while switch_connection changes the active one and clears caches. Cached API and reference data can also be cleared explicitly after changes made in the e-arveldaja web interface.

Several administrative actions use a preview-then-execute flow. Importing an apikey*.txt file first returns a plan handle and a projected target; persistence requires a second call with execute=true and that handle. Removing a stored credential follows the same pattern. This provides an opportunity to review local or global .env changes before writing them.

The server also records mutating-operation activity in Markdown audit logs. Logs can be listed, retrieved for the current connection or another label, and cleared. Clearing the current session log is destructive and cannot be undone.

Setup and configuration

Install the package through an MCP client using npx. For Claude Code, the setup command is:

Terminal
claude mcp add e-arveldaja -- npx -y e-arveldaja-mcp

Other clients can add an equivalent MCP entry that launches npx -y e-arveldaja-mcp. The package supports Claude Code, Codex CLI, Gemini CLI, Cursor, Windsurf, Cline, and other MCP clients.

To obtain credentials, create an access token in e-arveldaja under Settings → General settings → Add new access token, configure the allowed public IP address, download apikey.txt, and place it in the working directory used by the assistant. A changing public IP can cause 401 Unauthorized responses when it no longer matches the token’s allowlist. The credential file should never be committed to source control.

Set EARVELDAJA_SERVER=demo to use the demo server. Set EARVELDAJA_EXPOSE_GRANULAR_TOOLS=1 to register additional focused workflow tools that are hidden by default.

Tools and capabilities

  • Inspect server status, active tool profile, release notices, stored credentials, and configured connections.
  • Import or remove credential blocks with reviewable execution plans.
  • Switch connections and clear API or reference-data caches.
  • List, search, identify, create, update, deactivate, reactivate, and delete clients.
  • List, retrieve, create, update, deactivate, reactivate, and delete products or services.
  • List journals, retrieve postings, and create journal entries.
  • Read, list, and clear mutating-operation audit logs.

Limitations and notes

This is an unofficial experimental project that works with live financial data. It can create, modify, confirm, or delete accounting records, so users remain responsible for checking every operation. Testing on the e-arveldaja demo server is recommended before production use. The project is not affiliated with or endorsed by RIK or e-arveldaja, and it provides no warranty against data loss or incorrect bookings.

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about E Arveldaja MCP

e-arveldaja-mcp is an MCP server that connects AI assistants to Estonia’s e-arveldaja (RIK e-Financials) REST API. Its main tools manage API credentials and connections, clients, products or services, journal entries, caches, and audit logs, including operations to create, update, deactivate, reactivate, and inspect accounting records.

Install it with npx through your MCP client. In Claude Code, run `claude mcp add e-arveldaja -- npx -y e-arveldaja-mcp`; other clients can add an equivalent MCP configuration that launches the package with npx.

Place the downloaded `apikey.txt` file in the working directory used by the assistant, or use the credential import tool to preview and persist `apikey*.txt` credentials into a local or global `.env` file. Configure the token’s allowed public IP in e-arveldaja first.

Yes, e-arveldaja-mcp works with Cursor. Add it to Cursor’s MCP configuration using an entry that launches `npx -y e-arveldaja-mcp`, then provide the e-arveldaja API credentials.

Set `EARVELDAJA_SERVER=demo` before launching the server. The demo setting directs the package to the e-arveldaja demo environment, which is recommended for testing before using live financial data.

Related MCP servers

Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewE Arveldaja MCP AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/e-arveldaja-mcp?style=directory)](https://allmcps.com/mcp/e-arveldaja-mcp)
HTML Embed
<a href="https://allmcps.com/mcp/e-arveldaja-mcp"><img src="https://allmcps.com/api/badge/e-arveldaja-mcp?style=directory" alt="E Arveldaja MCP on AllMCPs" /></a>