How to integrate DeployHQ MCP with Claude Code

Manage your DeployHQ directly from Claude Code with zero worries about OAuth hassles, API-breaking issues, or reliability and security concerns. You can do this in two different ways: Via Composio Connect - Direct and easiest approach Via Composio SDK - Programmatic approach with more control

DeployHQ logoDeployHQ
Basic

DeployHQ is a deployment automation service for Git, SVN, and Mercurial projects. It streamlines code deployments, making project launches seamless and reliable.

61 Tools

Introduction

Manage your DeployHQ directly from Claude Code with zero worries about OAuth hassles, API-breaking issues, or reliability and security concerns.

You can do this in two different ways:

  1. Via Composio Connect - Direct and easiest approach
  2. Via Composio SDK - Programmatic approach with more control

Also integrate DeployHQ with

Why use Composio?

  • Only one MCP URL to connect multiple apps with Claude Code with zero auth hassles.
  • Programmatic tool calling allows LLMs to write its code in a remote workbench to handle complex tool chaining. Reduces to-and-fro with LLMs for frequent tool calling.
  • Handling Large tool responses out of LLM context to minimize context rot.
  • Dynamic just-in-time access to 20,000 tools across 1000+ other Apps for cross-app workflows. It loads the tools you need, so LLMs aren't overwhelmed by tools you don't need.

Connecting DeployHQ to Claude Code using Composio

1. Add the Composio MCP to Claude

Terminal

2. Start Claude Code

bash
claude

3. Open your MCP list

bash
/mcp

4. Select Composio and click on Authenticate

Select Composio and click Authenticate

5. This will redirect you to the Composio OAuth page. Complete the flow by authorizing Composio and you're all set.

Composio OAuth authorization page
Composio authorization complete
Ask Claude to connect to your account and authenticate via the link

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

The DeployHQ MCP server is an implementation of the Model Context Protocol that connects your AI agent and assistants like Claude, Cursor, etc directly to your DeployHQ account. It provides structured and secure access so your agent can perform DeployHQ operations on your behalf.

Connecting DeployHQ via Composio SDK

Composio SDK is the underlying tech that powers Rube. It's a universal gateway that does everything Rube does but with much more programmatic control. You can programmatically generate an MCP URL with the app you need (here DeployHQ) for even more tool search precision. It's secure and reliable.

How the Composio SDK works

The Composio SDK 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

Step by step10 STEPS
1

Prerequisites

Before starting, make sure you have:
  • Claude Pro, Max, or API billing enabled Anthropic account
  • Composio API Key
  • A DeployHQ account
  • Basic knowledge of Python or TypeScript
2

Install Claude Code

bash
# macOS, Linux, WSL
curl -fsSL https://claude.ai/install.sh | bash

# Windows PowerShell
irm https://claude.ai/install.ps1 | iex

# Windows CMD
curl -fsSL https://claude.ai/install.cmd -o install.cmd && install.cmd && del install.cmd

To install Claude Code, use one of the following methods based on your operating system:

3

Set up Claude Code

bash
cd your-project-folder
claude

Open a terminal, go to your project folder, and start Claude Code:

  • Claude Code will open in your terminal
  • Follow the prompts to sign in with your Anthropic account
  • Complete the authentication flow
  • Once authenticated, you can start using Claude Code
Claude Code initial setup showing sign-in prompt
Claude Code terminal after successful login
4

Set up environment variables

bash
COMPOSIO_API_KEY=your_composio_api_key_here
USER_ID=your_user_id_here

Create a .env file in your project root with the following variables:

  • COMPOSIO_API_KEY authenticates with Composio (get it from Composio dashboard)
  • USER_ID identifies the user for session management (use any unique identifier)
5

Install Composio library

npm install @composio/core dotenv

Install the Composio TypeScript library to create MCP sessions.

  • @composio/core provides the core Composio functionality
  • dotenv loads environment variables from your .env file
6

Generate Composio MCP URL

import 'dotenv/config';
import { Composio } from '@composio/core';

const { COMPOSIO_API_KEY, USER_ID } = process.env;

if (!COMPOSIO_API_KEY || !USER_ID) {
  throw new Error('COMPOSIO_API_KEY and USER_ID required in .env');
}

const composioClient = new Composio({ apiKey: COMPOSIO_API_KEY });

const composioSession = await composioClient.create(USER_ID, {
  toolkits: ['deployhq'],
});

const composioMcpUrl = composioSession?.mcp.url;

console.log(`MCP URL: ${composioMcpUrl}`);
console.log(`\nUse this command to add to Claude Code:`);
console.log(`claude mcp add --transport http deployhq-composio "${composioMcpUrl}" --headers "X-API-Key:${COMPOSIO_API_KEY}"`);

Create a script to generate a Composio MCP URL for DeployHQ. This URL will be used to connect Claude Code to DeployHQ.

What's happening

  • We import the Composio client and load environment variables
  • Create a Composio instance with your API key
  • Call create() to create a Tool Router session for DeployHQ
  • The returned mcp.url is the MCP server URL that Claude Code will use
  • The script prints this URL so you can copy it
7

Run the script and copy the MCP URL

node --loader ts-node/esm generate_mcp_url.ts
# or if using tsx
tsx generate_mcp_url.ts

Run your TypeScript script to generate the MCP URL.

  • The script connects to Composio and creates a Tool Router session
  • It prints the MCP URL and the exact command you need to run
  • Copy the entire claude mcp add command from the output
8

Add DeployHQ MCP to Claude Code

bash
claude mcp add --transport http deployhq-composio "YOUR_MCP_URL_HERE" --headers "X-API-Key:YOUR_COMPOSIO_API_KEY"

# Then restart Claude Code
exit
claude

In your terminal, add the MCP server using the command from the previous step. The command format is:

  • claude mcp add registers a new MCP server with Claude Code
  • --transport http specifies that this is an HTTP-based MCP server
  • The server name (deployhq-composio) is how you'll reference it
  • The URL points to your Composio Tool Router session
  • --headers includes your Composio API key for authentication

After running the command, close the current Claude Code session and start a new one for the changes to take effect.

9

Verify the installation

bash
claude mcp list

Check that your DeployHQ MCP server is properly configured.

  • This command lists all MCP servers registered with Claude Code
  • You should see your deployhq-composio entry in the list
  • This confirms that Claude Code can now access DeployHQ tools

If everything is wired up, you should see your deployhq-composio entry listed:

Claude Code MCP list showing the toolkit MCP server
10

Authenticate DeployHQ

The first time you try to use DeployHQ tools, you'll be prompted to authenticate.

  • Claude Code will detect that you need to authenticate with DeployHQ
  • It will show you an authentication link
  • Open the link in your browser (or copy/paste it)
  • Complete the DeployHQ authorization flow
  • Return to the terminal and start using DeployHQ through Claude Code

Once authenticated, you can ask Claude Code to perform DeployHQ operations in natural language. For example:

  • "Trigger a deployment for Project X"
  • "List all deployments for Project Y"
  • "Get status of last deployment"

Complete Code

Here's the complete code to get you started with DeployHQ and Claude Code:

import 'dotenv/config';
import { Composio } from '@composio/core';

const { COMPOSIO_API_KEY, USER_ID } = process.env;

if (!COMPOSIO_API_KEY || !USER_ID) {
  throw new Error('COMPOSIO_API_KEY and USER_ID required in .env');
}

const composioClient = new Composio({ apiKey: COMPOSIO_API_KEY });

const composioSession = await composioClient.create(USER_ID, {
  toolkits: ['deployhq'],
});

const composioMcpUrl = composioSession?.mcp.url;

console.log(`MCP URL: ${composioMcpUrl}`);
console.log(`\nUse this command to add to Claude Code:`);
console.log(`claude mcp add --transport http deployhq-composio "${composioMcpUrl}" --headers "X-API-Key:${COMPOSIO_API_KEY}"`);

Conclusion

You've successfully integrated DeployHQ with Claude Code using Composio's MCP server. Now you can interact with DeployHQ directly from your terminal using natural language commands.

Key features of this setup:

  • Terminal-native experience without switching contexts
  • Natural language commands for DeployHQ operations
  • Secure authentication through Composio's managed MCP
  • Tool Router for dynamic tool discovery and execution

Next steps:

  • Try asking Claude Code to perform various DeployHQ operations
  • Add more toolkits to your Tool Router session for multi-app workflows
  • Integrate this setup into your development workflow for increased productivity

You can extend this by adding more toolkits, implementing custom workflows, or building automation scripts that leverage Claude Code's capabilities.

TOOLS

Supported Tools

Every DeployHQ action and event your agent gets out of the box.

Delete Command

Tool to delete a command from a specified project.

Delete Project

Tool to delete a project from DeployHQ.

Delete Build Cache File

Tool to delete an existing build cache file from a project.

Delete Excluded File Rule

Tool to delete an existing excluded file rule from a project.

Delete Server Group

Tool to delete a server group from a project using the DeployHQ API.

Delete Template

Tool to delete a template by its unique permalink.

Get Projects

Tool to retrieve all projects from DeployHQ account.

Get Project

Tool to view an existing project in DeployHQ.

Get Project Build Known Hosts

Tool to list all known hosts within a project using DeployHQ API.

Get Project Commands

Tool to retrieve all SSH commands configured for a project.

Get Project Config Files

Tool to retrieve a list of all config files in a DeployHQ project.

Get Project Deployments

Tool to retrieve a paginated list of all deployments in a project.

Get Project Excluded Files

Tool to list all excluded files within a project template.

Get Config File

Tool to view a specific config file in a DeployHQ project.

Get Excluded File

Tool to view a specific excluded file in a DeployHQ project.

Get Server Group

Tool to view a specific server group in a DeployHQ project.

Get Project Repository

Tool to view repository details for a specific project in DeployHQ.

Get Repository Branches

Tool to view all available branches in the connected repository for a project.

Get Repository Commit Info

Tool to view detailed information about a specific revision in a project's connected repository.

Get Latest Repository Revision

Tool to view the latest remote revision of your repository.

Get Recent Commits and Tags

Tool to view up to 15 most recent revisions and up to 15 most recent tags in a specific branch.

Get Project Scheduled Deployments

Tool to retrieve all upcoming scheduled deployments for a project.

Get Project Server Groups

Tool to retrieve all server groups configured for a project.

Get Project Servers

Tool to retrieve all servers configured for a project.

Get Templates

Tool to retrieve all templates from DeployHQ account.

Get Public Template

Tool to retrieve a specific public template from DeployHQ.

Get Public Templates

Tool to retrieve publicly available deployment templates from DeployHQ.

Update Project

Tool to update project settings in DeployHQ.

Update Build Cache File

Tool to update an existing build cache file in a project.

Update Build Command

Tool to update an existing build command in a project.

Update Language Version

Tool to update the version of a language in a project's build environment.

Update Project Command

Tool to update an existing SSH command in a project.

Update Config File

Tool to update an existing config file in a DeployHQ project.

Update Excluded File

Tool to update an existing excluded file rule in a project.

Update Project Repository

Tool to update repository configuration for a project in DeployHQ.

Update Server Group

Tool to update an existing server group in a DeployHQ project.

Update Template

Tool to update an existing template in DeployHQ.

Create Project

Tool to create a new project in DeployHQ.

Generate AI Deployment Overview

Tool to generate an AI-powered deployment overview for a revision range.

Create Build Cache File

Tool to create a new build cached file within a project.

Create Build Command

Tool to create a new build command for a project in DeployHQ.

Create Project Build Known Host

Tool to create a new known host in a project using DeployHQ API.

Create SSH Command

Tool to create a new SSH command for a project in DeployHQ.

Create Config File

Tool to create a new config file in a DeployHQ project.

Create Config File Deployment

Tool to create a new config file deployment for a project.

Create Excluded File

Tool to add a new excluded file to a project.

Abort Deployment

Tool to abort a currently running deployment.

Add Project Repository

Tool to add repository details to a project in DeployHQ.

Create Server Group

Tool to create a new server group for automated deployments in a DeployHQ project.

Create Server

Tool to create a new server configuration in a DeployHQ project.

Create Template

Tool to create a new template in DeployHQ.

Update Project Settings

Tool to update settings of an existing DeployHQ project.

Edit Build Cache File

Tool to edit an existing build cache file within a project.

Edit Build Command

Tool to edit an existing build command within a template in DeployHQ.

Edit SSH Command

Tool to edit an existing SSH command in a DeployHQ project.

Edit Config File

Tool to edit an existing config file within a project.

Edit Excluded File

Tool to edit an existing excluded file rule within a project.

Update Excluded File

Tool to update an existing excluded file rule in a project.

Update Project Repository

Tool to update repository details for an existing project in DeployHQ.

Update Server Group

Tool to update a server group in a DeployHQ project using the API.

Edit Template

Tool to edit an existing template in DeployHQ.

FAQ

Frequently asked questions

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

Yes, you can. Claude Code 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 DeployHQ tools.

Yes, absolutely. You can configure which DeployHQ 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.

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 DeployHQ data and credentials are handled as safely as possible.

Start with DeployHQ.It takes 30 seconds.

Managed auth, hosted MCP servers, and every DeployHQ tool your agent needs.Free to start.

Start building