Skip to main content
Glama
Sign In
acumulus-mcp

acumulus-mcp

by NickAldewereld
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to acumulus-mcp

No user-submitted related servers found.

    Related Servers

    • bort

      Mobiss11
      F
      license
      B
      quality
      B
      maintenance
      Enables an AI assistant to read and manage a local project-management database over stdio: listing and creating projects, tasks, expenses, chats and people, and pulling money, margin, deadline and overdue summaries. It runs on the same service layer and SQLite file as the bundled web UI, so figures shown to the assistant and to the human always agree.
      14
      -

    • Exact Online MCP Server

      landje80
      F
      license
      Not graded
      quality
      C
      maintenance
      Enables connecting AI assistants to Exact Online through its official REST API with OAuth2 authentication and automatic token refresh. Provides curated tools for reading and, optionally, writing common accounting entities such as accounts, contacts, items, journal entries and sales/purchase invoices, plus generic GET/POST/PUT/DELETE tools for any other endpoint, over local stdio or hosted HTTP transports.
      1
      -
    • @klappay/mcp

      @klappay/mcpofficial

      klappay
      A
      license
      Not graded
      quality
      A
      maintenance
      Lets an AI assistant run locally over stdio to inspect and test the Klap Core API — looking up charges and timelines, listing webhooks and deliveries, checking accepted token/network pairs, querying metrics, and, in test mode, creating charges, re-checking them on-chain, retrying deliveries and driving sandbox payments. Live environments are read-only unless writes are explicitly opted into, and money-moving or endpoint-management operations are never exposed.
      215 npm
      MIT

    • Octopus MCP Server

      JulieMorozov
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables AI assistants to inspect, query, and diagnose issues within an Octopus instance, and to create releases, deploy them to environments and tenants, and run runbooks. Connects via stdio with API key or short-lived token auth, offering selectable toolsets, a read-only mode, and a structured REST backstop.
      453 npm
      MIT

    • milltime

      ehellman
      F
      license
      Not graded
      quality
      C
      maintenance
      Enables AI assistants to read and write Milltime time reports, expenses and travel allowances over stdio, with every write previewed and confirmed by token before anything is sent. Uses the login saved by the CLI, so the assistant never sees the password.
      446 npm
      -

    • iLEAP MCP

      bernard357
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI assistants to query product footprints, inspect transport activity data, and submit events from iLEAP-conformant endpoints through natural language, using MCP tools over Streamable-HTTP or stdio.
      1
      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.7/5.0

    Scored across 4 tools

    Disambiguation3/5

    whoami and list_picklist with picklist="accounts" perform essentially the same call, creating genuine redundancy. acumulus_request also overlaps with every dedicated tool by design, though its description explicitly steers usage toward uncovered endpoints, which mitigates the fuzziness.

    Naming Consistency3/5

    create_invoice and list_picklist follow a clean verb_noun pattern, but whoami is a bare verb-less word and acumulus_request is a namespaced prefix_noun, so the set mixes three conventions. Still readable but not predictable.

    Tool Count4/5

    Four tools is on the thin side, but for an API wrapper the generic acumulus_request plus two focused helpers and a connection check is defensible. whoami is arguably redundant given list_picklist, keeping it just shy of ideal.

    Completeness4/5

    acumulus_request makes any Acumulus endpoint reachable, so there are no true dead ends. However dedicated coverage is sparse — invoice creation exists but no dedicated get/update/delete invoice or payment-status tools, leaving common lifecycle operations to the generic escape hatch.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues

    Resources