Connect Hermes, OpenClaw & other agents

AI Connect ·4 min read ·Updated July 2026
You're here because

you run an agent like Hermes or OpenClaw, an automation platform, or your own scripts - and want them on the same endpoint, with a key instead of a login window.

Anything that speaks MCP over Streamable HTTP can use AI Connect – Hermes, OpenClaw, Cursor, Claude Code, n8n, custom agents and plain scripts. Clients with full OAuth support can sign in exactly like Claude does; for everything else there are Connection keys: long-lived Bearer tokens you generate in wp-admin.

Generate a Connection key

  1. Open Venuera → AI Connect → Connections.
  2. Click “Generate new connection key”.
  3. Copy the key right away – it is shown only once. Keys look like vmcp_key_….
Treat the key like a password. A Connection key acts as your WordPress user with all scopes and does not expire. If it leaks, revoke it on the Connections tab – revocation is instant.

Hermes & OpenClaw

In your agent’s MCP settings, add your site as a remote (Streamable HTTP) MCP server:

  • Server URL: https://your-site.com/wp-json/venuera-mcp/v1/mcp
  • Authentication: Bearer token – paste the Connection key.

The agent connects on its own with the key – no OAuth sign-in step. On the first connection it fetches the tool catalog and can start working immediately: “check today’s sales every morning and message me the summary” is now a one-line instruction to your agent.

Claude Code, Cursor & other developer clients

Add the endpoint as a remote MCP server (HTTP transport). These clients typically support both auth methods: OAuth (they open the browser for your WordPress login, like Claude) or a Bearer header with a Connection key. Either way they get the same tool catalog, filtered by the connected user’s permissions.

Automation platforms & scripts

n8n, Zapier-style MCP bridges and custom code authenticate with the Connection key in a standard header:

Authorization: Bearer vmcp_key_…

Requests are JSON-RPC 2.0 POSTs to the endpoint (initialize, tools/list, tools/call). Two protocol notes for implementers: the server is POST-only (a GET returns 405 – there is no SSE stream), and JSON-RPC batch requests are not supported.

Testing without a cloud client

MCP Inspector (npx @modelcontextprotocol/inspector) is the reference debugging tool – point it at your endpoint with a Connection key and you can browse tools and fire calls by hand. It runs locally, so it also works against a development site that cloud clients cannot reach.

Related questions

Was this article helpful? No or only partly? Tell us what was missing