Hydrant context, wired straight into your agents.
The Hydrant MCP gives Claude Code, Cursor, and any MCP client a direct path to the context graph behind your work: issues, decisions, notes, cycles, files, and execution briefs.
https://hydrant.dev/mcpOne hosted URL for browser discovery and client traffic.
Create revocable tokens in Hydrant settings.
Agents can gather context, update records, and assemble briefs.
The working set agents need.
The first catalog is hand-maintained so the landing page stays fast and build-safe. The protocol endpoint remains the source of truth for exact tool schemas.
Issues
get_issuelist_issuescreate_issueupdate_issueset_dependenciesPlanning
list_cyclesget_cycle_issueslist_milestonesget_milestone_issuesDecisions
get_decisionlist_decisionscreate_decisionupdate_decisionNotes
get_notelist_notescreate_noteupdate_notelist_foldersSearch
searchget_bundlepreview_bundlegenerate_bundleFiles
generate_upload_urlsave_fileget_file_urllist_filesPoint the client at one URL.
Create a personal access token in Hydrant, paste it into your MCP client config, and keep the public endpoint unchanged across clients.
Claude Code
Add Hydrant as a hosted HTTP MCP server.
{
"mcpServers": {
"hydrant": {
"type": "http",
"url": "https://hydrant.dev/mcp",
"headers": {
"Authorization": "Bearer hyd_sk_your-token-here"
}
}
}
}Cursor
Use the same endpoint and bearer token in Cursor's MCP config.
{
"mcpServers": {
"hydrant": {
"url": "https://hydrant.dev/mcp",
"headers": {
"Authorization": "Bearer hyd_sk_your-token-here"
}
}
}
}HTTP
Call the hosted endpoint directly from an MCP-aware HTTP client.
curl https://hydrant.dev/mcp \
-H "Authorization: Bearer hyd_sk_your-token-here" \
-H "Content-Type: application/json" \
-H "Accept: application/json, text/event-stream" \
--data '{"jsonrpc":"2.0","id":1,"method":"tools/list"}'