PEX MCP Server

PEX MCP Server

A Model Context Protocol (MCP) server that provides access to the PEX Card External API. Use this server to let AI assistants like Claude interact with your PEX business account, cards, transactions, and more.

Installation

npx @pexcard_engineering/mcp

Or install globally:

npm install -g @pexcard_engineering/mcp
pex-mcp-server

Getting Your PEX API Token

To use the PEX MCP Server, you need a PEX API token. Follow these steps to generate one:

1. Log in to the PEX Dashboard using your credentials.
2. Navigate to Profile > Authorized Apps (or go directly to /account/authorized-apps).
3. Find the PEX MCP Server application and click on it.
4. Click Generate Token and copy the token value.

Note: Keep your API token secure. Do not commit it to version control or share it publicly.

Configuration

Set the following environment variables:

Usage with Claude Desktop

Add to your claude_desktop_config.json:

{
  "mcpServers": {
    "pex": {
      "command": "npx",
      "args": ["-y", "@pexcard_engineering/mcp"],
      "env": {
        "PEX_API_URL": "https://coreapi.pexcard.com/v4",
        "PEX_API_TOKEN": "your-api-token-here"
      }
    }
  }
}

Config file locations

• macOS: ~/Library/Application Support/Claude/claude_desktop_config.json
• Windows: %APPDATA%\Claude\claude_desktop_config.json

Usage with Claude Code (CLI)

Add the MCP server using the Claude Code CLI:

claude mcp add pex -e PEX_API_URL=https://coreapi.pexcard.com/v4 -e PEX_API_TOKEN=your-api-token-here -- npx -y @pexcard_engineering/mcp

Or add it manually to your .claude/settings.json:

{
  "mcpServers": {
    "pex": {
      "command": "npx",
      "args": ["-y", "@pexcard_engineering/mcp"],
      "env": {
        "PEX_API_URL": "https://coreapi.pexcard.com/v4",
        "PEX_API_TOKEN": "your-api-token-here"
      }
    }
  }
}

Usage with GitHub Copilot

VS Code

Add the following to your VS Code settings (.vscode/settings.json or user settings):

{
  "github.copilot.chat.mcpServers": {
    "pex": {
      "command": "npx",
      "args": ["-y", "@pexcard_engineering/mcp"],
      "env": {
        "PEX_API_URL": "https://coreapi.pexcard.com/v4",
        "PEX_API_TOKEN": "your-api-token-here"
      }
    }
  }
}

Alternatively, create an .mcp.json file in your project root:

{
  "servers": {
    "pex": {
      "command": "npx",
      "args": ["-y", "@pexcard_engineering/mcp"],
      "env": {
        "PEX_API_URL": "https://coreapi.pexcard.com/v4",
        "PEX_API_TOKEN": "your-api-token-here"
      }
    }
  }
}

Tip: When using .mcp.json, add it to your .gitignore if it contains your actual token, or use environment variable references to keep secrets out of source control.

Available Tools (72 total)

Business (12 tools)

Cards (7 tools)

Transactions (10 tools)

Account Details (10 tools)

Spending Rulesets (7 tools)

Bills (4 tools)

Vendors (3 tools)

Payments (3 tools)

Credit & Invoices (4 tools)

Groups (2 tools)

Tokens (6 tools)

Callbacks (3 tools)

Partner (1 tool)

Features

• Full API Coverage: 72 tools covering all GET endpoints of the PEX External API
• Input Validation: All parameters validated with clear error messages
• Retry Logic: Automatic retries with exponential backoff on 502/503/504 errors
• Request Timeout: 30-second timeout prevents hanging requests
• Structured Logging: JSON logs to stderr for debugging (stdout reserved for MCP)
• Rich Documentation: All tool parameters include descriptions, valid values, and constraints

Example Queries

Once connected, you can ask Claude things like:

• "What's my business account balance?"
• "Show me all transactions from last week over $100"
• "List all cards with their spending limits"
• "What are the spending rules for card 12345?"
• "Show me pending payments"

License

MIT