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

# Claude Code

> Connect pwno-mcp to Claude Code over HTTP or stdio.

Claude Code supports both remote HTTP MCP servers and local stdio MCP servers.

<Info>
  HTTP is usually the better default for Claude Code because the server stays running independently of the client process.
</Info>

Start `pwno-mcp` in HTTP mode if you want Claude Code to connect to a long-running server.

Use stdio if you want Claude Code to spawn Docker directly and keep the MCP definition project-local in `.mcp.json`.

<CodeGroup>
  ```bash HTTP theme={null}
  claude mcp add --transport http --scope project pwno-mcp http://127.0.0.1:5500/mcp
  ```

  ```bash stdio theme={null}
  claude mcp add --transport stdio --scope project pwno-mcp -- \
    docker run --rm -i \
      --cap-add=SYS_PTRACE \
      --cap-add=SYS_ADMIN \
      --security-opt seccomp=unconfined \
      --security-opt apparmor=unconfined \
      -v "/ABSOLUTE/PATH/TO/YOUR/PROJECT/workspace:/workspace" \
      ghcr.io/pwno-io/pwno-mcp:latest \
      --stdio
  ```
</CodeGroup>

After HTTP setup, run `/mcp` in Claude Code to confirm the server is connected.

## Helpful commands

```bash theme={null}
claude mcp list
claude mcp get pwno-mcp
```

<Check>
  After setup, run `/mcp` in Claude Code and confirm that `pwno-mcp` appears as a connected server.
</Check>