Skip to main content
Glama
borgels

mcp-server-corpayone

by borgels
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to mcp-server-corpayone

No user-submitted related servers found.

    Related Servers

    • Payables MCP

      zeybekci-lab
      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
      -
    • fintaro-mcp by fintaro-ai

      fintaro-mcpofficial

      fintaro-ai
      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

    • jobber-mcp

      PineappleCare
      A
      license
      B
      quality
      B
      maintenance
      Enables approval-gated access to Jobber data, with read-only reporting tools and optional allowlisted write tools for records, scheduling, and communications, all requiring confirmation and auditing.
      16
      MIT

    • kingdee_star

      adambbhe
      F
      license
      A
      quality
      C
      maintenance
      Enables read-only access to Kingdee Cloud Star financial data, invoice tax calculation, and generation of reimbursement draft payloads through MCP tools.
      17
      -

    • Brex MCP Server

      dennisonbertram
      A
      license
      A
      quality
      D
      maintenance
      Enables interaction with Brex financial data including expenses, budgets, transactions, and accounts through read-only API access with support for pagination, filtering, and receipt management.
      21
      8 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

    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

    Resources