A few loose fittings.
Straight answers, no chatbot. If yours isn’t here, that’s our bug, and bots@hydrant.dev wants to hear about it.
What is Hydrant?
Hydrant is an issue tracker for builders who work with their own agents, solo or as a small team. Issues, blockers, projects, cycles and a shared Playbook live in one workspace. A scoped MCP connection lets your agents take work, post their evidence and hand it back in the same place you plan, and Sign-off is where a person reviews what they finished.
What can I do with it today?
Track and plan: capture issues in Markdown with images, and quick capture offers an unsolicited opinion on size, labels and likely duplicates without changing anything until you click. Sort with labels, priority, size and saved views, as a list or a Board, and change dozens at once. Connect blockers and sub-issues, plan with projects, milestones, roadmap targets and cycles, and see what shipped and where work waits in Insights. Follow any issue and get a daily digest and a Monday recap.
Review, release and agents: name reviewers on a review stage and decide finished work on Sign-off. On Solo Pro or the 14-day trial, follow Done work through your environments, with approvers, promotions and named releases. Link GitHub pull requests to issues and, if you choose, let them move status. Connect your own agents over MCP and teach them your process with the Playbook and the free workflow pack.
Does it run AI agents for me?
No. Bring your own agent client and connect it through MCP with a workspace-scoped credential. Hydrant exposes work and records changes; it does not supply a model or run agents in the background. Your agent provider has its own terms and data practices.
Which agents can connect?
Any MCP client that speaks Streamable HTTP, signing in through the browser with OAuth or using an agent key. We test Claude Code, Claude (claude.ai and Desktop) and Codex. Setup takes about two minutes, most of it spent in your browser.
Can I use it with a team?
Free includes 1 human per workspace; Solo Pro includes 3; Team has no cap. The owner’s plan covers everyone in that workspace. New accounts get 14 days of Solo Pro, on us, with 3 humans and no card. Every human in the workspaces you own is one seat, however many of them they’re in, you included. Agents never take one. Add someone new and the bill grows by a seat, prorated from that day. Remove someone and the unused time comes back as credit on your next invoice.
Do I need GitHub?
No. Sign in with GitHub or with a six-digit code sent to your email address, and keep both on one account if you like. Hydrant does not require you to select or connect a repository to track issues. Owners and Admins can optionally connect repositories so pull requests show up on the issues they mention; the person connecting needs GitHub among their sign-in methods. Hydrant never writes to GitHub. Pull requests change an issue only if an Owner or Admin turns on status automation, which moves its status under rules the workspace sets, or environment detection, which moves a Done issue’s environment as its commits reach each branch.
What is Sign-off?
One page for everything waiting on your word, with a count in the sidebar. In review lists the issues in review stages you decide: press Accept, or Send back with a note that tells whoever built it what to change. Each issue leads with its brief, What changed, How to check and Not done, so you don’t read the whole ticket to find out. A docket puts a few issues under one brief and you answer them together. Accept up to 100 at a time. All of it works on every plan.
Naming reviewers enforces nothing. Anyone can still move a status by hand; reviewers just get asked first.
I’m coming from Linear. Is there a Board?
Yes, on every plan. Any issue list switches between List and Board under Display. Columns, swimlanes and groups inside each column can use Status, Priority, Assignee, Size, Project, Milestone, Cycle or Label, and Environment too, read-only. Dropping a card sets every property the Board shows.
The difference you’ll notice: there’s no Manual ordering. Cards follow the view’s Ordering, such as Priority, and you hand-order only the cards that tie, so a High never ends up under a Medium. The hand order is shared with the whole workspace.
How do environments and releases work?
Done says the work is finished. Environment says where it has got to: Testing, Staging, Production, whatever you call yours. Promote to the next environment moves every Done issue in one go, in the app or over MCP, and GitHub can move issues as their commits reach each branch. Approvers you name answer every issue that lands, from Approve to Reject, with Hold for work you’ll fix forward and Pass for work that isn’t theirs to judge. An approver can clear an environment for the next one; clearing moves nothing, it tells engineering it can go. A promotion into the last environment can become a named release with notes. Hydrant never touches your branches or reads your feature flags. Environments come with Solo Pro or the 14-day trial: up to 10 per workspace, with approvers, promotions and named releases. Free has none.
Where is Hydrant listed?
In Claude’s Connectors Directory, in the official MCP Registry as dev.hydrant/hydrant, and on Glama. Any other MCP client that speaks Streamable HTTP connects by URL: https://hydrant.dev/api/mcp.
What happens when I trash an issue?
Trash is recoverable for 30 days. It keeps the issue’s content and relationships, and restoring it brings its blocking effect back. After 30 days in Trash, a daily purge permanently removes the issue and its dependents. Restoring from an older backup can bring a purged issue back; it is purged again once it has spent another 30 days in Trash.
Can I export my workspace?
Yes. An Owner or Admin requests one from Settings → General. Hydrant builds a .tar.gz of issues, comments, activity and settings as JSON and Markdown, and the download stays up for seven days. Images are listed with authenticated download links rather than bundled. One export per workspace per hour.
What does it cost?
Free is $0. Solo Pro is USD $6 per month or $60 per year per account. Team is USD $12 per human per month or $120 per human per year. Annual billing is selected by default: $60 charged annually ($5/month equivalent). Prices exclude applicable tax. Your account covers the workspaces you own. Free seats one human per workspace. Solo Pro seats three at no extra cost. On Team, every human is a seat. Unlimited issues on every plan. We don’t meter the mess. Start on Free. Upgrade to Solo Pro or Team from Settings → Billing whenever you outgrow it. New accounts get 14 days of Solo Pro, on us. Once per email address. No card. There will always be a Free plan. If its limits ever change, nothing you already have gets taken back.
Where do I report a leak?
Bugs, questions and privacy requests can go to bots@hydrant.dev. Security vulnerabilities go to security@hydrant.dev; the security page covers scope and what to expect. Include enough context to reproduce a bug, but keep passwords, agent keys and private workspace content out of your message.
Is Hydrant having trouble?
Check service status for reported interruptions and maintenance. The status page covers website and application reachability; it does not guarantee every feature is available. If a request fails, keep your tab open to preserve unfinished work, check status in a separate tab, then try again.