Skip to main content
Glama
jaakla

Merit MCP

by jaakla
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to Merit MCP

  • e-arveldaja MCP Server

    iseppo
    A
    license
    C
    quality
    A
    maintenance
    Enables interaction with the Estonian e-arveldaja (RIK e-Financials) REST API to manage financial records like invoices and journal entries using natural language. It supports automating purchase invoice entry from PDFs, reconciling bank transactions, and generating financial reports.
    130
    966 npm
    35
    Apache 2.0

Related Servers

  • merit-aktiva-mcp

    werkstatt-jasper
    A
    license
    B
    quality
    B
    maintenance
    Enables read-only access to Merit Aktiva accounting data, including customers, vendors, sales invoices, accounts, payments, and taxes, through natural language MCP tools.
    77
    MIT

  • merit-aktiva-mcp

    roosa-dev
    A
    license
    Not graded
    quality
    B
    maintenance
    Exposes ~60 tools for the Merit Aktiva accounting API, covering sales/purchase invoices, payments, customers, vendors, items, general ledger, offers, reference data, and reports with both read and write operations.
    12 npm
    MIT

  • Exact Online

    iwebdevnl
    A
    license
    Not graded
    quality
    B
    maintenance
    Hosted MCP server for Exact Online. Ask questions, pull reports, and prepare bookings you approve first.
    MIT

  • Eqvitta Accounting MCP Server

    Eqvitta
    A
    license
    A
    quality
    B
    maintenance
    Connects Claude Desktop, Claude Code, and other MCP-compatible clients to cloud accounting and GST billing records, enabling GST-compliant invoice creation, ledger and voucher management, balance queries, and real-time financial reporting through natural language with role-based tenant isolation.
    22
    24 npm
    MIT
Deploy Server
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

A3.5/5.0

Scored across 11 tools

Disambiguation4/5

Read tools are cleanly partitioned by domain (financial, inventory, master_data, purchases, reports, sales) with little overlap, and the preview/confirm write pairs are clearly distinguished by the _confirm suffix. Only minor conceptual overlap exists between merit_read_financial and merit_read_reports, which both surface monetary data.

Naming Consistency4/5

Names follow a strong merit_read_<domain> / merit_write_<domain> / merit_write_<domain>_confirm pattern throughout. The lone outlier is get_setup_instructions, which breaks both the merit_ prefix and the verb-noun domain convention.

Tool Count5/5

Eleven tools is well-scoped for an ERP surface, and reads are sensibly aggregated into multi-action domain tools (each carrying many sub-actions) rather than exploding into dozens of endpoints. Every tool earns its place.

Completeness3/5

Read coverage is broad across financials, inventory, master data, purchases, reports, and sales. However write operations are limited to customer upsert and sales invoice creation, with no vendor/purchase-order/item writes, no update/delete for existing records, and manual handling of delivery and credit notes leaving notable gaps.

Maintenance

ActivityMaintained
ResponsivenessUnresponsive

Resources