Hydrant has a page in Claude’s connector directory. That’s one fewer URL to paste into a form. Open the listing and add it from there.
Behind the listing is the same address every other client uses, https://hydrant.dev/api/mcp. Claude Code and Codex users: nothing changed for you. The commands in Connect your agent still work.
Read the banner
The listing says Community. The banner under it says what that means: Community connectors have been through automated reviews, not Anthropic verification. It’s a fair warning for any tool that can write to your tracker, ours included. Hydrant is made by Background Craft LLC, and the rules below are ours to keep.
One workspace, your call
Connecting sends you to Hydrant in the browser. Sign in with GitHub, pick one workspace and choose what Claude gets:
- Read only: it can look. It can’t touch.
- Read and write: it creates, edits and comments as you.
Either way, Claude never gets more than your own role in that workspace. A second workspace means a second connection. What you’re approving walks through the consent screen line by line.
The connection then appears in Hydrant under Settings › Agents › Access. It reads “authorized, waiting for its first contact” until Claude makes its first request, then flips to verified. Revoke it there whenever you like. Claude doesn’t get a vote.
Start with a question
Ask in plain words. Claude picks the tools.
- “What’s ready for me in Hydrant?”
- “Read #12 and tell me what’s missing before it’s Ready.”
- “What’s blocking the Launch project?”
- “File a bug: the export button does nothing on Safari.”
The first three work with either access level. The last one needs read and write. With read only, the server says no, and it means it.
If something goes sideways, When an agent gets stuck covers each error and what to do about it.
Filed under ShippedHenry Kobutra with Claude