← All integrations

DeployHQ MCP server

216 operations0 webhooks

Manage DeployHQ accounts, projects, servers, deployments, configuration, users, and deployment resources through its documented REST API.

Use DeployHQ in Claude, ChatGPT, Cursor or another MCP client

Connect DeployHQ once in Corsair, then add one MCP address to your agent.

Connect DeployHQ
Setup steps for Claude, ChatGPT, Cursor and Claude Code

Building your own app on the Corsair SDK? Get API keys

Try DeployHQ with your agent

Connect DeployHQ, then paste this into Claude, ChatGPT or Cursor. For ideas from other apps, see the use cases.

Using Corsair, show me what you can do in DeployHQ on my account, then run one read-only example and show me the result.

Runs once, when you ask

DeployHQ tools and triggers

Tools are what your agent can do in DeployHQ through Corsair's MCP server. Triggers are the DeployHQ events a routine can start from.

Projects

  • Ai Deployment Overview ProjectWrite

    AI Deployment Overview

    projects.aiDeploymentOverviewProject

  • Create ProjectWrite

    Create a project

    projects.createProject

  • Delete ProjectDestructive

    Delete a project

    projects.deleteProject

  • Get ProjectRead-only

    View a project

    projects.getProject

  • List Project InsightsRead-only

    Get project deployment insights

    projects.listProjectInsights

  • List ProjectsRead-only

    List all projects

    projects.listProjects

  • Regenerate Key Project Regenerate KeyDestructive

    Regenerate project SSH key

    projects.regenerateKeyProjectRegenerateKey

  • Replace ProjectWrite

    Update a project

    projects.replaceProject

  • Star ProjectWrite

    Toggle star/unstar on a project

    projects.starProject

  • Status Badge Status BadgeRead-only

    Get deployment status badge

    projects.statusBadgeStatusBadge

  • Status Badge Status Badge By IdentifierRead-only

    Get deployment status badge

    projects.statusBadgeStatusBadgeByIdentifier

  • Undeployed Changes Project Undeployed ChangeRead-only

    List undeployed commits for a project

    projects.undeployedChangesProjectUndeployedChange

Connect DeployHQ to Claude, ChatGPT or Cursor

  1. 1

    Connect DeployHQ in Corsair

    Add your DeployHQ API key once in Corsair. Corsair stores the credential encrypted and makes the DeployHQ API calls for your agent, so it never goes into a prompt or a config file. Connect DeployHQ

    If your link lets the agent add apps, you can skip this: it gives you a sign-in link the first time it needs DeployHQ. On a ChatGPT personal plan, connect DeployHQ here first.

  2. 2

    Add Corsair's MCP server to your agent

    Every client uses the same address:

    https://mcp.corsair.dev/mcp
    Open Customize → Connectors → Add custom connector, paste the address, then select Connect.

    Codex, Gemini CLI, VS Code, Zed and other clients with OAuth sign-in work the same way. Clients without it, such as GitHub Copilot's coding agent, use a link's own address and an API key. Setup for every client

  3. 3

    Sign in and choose what needs your approval

    Your client opens Corsair to sign in. Pick a link: the apps your agent can use and a mode that decides what it may do without asking. In the default Cautious mode, DeployHQ's read and write operations run right away and its 38 destructive operations wait for your approval. Strict mode asks before every write and refuses destructive operations, and Read mode allows reads only.

FAQ

Install corsair and @corsair-dev/deployhq, add the DeployHQ plugin, and connect with an API key. Then call methods like corsair.deployhq.api.account.billingStatusAccountBillingStatus() from your app. Corsair keeps each tenant isolated.

Yes. DeployHQ requires an API key from your DeployHQ account or developer dashboard. Create credentials with access that matches what you automate, then paste them into Corsair or connect through managed auth in Hub.

Yes. One Corsair client can hit DeployHQ, GitHub, Notion, Stripe, and the rest. Trigger DeployHQ from a webhook, push updates to Slack, or chain actions across plugins. Same tenant context across integrations, plain TypeScript.

Teams use Corsair for manage DeployHQ accounts, projects, servers, deployments, configuration, users, and deployment resources through its documented REST API. Common builds include sync jobs, admin tooling, and agents that call DeployHQ APIs from your backend.

The SDK is open source. Self-host and you pay Corsair nothing for the integration layer. Hub bills for hosted auth and execution, not per DeployHQ API call. Hub has a generous free tier. For hobby projects you can probably run the whole thing on free. Paid plans start to matter with more tenants or heavier traffic.

We maintain @corsair-dev/deployhq in the open repo. When DeployHQ ships API changes, upgrade the package. Your call sites stay typed. You should not need to rewrite the integration layer each time.

No. Corsair does not read your DeployHQ data or hold individual access credentials. Credentials stay in your database. API calls run on your instance. We do not store DeployHQ data on your behalf.

Yes. Add https://mcp.corsair.dev/mcp as a custom connector or MCP server in Claude, ChatGPT, Cursor, VS Code, Claude Code, Codex or any client that supports remote MCP servers with OAuth sign-in, then sign in to Corsair. On ChatGPT personal plans, custom servers currently get read tools only.

Yes. Put DeployHQ on a link in Strict mode and every write waits for your approval, while destructive actions are refused. The default Cautious mode asks only before the 38 destructive DeployHQ operations. You can change a link's mode at hub.corsair.dev/me.