The API reference moved here from eksis.io/developers.
Clients

OpenClaw

Connect OpenClaw to an eksis workspace over MCP.

Authentication: OAuth sign-in, API key

Server URL

https://api.eksis.io/mcp

Set it up

Stop the Gateway before you change saved servers, or add eksis from the Control UI under Settings, then MCP, while it runs. --auth oauth tells OpenClaw to sign in, and openclaw mcp login opens the eksis consent screen, where you pick the workspace and the permissions. openclaw mcp doctor eksis --probe then connects and lists the tools, because saving a server does not prove it is reachable. If the Gateway signs in on behalf of other people, set gateway.publicOrigin to its public HTTPS address first: eksis sends the browser back to that address after consent. To use an API key instead, put it in ~/.openclaw/.env and reference it as ${EKSIS_API_KEY}, so the key never sits in the config file.

Configuration

openclaw mcp add eksis --url https://api.eksis.io/mcp --transport streamable-http --auth oauth
openclaw mcp login eksis
openclaw mcp doctor eksis --probe

Set it up with an AI agent

Paste this prompt into OpenClaw, or into any other AI agent that can run commands and edit files on the same computer. It stops and hands back to you when eksis asks you to sign in.

Prompt
Connect the eksis MCP server to OpenClaw on this computer.

Server URL: https://api.eksis.io/mcp
Setup guide: https://docs.eksis.io/en/mcp/clients/openclaw

Use OAuth sign-in. Follow the API key steps only if I give you a key that starts with eksis_sk_. Then use my key wherever the steps show eksis_sk_..., or set it as EKSIS_API_KEY where they read that variable.

OAuth:
```bash
openclaw mcp add eksis --url https://api.eksis.io/mcp --transport streamable-http --auth oauth
openclaw mcp login eksis
openclaw mcp doctor eksis --probe
```

API key:
```bash
echo 'EKSIS_API_KEY=eksis_sk_...' >> ~/.openclaw/.env
openclaw mcp set eksis '{"url":"https://api.eksis.io/mcp","transport":"streamable-http","headers":{"Authorization":"Bearer ${EKSIS_API_KEY}"}}'
openclaw mcp doctor eksis --probe
```

From the setup guide:
Stop the Gateway before you change saved servers, or add eksis from the Control UI under **Settings**, then **MCP**, while it runs. `--auth oauth` tells OpenClaw to sign in, and `openclaw mcp login` opens the eksis consent screen, where you pick the workspace and the permissions. `openclaw mcp doctor eksis --probe` then connects and lists the tools, because saving a server does not prove it is reachable. If the Gateway signs in on behalf of other people, set `gateway.publicOrigin` to its public HTTPS address first: eksis sends the browser back to that address after consent. To use an API key instead, put it in `~/.openclaw/.env` and reference it as `${EKSIS_API_KEY}`, so the key never sits in the config file.

Rules:
- If OpenClaw already has a server named eksis, show me its entry and ask before you change it.
- Never put an API key in a file that is committed to git. Keep it in an environment variable or the client's own secret store, as the steps show.
- If a command asks a question interactively, show me the question and wait for my answer.
- When eksis opens a sign-in page in the browser, stop and ask me to pick the workspace and approve it. Do not approve it for me.

When you are done, check the connection and list the eksis tools OpenClaw can see. If it fails, show me the error.

How the two ways of signing in differ, and what each permission allows, is on the MCP overview. The tool list shows what the assistant can ask eksis to do.

On this page