

In an mcp.json file, add the configuration below, and restart Cursor.
Learn more in the official documentation ↗
1{
2 "mcpServers": {
3 "agent-handler": {
4 "url": "https://ah-api-develop.merge.dev/api/v1/tool-packs/{TOOL_PACK_ID}/registered-users/{REGISTERED_USER_ID}/mcp",
5 "headers": {
6 "Authorization": "Bearer yMt*****"
7 }
8 }
9 }
10}Open your Claude Desktop configuration file and add the server configuration below. You'll also need to restart the application for the changes to take effect.
Make sure Claude is using the Node v20+.
Learn more in the official documentation ↗
1{
2 "mcpServers": {
3 "agent-handler": {
4 "command": "npx",
5 "args": [
6 "-y",
7 "mcp-remote@latest",
8 "https://ah-api-develop.merge.dev/api/v1/tool-packs/{TOOL_PACK_ID}/registered-users/{REGISTERED_USER_ID}/mcp",
9 "--header",
10 "Authorization: Bearer ${AUTH_TOKEN}"
11 ],
12 "env": {
13 "AUTH_TOKEN": "yMt*****"
14 }
15 }
16 }
17}Open your Windsurf MCP configuration file and add the server configuration below.
Click on the refresh button in the top right of the Manage MCP server page or in the top right of the chat box in the box icon.
Learn more in the official documentation ↗
1{
2 "mcpServers": {
3 "agent-handler": {
4 "command": "npx",
5 "args": [
6 "-y",
7 "mcp-remote@latest",
8 "https://ah-api.merge.dev/api/v1/tool-packs/<tool-pack-id>/registered-users/<registered-user-id>/mcp",
9 "--header",
10 "Authorization: Bearer ${AUTH_TOKEN}"
11 ],
12 "env": {
13 "AUTH_TOKEN": "<ah-production-access-key>"
14 }
15 }
16 }
17 }In Command Palette (Cmd+Shift+P on macOS, Ctrl+Shift+P on Windows), run "MCP: Open User Configuration".
You can then add the configuration below and press "start" right under servers. Enter the auth token when prompted.
Learn more in the official documentation ↗
1{
2 "inputs": [
3 {
4 "type": "promptString",
5 "id": "agent-handler-auth",
6 "description": "Agent Handler AUTH_TOKEN", // "yMt*****" when prompt
7 "password": true
8 }
9 ],
10 "servers": {
11 "agent-handler": {
12 "type": "stdio",
13 "command": "npx",
14 "args": [
15 "-y",
16 "mcp-remote@latest",
17 "https://ah-api-develop.merge.dev/api/v1/tool-packs/{TOOL_PACK_ID}/registered-users/{REGISTERED_USER_ID}/mcp",
18 "--header",
19 "Authorization: Bearer ${input:agent-handler-auth}"
20 ]
21 }
22 }
23}It’s an MCP server that lets you access data and functionality from PayPal via tools. Your agents can use these tools to create invoices, list all recent disputes, confirm orders, and more.
PayPal offers an official MCP server here. You can also access a PayPal MCP server via a 3rd-party platform, like Merge Agent Handler.
Here are some popular options broken down by object types:
Invoices
Orders
Payments
Disputes
Here are some common use cases:
Here are a few reasons:
Yes, Merge Agent Handler includes a security gateway with data loss protection (DLP) that scans tool inputs and outputs for sensitive data. Developers can configure rules to block, redact, or mask specific data fields or types of information.
You can follow these steps:
1. Sign up for Merge Agent Handler and grab your Agent Handler API key, since your MCP client will use it as a bearer token when calling the Agent Handler MCP endpoint.
2. Create a Tool Pack for your PayPal workflow, because Tool Packs define exactly which connectors and tools your agent is allowed to use.
3. Add the PayPal connector to that Tool Pack and select only the PayPal tools you want exposed for the workflow.
4. Create a Registered User (or decide on a service account pattern), since this identity is what scopes credentials and audit logs for tool calls.
5. Authenticate PayPal for that registered user using Merge Link (or Magic Link), so PayPal tools can run with the right credentials without you handling third-party tokens directly.
6. Copy the MCP entry URL that includes your Tool Pack ID and Registered User ID, and add it to your MCP client (Cursor, Claude Desktop, VSCode, Windsurf, etc.).
7. Configure your MCP client to send <code class="blog_inline-code">Authorization: Bearer <AGENT_HANDLER_API_KEY></code> on requests to that MCP URL, then start by running <code class="blog_inline-code">list_tools</code> and a simple PayPal read call to confirm everything is wired up.
8. Validate behavior in the Playground and Logs, and tighten the Tool Pack and rules once you confirm the happy path works (especially before enabling money-moving tools like refunds or payouts).
Whether you're an engineer experimenting with agents or a product manager looking to add tools, you can get started for free now