Hydra ACI
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| logging | {} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": true,
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| navigateB | Navigate the stealth browser to a URL and discover session-specific actions for the page. |
| hydra_executeB | One-shot autonomous execution: provide a target URL and goal, and Hydra will complete the task automatically. |
| hydra_mountA | Mount a website as a persistent Hydra web capability workspace and return its canonical capability catalog. |
| hydra_probeC | Mount a website for browser-as-probe discovery, then return direct machine-usable capabilities separately from browser-action fallbacks without executing a generated capability. |
| hydra_refreshA | Re-scout the mounted site and refresh its capability catalog. |
| hydra_call_toolB | Call a mounted Hydra capability by canonical id, namespaced capability name, or original tool name. |
| hydra_inspect_sessionA | Inspect the current mounted Hydra session and route plan. |
| hydra_memoryC | Inspect or manage H8 web memory for a domain. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| hydra_execute_web_task | Use Hydra's one-shot executor to complete a web task through the best available route. |
| hydra_mount_web_session | Mount a web target as a live Hydra MCP session, then inspect tools and resources before acting. |
| hydra_inspect_current_session | Inspect the currently mounted Hydra session using MCP resources and tools. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| Hydra MCP capabilities | Redaction-safe summary of the live Hydra MCP engine and available protocol surfaces. |
| Hydra static tools | Static MCP tools available before a page is compiled. |
TDQS
Scored across 8 tools
The tools have distinct purposes, but 'hydra_mount' and 'hydra_probe' both involve mounting and could cause confusion despite different intents. Overall, agents can distinguish them with careful reading.
Most tools use the 'hydra_' prefix, but 'navigate' breaks the pattern. The naming styles vary: some are single verbs, some verb_noun, and 'hydra_memory' is a noun. This inconsistency reduces predictability.
With 8 tools, the count fits well within the recommended 3-15 range. Each tool appears justified for the server's complex web automation domain.
The tool set covers mounting, probing, refreshing, inspecting, memory management, calling capabilities, executing tasks, and navigation. A notable gap is the lack of an explicit unmount or close tool, but the core workflow is covered.