Skip to main content
OpenClaw can save remote MCP server definitions in its MCP registry. Use this guide to connect OpenClaw-managed runtimes to the hosted Lightsage MCP endpoint.
1

Confirm MCP registry support

Confirm your OpenClaw build includes the MCP registry commands:
The help output should include commands such as set, status, and doctor. If it only prints the top-level OpenClaw help, update OpenClaw or use another MCP client until your build includes the registry commands.
2

Get your Lightsage API key

Open the Lightsage dashboard, copy your API key, and store it as LIGHTSAGE_API_KEY:
Do not put your API key in shared project config, screenshots, issue reports, or public repositories.
3

Add Lightsage MCP to OpenClaw

Save Lightsage as a streamable HTTP MCP server:
Or write the JSON explicitly if you are editing a private local config:
Use direct JSON only on a private machine. Avoid committing literal API keys.
4

Verify OpenClaw tools

Run the OpenClaw static and live checks:
Then run a read-only prompt in an OpenClaw runtime that uses the MCP registry:
See the OpenClaw MCP docs for registry commands, live probes, OAuth, and streamable HTTP options.