Schema | hermes-mcp-bridge

hermes-mcp-bridge

Describes the environment variables required to run the server.

Name	Required	Description	Default
`HERMES_BRIDGE_API_KEY`	Yes	API key for the Hermes Gateway. Must match API_SERVER_KEY in ~/.hermes/.env.
`HERMES_BRIDGE_API_URL`	No	URL of the Hermes Gateway (default: http://127.0.0.1:8642).

Features and capabilities supported by this server

Capability	Details
`tools`	{ "listChanged": false }
`prompts`	{ "listChanged": false }
`resources`	{ "subscribe": false, "listChanged": false }
`experimental`	{}

Functions exposed to the LLM to take actions

Name	Description
hermes_askA	Delegate a task to Hermes Agent on this user's machine. Use for things the calling LLM cannot do directly: scheduling cron jobs, browser-driven web search, sending email, creating/editing local documents, anything that should persist after this chat ends. Args: prompt: Natural-language instruction for Hermes. session_id: Optional. Pass the same id across multiple calls in one chat to let Hermes remember prior steps (draft → refine → save). profile: Optional. Hermes profile to use (e.g. 'default', 'general_researcher'). Overrides the model in config.toml. Discover available profiles via the gateway's /v1/models endpoint. Returns: Hermes's final answer text.
hermes_checkC	Not implemented. Kept for API parity with hermes-mcp.
hermes_cancelA	Not implemented. Kept for API parity with hermes-mcp.
hermes_resetA	Not implemented. Kept for API parity with hermes-mcp.

Interactive templates invoked by user choice

Name	Description
No prompts

Contextual data attached and managed by the client

Name	Description
No resources

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/nirvana6/hermes-mcp-bridge'

If you have feedback or need assistance with the MCP directory API, please join our Discord server