Authorize.net MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| AUTHNET_ENVIRONMENT | No | The Authorize.net environment (sandbox or production) | sandbox |
| AUTHNET_API_LOGIN_ID | Yes | Your Authorize.net API Login ID | |
| AUTHNET_TRANSACTION_KEY | Yes | Your Authorize.net Transaction Key |
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_settled_batch_listB | Get a list of settled batches within a date range. Returns batch IDs, settlement dates, and statistics. |
| get_transaction_listC | Get all transactions within a specific settled batch. |
| get_unsettled_transaction_listB | Get all transactions that are pending settlement (not yet batched). |
| get_customer_profile_transaction_listB | Get all transactions for a specific customer profile ID. |
| get_transaction_detailsC | Get full details for a specific transaction by its transaction ID. |
| get_batch_statisticsC | Get aggregate statistics for a specific batch (totals, counts by card type, etc.). |
| get_merchant_detailsB | Get merchant account information including name, gateway ID, and processors. |
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 7 tools
Each tool has a clearly distinct purpose targeting specific resources: batch statistics, customer profile transactions, merchant details, settled batch lists, transaction details, batch-specific transaction lists, and unsettled transactions. No overlap exists, and the descriptions clearly differentiate the scope and target of each tool.
All tool names follow a consistent verb_noun pattern with 'get_' as the prefix, followed by descriptive nouns (e.g., get_batch_statistics, get_customer_profile_transaction_list). The naming is uniform, predictable, and enhances readability across the toolset.
With 7 tools, the server is well-scoped for payment processing and reporting tasks. Each tool serves a specific, necessary function in the Authorize.net domain, avoiding bloat while covering key operations like batch management, transaction retrieval, and merchant information.
The toolset provides comprehensive read-only coverage for transaction and batch reporting, including settled and unsettled data, customer profiles, and merchant details. A minor gap exists in write operations (e.g., creating or updating transactions), but the surface is complete for querying and analysis workflows.