Meet `dhq` — our new Go CLI for DeployHQ.
Trigger deploys, tail logs, roll back, all from the terminal. Built for humans AND AI agents: stdout is data, stderr is for humans.
Plays nice with Claude Code, Cursor, Windsurf out of the box.
https://t.co/9oxkvol1br
@HashgraphOnline Fair question. Today the MCP server is read-only and scoped to the signed-in user's permissions. Write tools will keep that model, with specifics on what a client can trigger shared before they ship.
Ask your AI assistant about your deployments.
The DeployHQ hosted MCP server is live: add one address to Claude Code, Codex, Gemini CLI or Cursor, sign in, and ask what failed and where things deploy.
Read-only at launch. Write tools are coming soon.
https://t.co/pBxyud0t8B
Looking for a GitHub alternative? We compared GitLab, Bitbucket, Gitea, Forgejo, Codeberg and Entire on pricing, self-hosting, built-in CI and migration, plus the webhook header each one uses to trigger deploys.
https://t.co/N4AhyeOZet
@kidtsang Agreed, and that's the idea: the hosted MCP server reads your actual deployment history, logs and server state, so the assistant answers from what really happened rather than guessing
@razaanstha Hey @razaanstha — apologies for today. The git tracking failures came from an upstream GitHub incident (SSH deploy keys), now resolved: https://t.co/FCCZUeMGrK. On the UI: we hear you — mind DMing specifics on what feels off? We genuinely want to fix it.
Most guides on giving an AI coding assistant database access start with the hard case: production Postgres, credentials, network access, read-only roles.
That's backwards. The safest place to start is a database that lives in one file on your laptop. 🧵
Two habits that keep it honest:
• Back up before writes, not reads — selects can't hurt the file
• Read the SQL before you run it — the assistant is drafting, not deciding
Prototype where undo is free, promote where it isn't.
6/ Full write-up with the actual GRANT SQL for Postgres/MySQL/SQL Server, the MCP flags, the sandbox pattern, and a copy-paste safety checklist: https://t.co/VD6rjXXp6Z
1/ "An AI assistant deleted our production database" isn't a story about a rogue AI. It's a story about a connection string with write permissions and no seatbelt. The fix is boring and it works: read-only guardrails. 🧵
5/ Step three: for anything that needs to write, give the AI a disposable copy — a throwaway Postgres loaded from a sanitized dump. It can mutate all it wants; nothing real is at risk. Schema changes still go through your deploy pipeline, never the agent.