The DeployHQ MCP server facilitates interaction between AI assistants and DeployHQ deployments, allowing for project management and deployment operations through a standardized protocol.
From the registry: Model Context Protocol (MCP) server for DeployHQ API integration
Please install the `deployhq-mcp-server` MCP server into my current AI client (that's you).
Required prerequisites (do these first if not already done):
- **DeployHQ account with API access** — Create or use an existing DeployHQ account (API access available on all paid plans). (https://www.deployhq.com)
Canonical MCP server config (stdio transport):
- command: `npx`
- args: ["-y","deployhq-mcp-server"]
- required environment variables:
- `DEPLOYHQ_EMAIL`: DeployHQ login email. (example: `<your-email>`)
- `DEPLOYHQ_API_KEY`: DeployHQ password or API key. (example: `<your-deployhq-api-key>`)
- `DEPLOYHQ_ACCOUNT`: DeployHQ account name (from https://ACCOUNT.deployhq.com). (example: `<your-account>`)
- optional environment variables:
- `LOG_LEVEL`: Log verbosity: ERROR, INFO, or DEBUG. Defaults to INFO. (example: `INFO`)
- `DEPLOYHQ_READ_ONLY`: Set to 'true' to block all mutating operations. (example: `false`)
Note: 18 tools for DeployHQ API. Optional SSE/HTTP hosted mode exists but stdio npx is canonical.
Add this MCP server to my current client's config in the correct format for you. If you need secrets or credentials I haven't provided, ASK me — do not invent values or leave raw placeholders. After adding it, tell me how to verify the server is connected.DEPLOYHQ_EMAILrequiredYour DeployHQ login emailDEPLOYHQ_API_KEYrequiredYour DeployHQ password/API keyDEPLOYHQ_ACCOUNTrequiredYour DeployHQ account nameReal-time Kubernetes network traffic visibility and API analysis for HTTP, gRPC, Redis, Kafka, DNS.