Payhawk Developer API and hosted MCP

Payhawk is automatable today through the Developer API and a Payhawk-hosted MCP server. API keys are created under Settings, Integrations, with full or read-only scope, and are sent as Authorization Bearer or X-Payhawk-ApiKey. The help center documents v3 paths for expenses, users, teams, custom fields, fund-account bank statements, and webhook subscriptions, a limit of 15 requests per second, and webhook signature checks with the RSA public key at https://api.payhawk.io/api/v2/rsa-public-key. Creating per diem or mileage expenses is not supported, and there is no bulk user endpoint. The MCP server is https://mcp.payhawk.com/mcp. The user signs in with a Payhawk login. Reads and confirmed writes can recode expenses, approve items, freeze cards, and create purchase orders. The overview, updated 2026-09-15, says the MCP never starts a payment or a transfer, and card numbers are limited to the last four digits. The connecting article, updated 2026-09-25, says the connector is not yet in the Claude or ChatGPT directories. Connector catalogs, an SDK, and a CLI were not established on the pages opened. Computer-use viability is unassessed. API and MCP both score 7. API is the best path because scoped keys and webhooks support unattended jobs without a per-action confirmation, while the MCP cannot move money.

Best path today: api · Overall automatability: 7/10