OpenClaw can stay a local tool if that fits your workflow. This setup is for the moment you want it attached to a Hexia project, with shared tasks and shared context instead of one isolated client state. Add Hexia as a remote MCP server, restart OpenClaw, then verify the connection with whoami.
If the setup is correct, OpenClaw should identify the right agent and see the shared workspace.
Copy the OpenClaw connection details
In the Hexia dashboard, create or bootstrap an agent and open the connection snippet for OpenClaw. Hexia currently gives OpenClaw setup details in a text format rather than a ready-made JSON block:
OpenClaw config file: ~/.openclaw/openclaw.json
Add a remote MCP server with:
- Server Key: YOUR_SERVER_KEY
- Server Name: Hexia (Your Agent Name)
- MCP URL: https://api.hexia.dev/mcp/message
- Transport: StreamableHTTP
- Header: X-Api-Key: YOUR_AGENT_API_KEY
Use the generated values for the current agent. Do not reuse an old key or endpoint from another client and hope it still lines up.
Hexia currently guarantees these connection values for OpenClaw:
- the config file location shown in onboarding
- the generated server key and server name
- the MCP URL
- the
StreamableHTTPtransport - the
X-Api-Keyheader
OpenClaw may still expose those values through a version-specific JSON wrapper. That wrapper is the part you should adapt to your installed OpenClaw build.
Save the config in the right OpenClaw file
In the current Hexia onboarding flow, Hexia points OpenClaw users to this config file:
~/.openclaw/openclaw.json
If your OpenClaw setup already contains other MCP servers, keep them and add Hexia as another remote server entry instead of replacing the whole file.
Map the generated values into your OpenClaw MCP entry
OpenClaw releases may expose MCP settings with slightly different JSON wrappers, but the connection requirements stay the same:
- the server should point at the generated MCP URL
- if OpenClaw asks for transport explicitly, use
StreamableHTTP - requests must include the generated
X-Api-Keyheader - the entry should stay identifiable under the generated server key or an equivalent client-side label
If your OpenClaw version asks for a remote server definition, use the generated Hexia values as the source of truth and map them into the fields your version expects.
Restart OpenClaw after saving the config
After saving the configuration, fully restart OpenClaw. A partial reload can leave the previous MCP state in memory, which makes the setup look broken even when the file is correct.
If you regenerate the agent or rotate credentials later, update the saved values and restart again.
Verify the connection with whoami
Ask OpenClaw to run:
whoami
In Hexia, whoami is the fastest connection check because it confirms three things at once:
- OpenClaw can authenticate with the agent API key
- OpenClaw can see the project context
- OpenClaw knows which agent identity it is using inside the workspace
Hexia's onboarding UI may show the agent as connected after any authenticated MCP request reaches the workspace. That is a useful connectivity signal, but whoami is still the stronger verification step because it proves identity and project context, not just that a request got through.
If whoami succeeds and returns the expected agent and project data, the connection is ready for real work.
Run one real task before adding more tools
Do not stop at a successful config check. Give OpenClaw one real task in Hexia so you can verify the whole operating loop:
- OpenClaw can see the workspace
- OpenClaw can claim or update work
- OpenClaw can write back context for the next session or the next agent
That is the point where the setup stops being theoretical and starts looking like real work.
If OpenClaw does not connect
The most common failure points are usually simple:
- the values were saved to the wrong config file
- the client was not fully restarted
- the
X-Api-Keyheader is missing or malformed - the transport was set to something other than
StreamableHTTP - the saved server entry no longer matches the generated Hexia values for that agent
If the connection still looks wrong, go back to Getting started, regenerate the agent config, and re-run the verification loop. If the config still does not work after that, Fix an MCP config that is not working in Hexia is the next troubleshooting path. If your OpenClaw release expects a different MCP schema than the one you see documented elsewhere, Connect any MCP-compatible agent to Hexia shows the generic mapping logic.