Skip to main content
Glama
Sign In
mcp-purchase-requisition

mcp-purchase-requisition

by zovo-one
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Hybrid

Related Servers

Alternatives to mcp-purchase-requisition

No user-submitted related servers found.

    Related Servers

    • mcp-checklist

      zovo-one
      A
      license
      A
      quality
      A
      maintenance
      Enables creating reusable checklists, running dated instances of them, recording pass/fail/not-applicable results with sign-off, and producing frozen dated records for accountability.
      16
      0
      MIT

    • onboarding

      zovo-one
      A
      license
      A
      quality
      B
      maintenance
      Enables HR and managers to create role-based task templates, turn them into dated checklists per new hire, track task owners and due dates, and sign off with a preserved record.
      9
      0
      MIT

    • po-guard-mcp

      janishkumar
      A
      license
      A
      quality
      B
      maintenance
      Enables AI assistants to raise, submit, approve, amend, and cancel purchase orders and onboard suppliers in ERPNext or SAP S/4HANA while enforcing procurement controls such as duplicate detection, budget limits, split-purchase checks, price tolerances, and segregation of duties.
      14
      MIT
    • BrowserSpend Guard MCP

      BrowserSpend Guard MCPofficial

      clauxel
      F
      license
      Not graded
      quality
      D
      maintenance
      Approval receipts for AI browser purchases. Enables purchase evaluation, approval recording, budget alerts, and receipt export.
      -

    • 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/5.0

    Scored across 16 tools

    Disambiguation5/5

    Each tool targets a distinct resource and action: template creation, item management, run lifecycle, and license management are clearly separated. Even similar-sounding tools like run_show and run_report are differentiated by purpose (interactive view vs. printable text export).

    Naming Consistency4/5

    Names mostly follow a predictable resource_action pattern, such as purchase-requisition_create, run_start, and license_activate. The pattern is slightly weakened by noun-like actions like run_status and license_status, where status means "change status" in one case and "report status" in the other.

    Tool Count4/5

    At 16 tools, the set is slightly above the ideal 3-15 range but still well-scoped for the domain: 6 template tools, 8 run tools, and 2 license tools. Each tool covers a recognizable operation, so the count feels reasonable rather than bloated.

    Completeness4/5

    The core lifecycle is well covered: create/show/list/delete requisitions, add/remove items, start/check/show/list/sign off/delete runs, and license management. Missing update operations for requisition metadata and item details are notable gaps, though they can be worked around by recreating or removing and re-adding items.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources