mcp-server-corpayone
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| CORPAYONE_API_TOKEN | Yes | Your Corpay One API token (required) | |
| CORPAYONE_AUDIT_LOG | No | Absolute path to audit log file (required if writes enabled) | |
| CORPAYONE_POLICY_PATH | No | Absolute path to policy JSON file (required if writes enabled) | |
| CORPAYONE_ENABLE_WRITES | No | Set to 'true' to enable write operations (optional, default false) |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| corpay_search_capabilitiesA | Find supported tools and allowlisted endpoint operations. |
| corpay_check_connectionA | Validate OAuth credentials by acquiring an access token (does not require a teamId). |
| corpay_call_endpointC | Call a validated, allowlisted endpoint. Read-only unless write policy permits the call. |
| corpay_prepare_expense_codingA | Dry-run update of an expense’s coding — category (GL account) and labels (project, cost type, ...). Returns an operationHash to commit. Does not call Corpay One until committed. |
| corpay_prepare_webhook_changeA | Dry-run create (POST), update (PUT), or delete (DELETE) of a webhook subscription. Returns an operationHash to commit. |
| corpay_list_webhooksA | List active webhook subscriptions for the configured team. |
| corpay_commit_prepared_operationA | Execute a prepared, policy-checked write. Requires the full prepared operation, a matching confirmOperationHash, and an idempotencyKey. |
| corpay_list_expensesA | List expenses (bills/documents). Filter via query (e.g. status=pending_approval). |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 8 tools
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.
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.
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.
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.