2.4 KiB
2.4 KiB
Connecting Hermes MCP to CLI Agents
Hermes exposes a Streamable HTTP MCP endpoint at:
https://hermes.squaremcp.com/mcp
Legacy SSE is also available at:
https://hermes.squaremcp.com/sse
Use your own credential value anywhere you see:
YOUR_MCP_API_KEY
Never commit a live API key into repo config files.
Claude Code
Some Claude Code builds support MCP add/list commands and some require manual config.
If your Claude CLI supports mcp add
claude mcp add hermes \
--transport http \
https://hermes.squaremcp.com/mcp \
--header "x-api-key: YOUR_MCP_API_KEY"
Manual config
If your version does not support the CLI flow, add Hermes to:
~/.claude/mcp.json
{
"mcpServers": {
"hermes": {
"url": "https://hermes.squaremcp.com/mcp",
"headers": {
"x-api-key": "YOUR_MCP_API_KEY"
}
}
}
}
Verify
claude mcp list
Claude Desktop
Add Hermes to the Claude Desktop config:
macOS
~/Library/Application Support/Claude/claude_desktop_config.json
Linux
~/.config/Claude/claude_desktop_config.json
Windows
%APPDATA%\Claude\claude_desktop_config.json
{
"mcpServers": {
"hermes": {
"url": "https://hermes.squaremcp.com/mcp",
"headers": {
"x-api-key": "YOUR_MCP_API_KEY"
}
}
}
}
Restart Claude Desktop after saving the file.
Generic MCP-capable CLI agents
Many agent CLIs and editor plugins accept a JSON config file with an mcpServers block.
Example portable config:
{
"mcpServers": {
"hermes": {
"url": "https://hermes.squaremcp.com/mcp",
"headers": {
"x-api-key": "YOUR_MCP_API_KEY"
}
}
}
}
Typical usage pattern:
some-agent-cli --mcp-config-file ~/.mcp.json
Possible target clients include:
- custom MCP wrappers
- editor plugins that expose MCP server config
- internal agent CLIs that consume a shared JSON config
SSE fallback
If a client only supports SSE:
{
"mcpServers": {
"hermes": {
"url": "https://hermes.squaremcp.com/sse",
"headers": {
"x-api-key": "YOUR_MCP_API_KEY"
}
}
}
}