Skip to main content
Glama
zovo-one

mcp-supplier-list

by zovo-one
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Hybrid

Related Servers

Alternatives to mcp-supplier-list

No user-submitted related servers found.

    Related Servers

    • Vendor-Accreditation MCP

      zackria
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables managing procurement vendor accreditation data through MCP tools, including listing expiring vendors, retrieving vendor records, updating accreditation statuses with audit logging, and searching vendors by name or category.
      MIT

    • PO Pilot MCP

      maskchanel14-source
      A
      license
      A
      quality
      A
      maintenance
      Enables Claude Desktop, Claude Code, Cursor, and n8n to compute stockout-adjusted replenishment plans, build vendor MOQ purchase orders with roundable carton quantities and Shopify Draft PO CSV exports, recover supplier profiles from legacy Stocky CSV snapshots, and run accounts-payable 3-way invoice matching that recovers overcharges. Runs fully locally with zero credentials in demo/CSV mode, or reads live store data through an optional read-only Shopify Admin GraphQL token.
      4
      326 npm
      MIT

    • mcp-obras

      RafaOPato
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables agents to query fictional construction works, suppliers, purchase requests, and quotes, and to create and approve purchase orders under code-enforced per-agent permissions and audit logging.
      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.4/5.0

    Scored across 10 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: add, get, list, update, remove, review, export, and license management. There is no overlap; even list vs export are differentiated by output format and purpose. Agents can reliably select the correct tool.

    Naming Consistency5/5

    All tool names follow a consistent snake_case verb_noun pattern with a domain prefix (supplier_ or license_). Actions like add, get, list, update, remove, mark_reviewed, due_review, export, activate, and status are clear and predictable.

    Tool Count5/5

    With 10 tools, the server covers the full supplier lifecycle, review workflow, export, and licensing without redundancy. The count is well-scoped for a domain-specific directory server, neither sparse nor bloated.

    Completeness5/5

    The tool surface is complete for the domain: full CRUD for suppliers (add, get, update, remove), a review cycle (mark_reviewed, due_review), export/list capabilities with filters, and license management (activate, status). No obvious gaps like missing search or bulk operations exist within the stated scope.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources