OpenClaw
Add Xentropy to OpenClaw over Streamable HTTP and sign in with OAuth or an API key header.
OpenClaw connects to Xentropy as a remote MCP server.
Connect with OAuth
-
Add the server. Always pass the transport, because OpenClaw defaults to SSE:
openclaw mcp add xentropy --url https://api.xentropy.ai/mcp --transport streamable-http --auth oauth -
Sign in:
openclaw mcp login xentropy -
Sign in to Xentropy in the browser and review the requested access.
When OpenClaw runs as a gateway, sign-in returns to the gateway's public
origin (<public origin>/oauth/mcp/callback), so that origin must be reachable
over https from your browser. A local OpenClaw uses a loopback address.
Headless use with an API key
Create a key with the Agent preset under Settings → API Keys, keep it
in the gateway environment as XENTROPY_API_KEY, and set this header in your
OpenClaw config instead of signing in:
mcp.servers.xentropy.headers.Authorization: "Bearer ${XENTROPY_API_KEY}"Skill (coming soon)
A Xentropy skill on ClawHub is coming soon.
Scopes to grant
OAuth sign-in offers the agent default scopes: artifacts:read,
artifacts:write, artifacts:render, dashboards:read, dashboards:write,
data:read, data:write and connections:read. The Agent preset for API
keys matches that set. See API keys and scopes.
Troubleshooting
- New tools are missing. OpenClaw lists tools when it connects. After a Xentropy update, restart the gateway or reconnect the server.
- Sign-in does not return. Check the gateway's public origin and that it
serves
/oauth/mcp/callbackover https. - Revoked or expired. Run
openclaw mcp login xentropyagain.