Hyperagent MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| HYPERAGENT_COOKIES_FILE | No | Absolute or relative path to the cookie file. Default is ./cookies.md relative to current working directory. | cookies.md |
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
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| hyperagent_modelsA | Lists the two Hyperagent models supported by this local bridge. |
| hyperagent_chatA | Sends a prompt to Fable 5 or GPT-5.6 Sol through Hyperagent. Omit thread_id to create a thread; reuse the returned thread_id to continue it. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 2 tools
The two tools have clearly distinct purposes: hyperagent_models lists supported models, and hyperagent_chat handles chat interactions. There is no functional overlap between them.
Both tool names follow a consistent snake_case pattern with the 'hyperagent_' prefix, making them easy to understand and predict.
With only 2 tools, the server feels minimal but still covers the core functionality of listing models and chatting. A few more management tools (e.g., thread listing) would be welcome, but the count is not unreasonable for a focused bridge.
The essential operations (list models, send prompts, manage threads implicitly via thread_id) are covered. Minor gaps include the lack of explicit thread management tools like list or delete threads, but the core workflow is supported.