DeployHQ logo
ConnectorDeployHQ

DeployHQ integration for Claude and Codex

Connect DeployHQ once, then control which Spaces can use its approved tools and data without pasting credentials into prompts or threads.

Use DeployHQ from Claude

Add the DeployHQ connection to a Space that runs Claude, then use it from every channel in that Space.

Use DeployHQ from Codex

Add the DeployHQ connection to a Space that runs Codex, then use it from every channel in that Space.

Use DeployHQ from Sidekick

Connect your own OpenClaw to Sidekick while type.com provides the conversations, permissions, connections, skills, and automations.

Developer Tools & IT

What the DeployHQ connector can do

DeployHQ automates deployments from Git, SVN, and Mercurial, and the housekeeping side, old projects, stale build caches, outdated exclusion rules, tends to pile up quietly. A DevOps Space in type.com can ask Claude to clear a build cache, remove a server group that's no longer used, or delete an old project, keeping the deployment configuration from accumulating clutter.

One connection, many Spaces

Connect DeployHQ once, then decide which Spaces can use it in threads, skills, automations, and coding work.

What teams do with DeployHQ in type.com

Clear a stale build cache

Remove a cached build artifact that's taking up space or causing a deploy to use outdated files.

Try asking
Delete the build cache file for our staging project in DeployHQ, the last deploy pulled a stale asset.

Retire an unused server group

Remove a server group from a project's configuration once that environment is decommissioned.

Try asking
Delete the legacy-eu server group from our main DeployHQ project.

Clean up an old project

Permanently remove a project that's no longer deployed anywhere.

Try asking
Delete the old marketing-site-v1 project from DeployHQ, we shut that site down last month.

Representative actions

  • Delete Command

    Removes an SSH command from a project's deployment configuration.

  • Delete Project

    Permanently removes a project from DeployHQ by its permalink or identifier.

  • Delete Build Cache File

    Removes a cached build artifact from a project's build cache storage.

  • Delete Excluded File Rule

    Removes an excluded file pattern from a project's deployment configuration.

  • Delete Server Group

    Removes a server group from a project's deployment configuration.

Connection

API and auth details

DeployHQ offers REST and OpenAPI documentation for automating deployments from Git, SVN, and Mercurial repositories. Integrations can trigger deployments, inspect projects, manage servers and config files, wire DeployHQ into CI/CD pipelines, and use authenticated API calls or the official Ruby gem for deployment workflows.

FAQ

Questions people ask before connecting DeployHQ

Can Claude manage DeployHQ configuration from type.com?

Yes. Once DeployHQ is connected to a Space, you can ask the agent to clear a build cache, remove a server group, or delete an old project, and the change shows up in the thread for the team.

How does type.com authenticate with DeployHQ?

DeployHQ uses basic authentication. An admin enters the credentials once when creating the connection and controls which Spaces can use it.

Can DeployHQ cleanup run on a schedule?

Yes. A recurring cleanup, such as reviewing stale build caches monthly, can be set up as a type.com automation that posts a summary to a channel.

Is this the same as an MCP server for DeployHQ?

Not exactly. type.com uses connectors and connections to give selected Spaces access to approved app tools and data. Some connectors use hosted MCP, while others use OAuth, API keys, service accounts, or custom APIs.

More developer tools & it connectors

All Developer Tools & IT integrations