---
title: OpenClaw | FLORA API
description: Add FLORA MCP to OpenClaw with the openclaw mcp CLI.
---

[OpenClaw](https://openclaw.ai) is a local-first personal AI assistant. MCP servers are managed with the `openclaw mcp` CLI; entries are stored in `~/.openclaw/openclaw.json` under `mcp.servers`.

## Install

Register FLORA as an MCP server:

Terminal window

```
openclaw mcp set flora '{"command":"npx","args":["-y","mcp-remote","https://agents.flora.ai/mcp"]}'
```

OpenClaw’s HTTP transport only supports static bearer headers, not the OAuth 2.1 + PKCE flow FLORA MCP uses. The [`mcp-remote`](https://www.npmjs.com/package/mcp-remote) shim bridges OpenClaw’s stdio interface to FLORA’s hosted HTTP transport and handles the browser OAuth handshake. You’ll need Node.js 18+ on the machine.

## Authorize

Ask OpenClaw:

> List my FLORA Techniques.

`mcp-remote` opens a browser for OAuth on first use. Sign in to FLORA and approve. The token is cached in `~/.mcp-auth/`.

## Verify

Terminal window

```
openclaw mcp list
openclaw mcp show flora
```

The first command lists every configured server; the second prints FLORA’s full entry so you can confirm the command and args round-tripped correctly. Note that these read OpenClaw’s config — they don’t reach out to `agents.flora.ai` to validate connectivity. The smoke test is asking the agent to list Techniques.

## Remove

Terminal window

```
openclaw mcp remove flora
```

To clear the cached OAuth token: `rm -rf ~/.mcp-auth/flora`. Revoke server-side in FLORA → Settings → Connected apps.

## Next

- [Authentication details](/mcp/authentication/index.md)
- [Tools reference](/mcp/tools/index.md)
- [Troubleshooting](/mcp/troubleshooting/index.md)