Skip to main content
Glama
macola-mcp

macola-mcp

by Banidan

Related Servers

Alternatives to macola-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      B
      quality
      C
      maintenance
      Enables read-only access to Epicor Kinetic ERP data, including sales orders, customers, parts, and shipments, through secure MCP tools.
      4
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      Enables querying Proluxe ERP data such as customers, orders, invoices, AR aging, bills of materials, product catalog, focus priorities, and projects through MCP tools.
      1
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      Enables AI assistants and other MCP clients to securely read SAP Business One data through the Service Layer REST API, with read-only tools for business partners, items, orders, invoices, balances, stock, and pre-approved saved queries.
      9
      MIT
    • A
      license
      B
      quality
      C
      maintenance
      Enables read-only access to a MarketSharp CRM's contacts, inquiries, appointments, jobs, notes and reference lists through 25 MCP tools backed by the MarketSharp REST API. Every tool is read-only, with no create, update or delete operations.
      25
      Apache 2.0
    • A
      license
      A
      quality
      B
      maintenance
      Enables MCP clients to search and describe API routes, retrieve people, admissions, academics, and billing records, download exports, and optionally make changes against a school information system, read-only by default.
      6
      161 npm
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables MCP-capable clients to sign in with OAuth and perform purchaser tasks such as browsing catalogues, checking inventory, managing stocktakes and recipes, drafting requisitions, updating buy lists, exporting reports, and processing invoices. It also supports supplier access for listing and inspecting connections, catalogues, products, purchase orders, invoices, and entitled reports.
      MIT

    TDQS

    C2.3/5.0

    Scored across 88 tools

    Disambiguation3/5

    Most tools target distinct resources and actions, but the large surface creates several close pairs such as locations_find/locations_get versus inventory_locations_find/inventory_locations_get, and addresses_find versus addresses_address_book. Descriptions help, but an agent must carefully distinguish many find/get pairs across similar ERP entities.

    Naming Consistency4/5

    The dominant convention is clear snake_case with an entity prefix followed by an action (addresses_find, purchase_orders_create, inventory_items_get). There are minor deviations such as singular/plural inconsistencies (purchase_orders vs purchase_order_lines, standard_routing), awkward names like addresses_address_book, and special action names like customer_orders_remove_credit_hold.

    Tool Count1/5

    With 88 tools, the server is far beyond a practical MCP tool surface and will be difficult for an agent to navigate efficiently. Although the ERP domain is broad, the set is bloated with many repetitive find/get pairs and would benefit from consolidation or resource-oriented grouping.

    Completeness3/5

    Core sales, purchasing, inventory, and contact/address workflows are broadly covered, with several resources supporting full CRUD. However, many resources are read-only or partially covered, such as inventory_items, projects, shop_floor_orders, locations, and tax codes, leaving notable lifecycle gaps.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues