> ## Documentation Index
> Fetch the complete documentation index at: https://docs.levios.app/llms.txt
> Use this file to discover all available pages before exploring further.

# Connect OpenClaw

> Add levios as a remote MCP server in OpenClaw.

<Note>
  Available tools and activation support depend on your current connection. After
  connecting, ask the agent to check the available operations before creating an
  automation.
</Note>

## Add the server

OpenClaw reads MCP servers from `~/.openclaw/openclaw.json`. Add this entry
under `mcp.servers`:

```json theme={null}
{
  "mcp": {
    "servers": {
      "levios": {
        "url": "https://levios.app/api/mcp",
        "transport": "streamable-http",
        "auth": "oauth",
        "enabled": true
      }
    }
  }
}
```

If the file already has other servers, add the `levios` entry inside the
existing `servers` object instead of replacing the file.

## Restrict which agents can reach levios

OpenClaw routes servers per agent. An agent with no override inherits the global
list, which means every agent can call levios by default. To limit levios to
specific agents, list it under `agents.<name>.mcpServers` for those agents only.

This matters because a levios grant reaches real Instagram accounts. Give the
connection to the agents that need it rather than to all of them.

## Authorize the connection

```bash theme={null}
openclaw mcp login levios
```

Follow the authorization URL that OpenClaw prints. Sign in to levios, review the
permissions and Instagram accounts, then approve the request. OpenClaw captures
the credential automatically.

See [the OpenClaw MCP guide](https://docs.openclaw.ai/tools/mcp) for the current
configuration keys and per-agent routing.

## Verify access

Ask OpenClaw to list your levios accounts or automations. The result must
contain only accounts included in the grant. Tools that need permissions you did
not approve will not appear.

If the server has no tools, open **Settings > MCP** in levios and check its
status, permissions, and account access. Revoke the connection and start again
if you need to choose a different permission set.

Do not put an API key or bearer token in `headers`. The browser authorization
flow supplies the credential.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.