Skip to main content
Glama
Swandive-Inc

makeleaps-mcp

Official
by Swandive-Inc
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to makeleaps-mcp

No user-submitted related servers found.

    Related Servers

    • invoiceninja-mcp

      ambaloo
      A
      license
      B
      quality
      D
      maintenance
      MCP server for Invoice Ninja v5 API. Enables AI assistants to manage clients, invoices, quotes, payments, and time tracking through natural language.
      32
      20 npm
      2
      MIT

    • toconline-mcp

      themiguelamador
      A
      license
      B
      quality
      C
      maintenance
      Local MCP server for TOCOnline accounting/invoicing API that enables AI assistants to manage customers, products, sales documents, and call arbitrary endpoints via natural language after OAuth login.
      67
      1
      MIT

    • FreeAgent MCP Server

      StupidCodeFactory
      A
      license
      Not graded
      quality
      C
      maintenance
      MCP server for the FreeAgent accounting API, enabling LLMs to securely access and manage accounting data including contacts, invoices, bills, bank transactions, and more.
      5 npm
      1
      MIT

    • Frappe Assistant Core

      buildswithpaul
      A
      license
      Not graded
      quality
      A
      maintenance
      MCP server that enables LLMs to interact with ERPNext/Frappe sites for document CRUD, search, reports, workflows, and analytics, respecting user permissions and logging all actions.
      315
      AGPL 3.0

    • MCP Moloni ON

      rubencodex86
      F
      license
      Not graded
      quality
      D
      maintenance
      MCP server that exposes the Moloni ON GraphQL API to AI clients, providing a curated set of operations as typed and documented tools.
      -
    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

    A4/5.0

    Scored across 8 tools

    Disambiguation5/5

    Each tool targets a distinct resource and action: clients vs documents, search/get/create are clearly separated. There is no ambiguity between e.g. search_documents and get_document or create_quote and create_invoice.

    Naming Consistency5/5

    All tools follow the verb_noun pattern with consistent snake_case style (search_, get_, create_, list_). Even the longer create_organization_client fits the convention, and there are no mixed naming styles.

    Tool Count5/5

    With 8 tools covering clients and documents (quotes/invoices), the set is well-scoped and each tool has a clear purpose. It sits comfortably in the ideal 3-15 range.

    Completeness4/5

    The tool surface covers core workflows: search/get/create for clients, and search/get/create plus template listing for documents. Minor gaps exist, such as no update/delete operations and no creation of individual (non-organization) clients, but agents can work around these.

    Maintenance

    ActivityStale
    ResponsivenessNo issues

    Resources