Payments Gateway MCP
The Payments Gateway MCP server exposes Inyo's Gateway APIs as AI-ready tools. It handles OAuth authentication automatically, caching and refreshing tokens as needed.
Package: @inyo-global/gateway-mcp
Install
Choose your client to get started:
Cursor
Add to your Cursor MCP configuration at ~/.cursor/mcp.json:
{
"mcpServers": {
"inyo-gateway": {
"command": "npx",
"args": ["-y", "@inyo-global/gateway-mcp@latest"],
"env": {
"GATEWAY_BASE_URL": "your-gateway-url",
"GATEWAY_CLIENT_ID": "your-client-id",
"GATEWAY_CLIENT_SECRET": "your-client-secret"
}
}
}
}
Or go to Settings → MCP Servers in Cursor and add the configuration there.
VS Code
Add to .vscode/mcp.json in your project root:
{
"mcpServers": {
"inyo-gateway": {
"command": "npx",
"args": ["-y", "@inyo-global/gateway-mcp@latest"],
"env": {
"GATEWAY_BASE_URL": "your-gateway-url",
"GATEWAY_CLIENT_ID": "your-client-id",
"GATEWAY_CLIENT_SECRET": "your-client-secret"
}
}
}
}
Windsurf
Add to your Windsurf MCP configuration at ~/.windsurf/mcp.json:
{
"mcpServers": {
"inyo-gateway": {
"command": "npx",
"args": ["-y", "@inyo-global/gateway-mcp@latest"],
"env": {
"GATEWAY_BASE_URL": "your-gateway-url",
"GATEWAY_CLIENT_ID": "your-client-id",
"GATEWAY_CLIENT_SECRET": "your-client-secret"
}
}
}
}
Claude Desktop
Add to your Claude Desktop configuration:
- macOS:
~/Library/Application Support/Claude/claude_desktop_config.json - Windows:
%APPDATA%\Claude\claude_desktop_config.json
{
"mcpServers": {
"inyo-gateway": {
"command": "npx",
"args": ["-y", "@inyo-global/gateway-mcp@latest"],
"env": {
"GATEWAY_BASE_URL": "your-gateway-url",
"GATEWAY_CLIENT_ID": "your-client-id",
"GATEWAY_CLIENT_SECRET": "your-client-secret"
}
}
}
}
Restart Claude Desktop after saving the configuration.
Claude Code (CLI)
Run the following command to add the MCP server:
claude mcp add inyo-gateway \ -e GATEWAY_BASE_URL=your-gateway-url \ -e GATEWAY_CLIENT_ID=your-client-id \ -e GATEWAY_CLIENT_SECRET=your-client-secret \ -- npx -y @inyo-global/gateway-mcp@latest
Or add to .mcp.json in your project root (or ~/.claude/mcp.json globally):
{
"mcpServers": {
"inyo-gateway": {
"command": "npx",
"args": ["-y", "@inyo-global/gateway-mcp@latest"],
"env": {
"GATEWAY_BASE_URL": "your-gateway-url",
"GATEWAY_CLIENT_ID": "your-client-id",
"GATEWAY_CLIENT_SECRET": "your-client-secret"
}
}
}
}
Environment Variables
| Variable | Description |
|---|---|
GATEWAY_BASE_URL | Gateway API endpoint URL |
GATEWAY_CLIENT_ID | OAuth client identifier |
GATEWAY_CLIENT_SECRET | OAuth client secret |
Contact your Inyo account representative to obtain your credentials. For sandbox testing, use your sandbox environment URL and credentials.
Available Tools
Payment Operations
| Tool | Description |
|---|---|
create-payment | Create a new payment (PULL, PUSH, PULLPUSH, or CHECK) |
capture-payment | Capture a previously authorized payment |
void-payment | Void a payment before settlement |
refund-payment | Refund a settled payment |
Account Verification
| Tool | Description |
|---|---|
check-card-account | Verify card account details (ANI check) |
check-bank-account | Verify bank account details |
Read Operations
| Tool | Description |
|---|---|
authenticate | Manually trigger OAuth authentication |
get-payment | Retrieve payment details by ID |
Additional Services
| Tool | Description |
|---|---|
create-fx | Generate a foreign exchange quote |
create-plaid-link | Create a Plaid Link token for bank account linking |
get-plaid-link | Retrieve Plaid Link session details |
Payment Types
The create-payment tool supports multiple payment types:
| Type | Description |
|---|---|
| PULL | Pull funds from a payment source (card charge, ACH debit) |
| PUSH | Push funds to a recipient (OCT, payout) |
| PULLPUSH | Pull and push in a single operation |
| CHECK | Account verification without charging |
Supported Payment Methods
- Cards — Visa, Mastercard, credit and debit
- Bank accounts — ACH direct debit
- PIX — Brazilian instant payments
- Digital wallets — Where supported
Authentication
The MCP server handles OAuth token management automatically:
- On the first tool call, the server authenticates using your client credentials
- The access token is cached in memory
- Tokens are refreshed automatically 60 seconds before expiration
- No manual token management required
Example Usage
Once configured, you can interact with the Gateway through natural language in your AI assistant:
- "Create a $50 card payment using token tk_abc123"
- "Check the status of payment pay_xyz789"
- "Refund payment pay_xyz789 for $25"
- "Void the authorization on payment pay_abc456"
- "Verify this card account: 4111111111111111"
The AI assistant translates your request into the appropriate tool call, executes it against the Gateway API, and returns the structured response.
