MCP Integration
Learn how to connect to Merge Agent Handler via MCP.
This section explains how your agent connects to Merge Agent Handler tools via MCP.
Prerequisites
- Tool Pack ID: ID of the tool pack you wish to expose to your user at the time of session. This ID can be retrieved within the dashboard or via API using the GET /tool-packs call.
- Registered User ID: ID of the user who will be interacting with your agent at the time of session. This ID can be retrieved within the dashboard or via API when first creating a Registered User.
- Production Access Key: Your Merge Agent Handler API Key used to authenticate requests.
If you are using a Test Registered User, you must also use a test production access key. If you are using a Production Registered User, you must use a production access key.
MCP Entry URL
The MCP Entry URL is a combination of Tool Pack ID and Registered User ID, and looks like this:
Implementation of Merge Agent Handler MCP Server
Config File
Many applications like Claude Desktop, Cursor, or Windsurf support MCP servers out of the box and will handle the connection to Merge Agent Handler.
Implement using MCP’s Python SDK
For MCP Client builders, the following code snippet can be used to connect to Merge Agent Handler.