View raw

Nous Hermes#

Connect ClipKit to Hermes — Nous Research's open-source agent (terminal app + Hermes Desktop) — whose built-in MCP client auto-loads tools from configured servers at startup.

ClipKit's connector is open (no key) and speaks Streamable HTTP at https://www.clipkit.dev/mcp.

Add the connector#

CLI:

hermes mcp add clipkit --url https://www.clipkit.dev/mcp

Or in config.yaml:

mcp_servers:
  clipkit:
    url: "https://www.clipkit.dev/mcp"
    # no headers needed — open, no-auth server

Verify#

Run /mcp in a Hermes session (or hermes mcp list) — clipkit should show as connected with its tools. Then ask the agent to use one.

Notes#

  • Transport is inferred, not declared — a url field means an HTTP server. Don't add a transport: / type: key, and don't point it at a /sse path (ClipKit's legacy SSE stream is disabled). Use the plain /mcp URL.
  • No auth — leave headers out.
  • Local option. ClipKit also runs as a local stdio server via npx -y @clipkit/cli mcp, which adds transcribe_to_captions (Whisper) and render_video. Hermes's MCP client supports stdio servers — since transport is inferred from the config shape, use a command / args pair instead of url and check the key names against Hermes's current docs. See Run it locally for what differs between the two routes.

New to the tools? The MCP server overview has the full tool list and how projects work.