How to integrate Hookdeck MCP with Claude Agent SDK

BOOK A CALLGET STARTED FOR FREE
Framework Integration Gradient
Hookdeck Logo
Claude Agent SDK Logo
divider

Introduction

This guide walks you through connecting Hookdeck to the Claude Agent SDK using the Composio tool router. By the end, you'll have a working Hookdeck agent that can retry all failed webhook events from today, create a new source for github webhooks, bookmark this event for quick review later, cancel scheduled retries for a specific webhook through natural language commands.

This guide will help you understand how to give your Claude Agent SDK agent real control over a Hookdeck account through Composio's Hookdeck MCP server.

Before we dive in, let's take a quick look at the key ideas and tools involved.

TL;DR

Here's what you'll learn:
  • Get and set up your Claude/Anthropic and Composio API keys
  • Install the necessary dependencies
  • Initialize Composio and create a Tool Router session for Hookdeck
  • Configure an AI agent that can use Hookdeck as a tool
  • Run a live chat session where you can ask the agent to perform Hookdeck operations

What is Claude Agent SDK?

The Claude Agent SDK is Anthropic's official framework for building AI agents powered by Claude. It provides a streamlined interface for creating agents with MCP tool support and conversation management.

Key features include:

  • Native MCP Support: Built-in support for Model Context Protocol servers
  • Permission Modes: Control tool execution permissions
  • Streaming Responses: Real-time response streaming for interactive applications
  • Context Manager: Clean async context management for sessions

What is the Hookdeck MCP server, and what's possible with it?

The Hookdeck MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to your Hookdeck account. It provides structured and secure access to your webhook management platform, so your agent can perform actions like routing webhooks, managing events, configuring sources and destinations, and automating retries or cancellations on your behalf.

  • Automated event management: Let your agent bulk cancel or retry multiple webhook events, keeping your pipeline clean and efficient without manual intervention.
  • Source and destination setup: Have the agent create, configure, and manage Hookdeck sources and destinations for seamless webhook routing between services.
  • Connection orchestration: Direct your agent to establish new connections between sources and destinations, ensuring events flow exactly where you want them to go.
  • Payload transformation: Empower the agent to create custom payload transformations using JavaScript, modifying webhook data before it reaches your endpoints.
  • Bookmarking and cleanup: Ask your agent to bookmark important events for quick access or delete outdated bookmarks to keep your workspace organized.

Supported Tools & Triggers

Tools
Bulk Cancel Hookdeck EventsTool to create a bulk cancellation job for events.
Bulk Retry Hookdeck EventsTool to initiate a bulk retry for a set of events.
Cancel Hookdeck EventTool to cancel all future delivery attempts for a specific event.
Cancel Hookdeck Scheduled RetriesTool to cancel all future scheduled retries for an event.
Create Hookdeck BookmarkTool to create a new bookmark.
Create Hookdeck ConnectionTool to create a connection between a source and a destination.
Create Hookdeck DestinationTool to create a new Hookdeck destination.
Create Hookdeck SourceTool to create a new Hookdeck source.
Create Hookdeck TransformationTool to create a new Hookdeck transformation.
Delete Hookdeck BookmarkTool to delete a specific bookmark by its ID.
Delete Hookdeck ConnectionTool to delete a specific connection by its ID.
Delete Hookdeck DestinationTool to delete a specific destination by its ID.
Delete Hookdeck SourceTool to delete a specific source by its ID.
Delete Hookdeck TransformationTool to delete a specific transformation by its ID.
Get Hookdeck AttemptTool to retrieve details of a specific Hookdeck attempt by its ID.
Get attemptsTool to list delivery attempts for your Hookdeck account.
Get Hookdeck ConnectionTool to retrieve details of a specific Hookdeck connection.
Hookdeck: Get ConnectionsTool to list Hookdeck connections.
Get Hookdeck DestinationTool to retrieve details of a specific Hookdeck destination.
Hookdeck: Get DestinationsTool to list Hookdeck destinations.
Get eventsTool to list events for your Hookdeck account.
Get Hookdeck RequestTool to retrieve details of a specific Hookdeck request.
Hookdeck: Get RequestsTool to list Hookdeck requests.
Get sourcesTool to retrieve all sources associated with your Hookdeck account.
Get Hookdeck TransformationTool to retrieve details of a specific Hookdeck transformation.
Get transformationsTool to list Hookdeck transformations.
Get Hookdeck SourceTool to retrieve details of a specific Hookdeck source.
Send Hookdeck Source RequestTool to send HTTP requests to a Hookdeck Source URL.
List Hookdeck BookmarksTool to list bookmarks.
Hookdeck: List IssuesTool to list all issues detected in your Hookdeck account.
Manually Retry Hookdeck EventTool to manually retry a specific Hookdeck event delivery.
Replay Hookdeck EventTool to replay a specific Hookdeck event.
Resolve Hookdeck IssueTool to resolve a Hookdeck issue.
Retrieve Hookdeck IssueTool to retrieve details of a specific Hookdeck issue.
Trigger Hookdeck BookmarkTool to trigger a stored request via its bookmark ID.
Hookdeck Update ConnectionTool to update an existing connection.
Update Hookdeck DestinationTool to update an existing Hookdeck destination.
Hookdeck Update SourceTool to update a Hookdeck source.
Update Hookdeck TransformationTool to update an existing Hookdeck transformation.

What is the Composio tool router, and how does it fit here?

What is Tool Router?

Composio's Tool Router helps agents find the right tools for a task at runtime. You can plug in multiple toolkits (like Gmail, HubSpot, and GitHub), and the agent will identify the relevant app and action to complete multi-step workflows. This can reduce token usage and improve the reliability of tool calls. Read more here: Getting started with Tool Router

The tool router generates a secure MCP URL that your agents can access to perform actions.

How the Tool Router works

The Tool Router follows a three-phase workflow:

  1. Discovery: Searches for tools matching your task and returns relevant toolkits with their details.
  2. Authentication: Checks for active connections. If missing, creates an auth config and returns a connection URL via Auth Link.
  3. Execution: Executes the action using the authenticated connection.

Step-by-step Guide

Prerequisites

Before starting, make sure you have:
  • Composio API Key and Claude/Anthropic API Key
  • Primary know-how of Claude Agents SDK
  • A Hookdeck account
  • Some knowledge of Python

Getting API Keys for Claude/Anthropic and Composio

Claude/Anthropic API Key
  • Go to the Anthropic Console and create an API key. You'll need credits to use the models.
  • Keep the API key safe.
Composio API Key
  • Log in to the Composio dashboard.
  • Navigate to your API settings and generate a new API key.
  • Store this key securely as you'll need it for authentication.

Install dependencies

pip install composio-anthropic claude-agent-sdk python-dotenv

Install the Composio SDK and the Claude Agents SDK.

What's happening:

  • composio-anthropic provides Composio integration for Anthropic
  • claude-agent-sdk is the core agent framework
  • python-dotenv loads environment variables

Set up environment variables

bash
COMPOSIO_API_KEY=your_composio_api_key_here
USER_ID=your_user_id_here
ANTHROPIC_API_KEY=your_anthropic_api_key_here

Create a .env file in your project root.

What's happening:

  • COMPOSIO_API_KEY authenticates with Composio
  • USER_ID identifies the user for session management
  • ANTHROPIC_API_KEY authenticates with Anthropic/Claude

Import dependencies

import asyncio
from claude_agent_sdk import ClaudeSDKClient, ClaudeAgentOptions
import os
from composio import Composio
from dotenv import load_dotenv

load_dotenv()
What's happening:
  • We're importing all necessary libraries including the Claude Agent SDK and Composio
  • The load_dotenv() function loads environment variables from your .env file
  • This setup prepares the foundation for connecting Claude with Hookdeck functionality

Create a Composio instance and Tool Router session

async def chat_with_remote_mcp():
    api_key = os.getenv("COMPOSIO_API_KEY")
    if not api_key:
        raise RuntimeError("COMPOSIO_API_KEY is not set")

    composio = Composio(api_key=api_key)

    # Create Tool Router session for Hookdeck
    mcp_server = composio.create(
        user_id=os.getenv("USER_ID"),
        toolkits=["hookdeck"]
    )

    url = mcp_server.mcp.url

    if not url:
        raise ValueError("Session URL not found")
What's happening:
  • The function checks for the required COMPOSIO_API_KEY environment variable
  • We're creating a Composio instance using our API key
  • The create method creates a Tool Router session for Hookdeck
  • The returned url is the MCP server URL that your agent will use

Configure Claude Agent with MCP

# Configure remote MCP server for Claude
options = ClaudeAgentOptions(
    permission_mode="bypassPermissions",
    mcp_servers={
        "composio": {
            "type": "http",
            "url": url,
            "headers": {
                "x-api-key": os.getenv("COMPOSIO_API_KEY")
            }
        }
    },
    system_prompt="You are a helpful assistant with access to Hookdeck tools via Composio.",
    max_turns=10
)
What's happening:
  • We're configuring the Claude Agent options with the MCP server URL
  • permission_mode="bypassPermissions" allows the agent to execute operations without asking for permission each time
  • The system prompt instructs the agent that it has access to Hookdeck
  • max_turns=10 limits the conversation length to prevent excessive API usage

Create client and start chat loop

# Create client with context manager
async with ClaudeSDKClient(options=options) as client:
    print("\nChat started. Type 'exit' or 'quit' to end.\n")

    # Main chat loop
    while True:
        user_input = input("You: ").strip()
        if user_input.lower() in {"exit", "quit"}:
            print("Goodbye!")
            break

        # Send query
        await client.query(user_input)

        # Receive and print response
        print("Claude: ", end="", flush=True)
        async for message in client.receive_response():
            if hasattr(message, "content"):
                for block in message.content:
                    if hasattr(block, "text"):
                        print(block.text, end="", flush=True)
        print()
What's happening:
  • The Claude SDK client is created using the async context manager pattern
  • The agent processes each query and streams the response back in real-time
  • The chat loop continues until the user types 'exit' or 'quit'

Run the application

if __name__ == "__main__":
    asyncio.run(chat_with_remote_mcp())
What's happening:
  • This entry point runs the async chat_with_remote_mcp() function using asyncio.run()
  • The application will start, create the MCP connection, and begin the interactive chat session

Complete Code

Here's the complete code to get you started with Hookdeck and Claude Agent SDK:

import asyncio
from claude_agent_sdk import ClaudeSDKClient, ClaudeAgentOptions
import os
from composio import Composio
from dotenv import load_dotenv

load_dotenv()

async def chat_with_remote_mcp():
    api_key = os.getenv("COMPOSIO_API_KEY")
    if not api_key:
        raise RuntimeError("COMPOSIO_API_KEY is not set")

    composio = Composio(api_key=api_key)

    # Create Tool Router session for Hookdeck
    mcp_server = composio.create(
        user_id=os.getenv("USER_ID"),
        toolkits=["hookdeck"]
    )

    url = mcp_server.mcp.url

    if not url:
        raise ValueError("Session URL not found")

    # Configure remote MCP server for Claude
    options = ClaudeAgentOptions(
        permission_mode="bypassPermissions",
        mcp_servers={
            "composio": {
                "type": "http",
                "url": url,
                "headers": {
                    "x-api-key": os.getenv("COMPOSIO_API_KEY")
                }
            }
        },
        system_prompt="You are a helpful assistant with access to Hookdeck tools via Composio.",
        max_turns=10
    )

    # Create client with context manager
    async with ClaudeSDKClient(options=options) as client:
        print("\nChat started. Type 'exit' or 'quit' to end.\n")

        # Main chat loop
        while True:
            user_input = input("You: ").strip()
            if user_input.lower() in {"exit", "quit"}:
                print("Goodbye!")
                break

            # Send query
            await client.query(user_input)

            # Receive and print response
            print("Claude: ", end="", flush=True)
            async for message in client.receive_response():
                if hasattr(message, "content"):
                    for block in message.content:
                        if hasattr(block, "text"):
                            print(block.text, end="", flush=True)
            print()

if __name__ == "__main__":
    asyncio.run(chat_with_remote_mcp())

Conclusion

You've successfully built a Claude Agent SDK agent that can interact with Hookdeck through Composio's Tool Router.

Key features:

  • Native MCP support through Claude's agent framework
  • Streaming responses for real-time interaction
  • Permission bypass for smooth automated workflows
You can extend this by adding more toolkits, implementing custom business logic, or building a web interface around the agent.

How to build Hookdeck MCP Agent with another framework

OpenAI Agents SDK

OpenAI Agents SDK

Use Hookdeck MCP with OpenAI Agents SDK

Google ADK

Google ADK

Use Hookdeck MCP with Google ADK

LangChain

LangChain

Use Hookdeck MCP with LangChain

Vercel AI SDK

Vercel AI SDK

Use Hookdeck MCP with Vercel AI SDK

Mastra AI

Mastra AI

Use Hookdeck MCP with Mastra AI

LlamaIndex

LlamaIndex

Use Hookdeck MCP with LlamaIndex

CrewAI

CrewAI

Use Hookdeck MCP with CrewAI

FAQ

What are the differences in Tool Router MCP and Hookdeck MCP?

With a standalone Hookdeck MCP server, the agents and LLMs can only access a fixed set of Hookdeck tools tied to that server. However, with the Composio Tool Router, agents can dynamically load tools from Hookdeck and many other apps based on the task at hand, all through a single MCP endpoint.

Can I use Tool Router MCP with Claude Agent SDK?

Yes, you can. Claude Agent SDK fully supports MCP integration. You get structured tool calling, message history handling, and model orchestration while Tool Router takes care of discovering and serving the right Hookdeck tools.

Can I manage the permissions and scopes for Hookdeck while using Tool Router?

Yes, absolutely. You can configure which Hookdeck scopes and actions are allowed when connecting your account to Composio. You can also bring your own OAuth credentials or API configuration so you keep full control over what the agent can do.

How safe is my data with Composio Tool Router?

All sensitive data such as tokens, keys, and configuration is fully encrypted at rest and in transit. Composio is SOC 2 Type 2 compliant and follows strict security practices so your Hookdeck data and credentials are handled as safely as possible.

Used by agents from

Context
Letta
glean
HubSpot
Agent.ai
Altera
DataStax
Entelligence
Rolai
Context
Letta
glean
HubSpot
Agent.ai
Altera
DataStax
Entelligence
Rolai
Context
Letta
glean
HubSpot
Agent.ai
Altera
DataStax
Entelligence
Rolai

Never worry about agent reliability

We handle tool reliability, observability, and security so you never have to second-guess an agent action.

Book a call↗Get started for free