AI Agents

OpenClaw

An open-source personal agent that runs on your own machine and answers in your chat apps.

Connects with: Sign in, API key, Skill
Connector: SPREVA
Plans: Free and open source. You bring your own model provider.

Before you start

OpenClaw installed, with its gateway running.
An API key, created in SPREVA under Developer, then API keys.

Set it up

1
Put your SPREVA API key in your terminal's environment:
Terminal
```
export SPREVA_API_KEY=POST_API_KEY_...
```
2
Add SPREVA. Keep --transport streamable-http: without it, OpenClaw uses the older SSE transport, which SPREVA doesn't answer. OpenClaw checks the connection before it saves SPREVA.
Terminal
```
openclaw mcp add spreva \
  --url https://dev-app.spreva.ai/api/mcp \
  --transport streamable-http \
  --header "Authorization=Bearer $SPREVA_API_KEY"
```
3
Check that OpenClaw reaches SPREVA:
Terminal
```
openclaw mcp doctor spreva --probe
```

Also works with

Connector URL and sign in

Paste the connector URL into the app, sign in to SPREVA and click Allow. No key to keep safe.

Terminal

openclaw mcp add spreva \
  --url https://dev-app.spreva.ai/api/mcp \
  --transport streamable-http --auth oauth
openclaw mcp login spreva

The CLI and the Agent Skill
Install the spreva command line and its Agent Skill, for agents that work in a terminal.
Terminal
```
export SPREVA_API_KEY=POST_API_KEY_...
npx -y @spreva/cli skill install --target openclaw
```

Check it works

Start a new conversation and ask:

Ask your agent

What's going out this week on SPREVA?

OpenClaw calls SPREVA's overview tool and answers with the workspace's time zone, what goes out next and anything that needs attention. The first time, OpenClaw may ask you to allow the tool.

Troubleshooting

OpenClaw can't connect to SPREVA

Run openclaw mcp status --verbose. If SPREVA's transport is sse, remove it with openclaw mcp unset spreva and add it again with --transport streamable-http.

OpenClaw asks me to sign in although I added a key

With --auth oauth, OpenClaw signs in and ignores the Authorization header. Use one or the other: remove SPREVA and add it again the way you want.

The Agent Skill says the API key is missing

The commands OpenClaw runs read SPREVA_API_KEY from the gateway's environment. Set it there and restart the gateway.

Something else? Troubleshooting covers sign-in loops, plans, limits and time zones.