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

# Connect your AI tool

> Give Claude Code, Codex, Cursor, VS Code or any MCP client access to your Cyberwave workspace with the hosted MCP server and the Cyberwave skill.

Connect your coding agent once and it can build environments, control twins and draft workflows in your workspace. Two pieces do the work:

* **The MCP server** gives the agent typed Cyberwave tools. It is hosted at `https://mcp.cyberwave.com/mcp`.
* **The Cyberwave skill** teaches the agent when to use MCP, the CLI or the SDK, and the safety rules for robot control. Install it in clients that support skills.

**Needs:** a Cyberwave API key scoped to one workspace ([create one](https://docs.cyberwave.com/get-started/account.md)), exported as `CYBERWAVE_API_KEY`. The skill install needs Git.

## Set up your client

**Claude Code**

```bash theme={null}
git clone https://github.com/cyberwave-os/cyberwave-skill ~/.claude/skills/cyberwave
claude mcp add --scope user --transport http cyberwave https://mcp.cyberwave.com/mcp \
  --header "Authorization: Bearer $CYBERWAVE_API_KEY"
claude
```

Then invoke `/cyberwave`. Claude stores the expanded header in its user configuration.

**Codex**

```bash theme={null}
git clone https://github.com/cyberwave-os/cyberwave-skill ~/.agents/skills/cyberwave
codex mcp add cyberwave --url https://mcp.cyberwave.com/mcp \
  --bearer-token-env-var CYBERWAVE_API_KEY
codex
```

Start Codex from the terminal where you exported the key, then invoke `$cyberwave`.

**Cursor**

Add to your Cursor `mcp.json`:

```json theme={null}
{
  "mcpServers": {
    "cyberwave": {
      "url": "https://mcp.cyberwave.com/mcp",
      "headers": { "Authorization": "Bearer <CYBERWAVE_API_KEY>" }
    }
  }
}
```

**VS Code**

Add to `settings.json`, then restart VS Code with `CYBERWAVE_API_KEY` set:

```json theme={null}
{
  "mcp": {
    "servers": {
      "cyberwave": {
        "url": "https://mcp.cyberwave.com/mcp",
        "headers": { "Authorization": "Bearer ${env:CYBERWAVE_API_KEY}" }
      }
    }
  }
}
```

**Gemini CLI**

```bash theme={null}
gemini mcp add -t http cyberwave https://mcp.cyberwave.com/mcp \
  --header "Authorization: Bearer $CYBERWAVE_API_KEY"
```

**Other MCP clients**

Add a **Streamable HTTP** server named `cyberwave` at `https://mcp.cyberwave.com/mcp`. Put `Bearer <your key>` in its `Authorization` header, using the client's private credential field, then reconnect. If your client can't send a header, use one of the other tabs.

> [!NOTE]
>
> `cyberwave login` configures the CLI only. It does not configure an MCP client.

## Verify the connection

Ask your agent:

```text theme={null}
List my Cyberwave workspaces using the Cyberwave MCP tools.
```

A tool response that names your workspace means you're connected.

> **401 or AUTH\_ERROR**
>
> The key is wrong or revoked. Create a new key and update the client's credential.

> **The Cyberwave tools don't appear**
>
> Reconnect the MCP server in your client and restart the agent session.

> **workspace\_required**
>
> The key covers several workspaces. Create a key scoped to one workspace.

> **The skill folder already exists**
>
> Reuse it, or update it with `git -C ~/.claude/skills/cyberwave pull`.

## Next steps

> **[Prompt library](https://docs.cyberwave.com/ai/prompt-library.md)**
>
> Prompts for scenes, control and workflows.

> **[Agent safety and approval](https://docs.cyberwave.com/ai/safety.md)**
>
> How plans, approval and limits keep robots safe.

> **[MCP tools reference](https://docs.cyberwave.com/overview/tools/mcp-server.md)**
>
> Every tool, resource and deployment option.


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