Skip to main content
Glama
Endrews-DFL

protheus-mcp-server (piloto)

by Endrews-DFL
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to protheus-mcp-server (piloto)

No user-submitted related servers found.

    Related Servers

    • Olist Tiny ERP

      mcp-dir
      A
      license
      Not graded
      quality
      F
      maintenance
      Read-only MCP server for Olist Tiny ERP, enabling querying of products, inventory, orders, invoices, accounts, contacts, shipping, purchase orders, CRM, and price lists via the official REST API v3.
      MIT

    • totvs-tickets-mcp

      Guipegoraro
      A
      license
      A
      quality
      D
      maintenance
      A read-only MCP server exposing TOTVS support tickets (Portal do Cliente) as tools for LLMs in Claude Code, Claude Desktop, and Cursor.
      11
      MIT

    • TOTVS Protheus MCP

      mcp-dir
      A
      license
      Not graded
      quality
      C
      maintenance
      Connects to your own company's Protheus ERP via the official REST API, enabling read-only natural-language queries of branches, customers, products, stock, sales, orders, invoice totals, production orders, and MRP purchasing. It also maps which APIs your installation answers and can call custom REST routes, without writing to the ERP.
      MIT

    • omie-mcp

      thiagoorodrigues
      A
      license
      Not graded
      quality
      B
      maintenance
      MCP server for the Omie API to list products, consult clients, and create budgets
      16 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

    A4/5.0

    Scored across 10 tools

    Disambiguation5/5

    Each tool targets a distinct business entity or operation: customer balance, credit limit, payment conditions, various MRP entities (products, stock, warehouses, purchase requests, orders), payroll, and clients by seller. No two tools overlap in purpose; descriptions clearly differentiate them.

    Naming Consistency5/5

    All tool names follow the pattern 'protheus_<entity>_<specifier>' with underscores and consistent use of Portuguese nouns. The naming is predictable and uniform, making it easy to infer functionality from the name.

    Tool Count5/5

    With 10 tools covering financial, MRP, HR, and sales domains, the count is well-scoped for a pilot consultation server. Each tool serves a clear purpose without bloat or redundancy.

    Completeness4/5

    The tool set provides essential read-only consultations across multiple ERP modules (financial, MRP, HR, sales). Minor omissions exist, such as a general customer list or inventory movements, but given the pilot nature, coverage is adequate for common queries.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources