The Payhawk MCP connects your Payhawk account to your AI Assistant, so you can ask about your live Payhawk data and act on it in the AI Assistant you already use, such as Claude, ChatGPT, or Cursor, using your own login and permissions.
Before you start
To connect the Payhawk MCP, you need:
An active Payhawk account. Sign in with the same credentials you use for the Payhawk Web Portal.
The Payhawk MCP server URL (https://mcp.payhawk.com/mcp, also available in the following sections).
Each person signs in with their own Payhawk login, so everyone keeps their own Payhawk permissions. You stay signed in while you use the connection. You need to sign in again after 7 days without use, and every 30 days at most.
Supported AI assistants
The following table lists the AI Assistants Payhawk MCP supports:
AI Assistant | Made by | Good to know |
|---|---|---|
Anthropic | Web, desktop and mobile apps. Listed in the Claude connector directory. On a Team or Enterprise plan, a Claude Owner has to enable Payhawk first. | |
Anthropic | Set up in a terminal. | |
OpenAI | Listed in the ChatGPT plugin directory, on every plan including Free. | |
OpenAI | Set up in a terminal. To use the Codex desktop app, follow the ChatGPT steps. UI components show as text. | |
Anysphere | Set up in your | |
GitHub | ||
GitHub | Set up from the Command Palette. | |
Microsoft | ||
Microsoft | A Microsoft 365 administrator has to approve the Payhawk agent. | |
Langdock | ||
Notion | ||
Dust |
Payhawk accepts sign-ins only from the AI Assistants in the table. In any other app, the sign-in fails with an error that mentions
host-not-allowedor “The client redirect URI is not allowed.” To request support for another app, contact Payhawk Support at support@payhawk.com.
Connecting to Claude
Claude supports the Payhawk MCP on the web, in the desktop app, and in the mobile app.
You can connect Payhawk from the Claude connector directory:
Click Add to Claude and follow the prompts to connect.
Sign in with the credentials you use for the Payhawk Web Portal and approve the connection.
If you use Claude on a Team or Enterprise plan, a Claude Owner must enable the connector first. Each person then connects with their own Payhawk login and keeps their own Payhawk permissions.
You can also add Payhawk as a custom connector, with the Payhawk MCP server URL.
First, check whether you can add connectors yourself.
Custom connectors work on every Claude plan (Free, Pro, Max, Team, and Enterprise; Free allows one), so the plan is rarely the blocker.
On a personal Free, Pro, or Max account, you can add Payhawk yourself.
On a Team or Enterprise workspace, only a Claude Owner can add a custom connector, so ask yours to add Payhawk once and then connect to it individually. Being a Payhawk Administrator makes no difference here; this is a Claude permission, not a Payhawk one.
If you add it yourself (Free, Pro, Max):
In the Claude desktop app, go to Settings > Connectors.
Click Add custom connector.
Enter a name, for example Payhawk, and the Payhawk MCP server URL https://mcp.payhawk.com/mcp.
Leave the options Claude marks as Detected: Sign in now under Authentication and Register automatically under OAuth client.
Sign in with your Payhawk credentials when prompted.
You can also add Payhawk from the Claude mobile app, on the same screen.
If your Claude Owner adds it (Team, Enterprise):
The Owner goes to Organization settings > Connectors, clicks Add, hovers Custom, and picks Web.
The Owner pastes the https://mcp.payhawk.com/mcp Payhawk MCP server URL and clicks Add.
Everyone else goes to Settings > Connectors, finds Payhawk, clicks Connect, and signs in with their own Payhawk login. Each person signs in as themselves, so everyone keeps their own Payhawk permissions.
Payhawk now appears in your Claude tools.
Connecting to Claude Code
To connect Payhawk to Claude Code:
In a terminal, run
claude mcp add --transport http payhawk https://mcp.payhawk.com/mcp. To make Payhawk available in all your projects instead of only the current one, add--scope user.Start Claude Code and type
/mcp.Select payhawk and follow the steps in your browser to sign in with your Payhawk login.
You can also sign in from the terminal with claude mcp login payhawk, and sign out with claude mcp logout payhawk.
Non-interactive runs (claude -p) can’t complete the sign-in, so sign in once from an interactive session first. If you remove the server with claude mcp remove payhawk, your saved sign-in is removed too.
Connecting to ChatGPT
You can connect Payhawk from the ChatGPT plugin directory, also on the Free plan:
Follow the prompts to install Payhawk and connect your account.
Sign in with the credentials you use for the Payhawk Web Portal and approve the connection.
Once connected, you can ask ChatGPT about your Payhawk data and take actions within your Payhawk permissions.
You can also add Payhawk in the ChatGPT desktop app with the Payhawk MCP server URL:
In the ChatGPT desktop app, go to Settings > Plugins > Add > Add MCP server.
Enter a name, for example Payhawk.
Choose Streamable HTTP and paste the Payhawk MCP server URL https://mcp.payhawk.com/mcp.
Sign in with your Payhawk credentials when prompted.
Connecting to Codex
The Codex desktop app is now part of the ChatGPT desktop app. To use Payhawk there, follow the steps for ChatGPT. To connect Payhawk to the Codex CLI (the command-line tool):
In a terminal, run
codex mcp add payhawk --url https://mcp.payhawk.com/mcp.Run
codex mcp login payhawk.Sign in with your Payhawk credentials in the browser window that opens.
UI components, such as flight or approval widgets, don’t render in Codex. You get the answer as text.
Connecting to Cursor
To connect Payhawk to Cursor:
In Cursor, go to Customize > MCPs > New MCP Server. Cursor opens your
mcp.jsonfile.Add Payhawk inside
"mcpServers", as in the following example. If the file already lists other servers, add a comma after the previous entry.{ "mcpServers": { "payhawk": { "url": "https://mcp.payhawk.com/mcp" } } }Save the file and go back to Customize > MCPs.
Under Needs Attention, click Authenticate next to Payhawk and sign in with your Payhawk credentials.
Payhawk now appears under Connected.
Connecting to the GitHub Copilot app
To connect Payhawk to the GitHub Copilot app:
In the GitHub Copilot app, go to Customize > Installed.
Next to MCP Servers, click Add server > Add custom server.
In Server name, enter a name, for example payhawk.
In Server type, choose HTTP.
In URL, paste the Payhawk MCP server URL https://mcp.payhawk.com/mcp.
Leave Headers, OAuth Client ID, and Timeout empty, and click Add server.
Sign in with your Payhawk credentials when prompted.
Connecting to GitHub Copilot in VS Code
To connect Payhawk to GitHub Copilot in VS Code:
In VS Code, open the Command Palette (
Cmd+Shift+Pon Mac,Ctrl+Shift+Pon Windows) and run MCP: Add Server.Choose HTTP.
Paste the Payhawk MCP server URL https://mcp.payhawk.com/mcp.
Enter a name, for example Payhawk Customer MCP.
Choose Global or Workspace.
VS Code adds Payhawk to your mcp-config.json file, as in the following example:
{
"mcpServers": {
"Payhawk Customer MCP": {
"type": "http",
"url": "https://mcp.payhawk.com/mcp",
"tools": ["*"]
}
}
}Connecting to Microsoft Copilot Studio
To connect Payhawk to Microsoft Copilot Studio:
In Copilot Studio, go to Tools and click New tool.
Select Model Context Protocol.
Fill in the required fields: a name in Server name, for example Payhawk MCP, a description in Server description, and the Payhawk MCP server URL https://mcp.payhawk.com/mcp in Server URL.
In Authentication, choose OAuth 2.0, and in Type, choose Dynamic discovery.
Click Create.
Payhawk now appears in your list of tools.
Connecting to Microsoft 365 Copilot
Microsoft 365 Copilot has no option to add a connector. Instead, you package Payhawk as an agent in VS Code and publish it to your organization.
What you need
To publish Payhawk to Microsoft 365 Copilot, you need:
A Microsoft 365 work account. Personal Microsoft accounts don’t work.
A Microsoft 365 Global Administrator or Teams Administrator for the approval steps.
Visual Studio Code with the Microsoft 365 Agents Toolkit extension, version 6.12.0 or later.
Allowing custom apps (once, by an administrator)
In the Teams admin center:
Go to Teams apps > Setup policies > Global (Org-wide default), turn on Upload custom apps, and click Save.
Go to Teams apps > Manage apps > Actions > Org-wide app settings, turn on Let users interact with custom apps in preview, and click Save.
The changes can take up to 24 hours to apply.
Creating the agent in VS Code
To create the Payhawk agent:
In VS Code, click the Microsoft 365 Agents Toolkit icon in the left bar.
Click Create a New Agent/App > Declarative Agent > Add an Action > Start with an MCP Server.
For the server URL, enter https://mcp.payhawk.com/mcp.
For the authentication, select OAuth (with dynamic registration).
Choose a folder for the project and name the agent, for example Payhawk.
In the new VS Code window, click Trust. If you missed the prompt, click Restricted Mode in the status bar, and then click Trust.
Setting the name and description
Set a real name and description for the agent. If you skip this step, users see placeholder text and a “dev” suffix on the name.
In
appPackage/manifest.json, replace the placeholder values ofdeveloper.name,name.full,description.short, anddescription.full.In
appPackage/declarativeAgent.json, replacedescription.Create the file
env/.env.prodwith the following content:
TEAMSFX_ENV=prod
APP_NAME_SUFFIX=Publishing the agent
To send the agent to your administrator for approval:
In the Lifecycle pane, click Provision and choose prod.
Click Publish and choose prod.
Approving the agent (by an administrator)
In the Microsoft 365 admin center:
Go to Agents > All agents > Requests.
Open the Payhawk agent and click Publish to store.
Under Select users or groups who can install the agent, choose All users or specific groups. You can also choose who gets the agent pre-installed in their sidebar.
Accept the default security policy, review the permissions, and click Publish.
If the security policy step keeps loading, approve the agent in the Teams admin center instead: go to Teams apps > Manage apps, find the Payhawk agent, and publish or allow it.
Users then open Payhawk under Agents in the Copilot sidebar. The first time they ask something, they click Sign in, sign in with their Payhawk credentials, and approve the access.
Connecting to Langdock
To connect Payhawk to Langdock:
In Langdock, go to Integrations > Create > Integration.
Select Connect remote MCP.
In Server URL, paste the Payhawk MCP server URL https://mcp.payhawk.com/mcp.
In Authentication method, choose OAuth 2.0 (Dynamic Client Registration).
Sign in with your Payhawk credentials when prompted.
Connecting to Notion
To connect Payhawk to Notion:
In Notion, go to Settings > Connections.
Click + Add connection > Custom MCP connection.
In MCP server URL, enter the Payhawk MCP server URL https://mcp.payhawk.com/mcp, and in Name, enter a name, for example Payhawk.
In Authentication, choose OAuth.
Click Connect. Notion shows a notice that it hasn’t reviewed this server, which is expected for custom servers.
When Notion takes you to Payhawk, sign in with your Payhawk credentials.
Connecting to Dust
To connect Payhawk to Dust:
In Dust, go to Spaces > Tools and click Add tools.
Click Add MCP server.
In URL, paste the Payhawk MCP server URL https://mcp.payhawk.com/mcp.
Leave Authentication set to Automatic and click Save.
Payhawk now appears in your list of tools.
After you connect Payhawk to your AI Assistant
Once you are connected, you can ask about expenses, invoices, card transactions, suppliers, and budgets, and you can also ask your AI Assistant to take actions, such as recoding expenses, approving items, freezing cards, and creating requests. Every change shows a preview first and waits for your explicit confirmation.
For more hands-on information, see the article about getting the best out of the Payhawk MCP.