Skip to main content
Glama
borgels

mcp-server-corpayone

by borgels

Related Servers

Alternatives to mcp-server-corpayone

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables secure expense claim management with tools for listing, submitting, approving, and refunding expenses. It layers ThunderID scopes, runtime policy decisions, and application rules to authorize each call, with a full audit trail.
      MIT
    • F
      license
      A
      quality
      B
      maintenance
      Enables an AI agent to handle accounts payable tasks against a mock ERP, including reading and writing bills and vendors, checking duplicates, matching invoices, recommending approvals, and queuing payment releases, with configurable profiles that limit available tools.
      11
      -
    • A
      license
      B
      quality
      C
      maintenance
      Enables MCP clients to read Fortnox invoices and customers, validate receipts, and optionally perform approved write operations with strict safety controls.
      3
      MIT
    • F
      license
      A
      quality
      B
      maintenance
      Enables AI agents to use corporate card and expense functions, including balance checks, transaction listing, receipt compliance, expense reporting, and approval workflows, by calling existing REST APIs through a governed gateway with identity, policy, and audit controls.
      8
      -
    • A
      license
      A
      quality
      D
      maintenance
      Enables MCP-capable agents to read Fintaro invoices and transactions, and upload receipts, via a scoped API key with PII-safe projections.
      6
      Apache 2.0

    TDQS

    A3.8/5.0

    Scored across 8 tools

    Disambiguation5/5

    Each tool has a distinct purpose: connection check, generic endpoint call, committing prepared writes, listing expenses/webhooks, preparing expense coding or webhook changes, and searching capabilities. Descriptions clearly differentiate them, with no overlapping functionality that would cause confusion.

    Naming Consistency5/5

    All tools follow a consistent 'corpay_verb_noun' pattern using snake_case, such as 'corpay_list_expenses' and 'corpay_prepare_webhook_change'. Verbs are descriptive and uniform, making the tool set predictable and easy to navigate.

    Tool Count5/5

    With 8 tools, the server is well-scoped for its purpose of interacting with the Corpay One API. Each tool covers a necessary function (authentication, listing, preparing, committing, searching) without unnecessary bloat or gaps.

    Completeness4/5

    The tool set covers core workflows including listing, preparing, and committing operations. However, direct 'get' operations for individual expenses or webhook subscriptions are missing, requiring use of the generic endpoint call tool. This minor gap prevents full CRUD coverage.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues