Schema | codex-hermes-a2a-bridge

codex-hermes-a2a-bridge

Describes the environment variables required to run the server.

Name	Required	Description	Default
No arguments

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.

Features and capabilities supported by this server

Protocol revision2025-11-25

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_statusA	Check bridge persistence, Hermes health, connectivity, and a concise Agent Card summary.
hermes_chatA	Start or continue a Hermes conversation; returns a durable bridge task and A2A context mapping.
hermes_task_getA	Get one bridge task, its Hermes status/result/input request, and recent lifecycle events.
hermes_tasks_listA	List durable bridge tasks, optionally filtered by conversation and bridge state.
hermes_task_waitA	Wait for task progress/result using the active stream, A2A subscribe, then polling fallback.
hermes_task_cancelA	Request task cancellation; response is explicit that Hermes may continue underlying computation.
hermes_contextsA	List, inspect, or close bridge-owned conversation/context mappings; close never deletes Hermes data.

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/phamviet86/codex-hermes-a2a-bridge'

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