---
site: steel.dev
collection: docs
canonical_url: https://steel.dev/docs/integrations/claude-code
markdown_url: https://steel.dev/docs/integrations/claude-code.md
content_signal: ai-input=yes, ai-train=yes, search=yes
title: Connect Claude Code to Steel
description: Give Claude Code a cloud browser with the Steel CLI and its skills, or with the Steel MCP server.
summary: Give Claude Code a cloud browser with the Steel CLI and its skills, or with the Steel MCP server.
type: integration-guide
reviewed: 2026-11-12
prerequisites: []
related:
  - https://steel.dev/docs/integrations/codex.md
  - https://steel.dev/docs/integrations/cursor.md
  - https://steel.dev/docs/integrations/opencode.md
  - https://steel.dev/docs/integrations/pi.md
  - https://steel.dev/docs/integrations/claude.md
agent_setup: https://setup.steel.dev/install.md
docs_index: https://steel.dev/docs/sitemap.md
---

# Connect Claude Code to Steel

Claude Code can open pages, click, type and fill forms in a Steel session. Claude Code runs shell commands, so give it the [Steel CLI](https://steel.dev/docs/control/cli) and the `steel-browser` skill, and it runs `steel` commands in its shell. If Claude Code cannot run the `steel` command, for example on Windows without WSL, add the Steel [MCP server](https://steel.dev/docs/control/mcp-server) instead. It gives Claude Code browser tools, and Steel hosts it, so there is nothing to install. Your Claude Code permission settings decide whether it asks before it runs a shell command.

## Before you begin

- Claude Code, installed on your machine. See the [Claude Code overview](https://code.claude.com/docs/en/overview).
- A Steel account. The CLI or the MCP server signs you in with it.
- A project key in the `STEEL_API_KEY` environment variable, if Claude Code runs unattended. See [API keys](https://steel.dev/docs/account/api-keys).
- For the Steel CLI, macOS or Linux. On Windows, use WSL.
- Node.js 22.20 or later, for the skills installer.

## Set up the integration

### Install the CLI and the skill

The prompt in [Set up your agent](https://steel.dev/docs/get-started/agent-setup#1-send-the-setup-prompt) does this step for you: send it to Claude Code, and it installs the CLI and the `steel-browser` skill and signs you in. To do it yourself, install the Steel CLI. In an interactive terminal, the installer then runs `steel init`, which signs you in and installs skills for coding agents.

```sh
curl -fsS https://setup.steel.dev | sh
```

If you skipped the sign-in, run `steel login`.

If `steel init` did not install the `steel-browser` skill, install it for Claude Code:

```sh
npx skills add steel-dev/skills --skill steel-browser -a claude-code -g
```

You can also install it from Claude Code's plugin manager. Run these commands in Claude Code:

```text
/plugin marketplace add steel-dev/skills
/plugin install steel-browser@steel-skills
```

Restart Claude Code so that it finds the new skill. To have Claude Code write Steel code, add the `steel-developer` skill too. [Skills](https://steel.dev/docs/control/skills) lists every skill.

### Add the MCP server

Use the MCP server instead of the CLI when Claude Code cannot run the `steel` command. Run this command in your project's folder:

```sh
claude mcp add --transport http steel https://mcp.steel.dev/mcp
```

By default, Claude Code adds the server in the local scope, so it loads only in this project. To use Steel in every project, add `--scope user` to the command.

Then run `/mcp` in Claude Code and sign in to `steel`. On the Steel sign-in page, pick the organization and project. The sessions that Claude Code creates run in that project.

To skip the sign-in, for example in CI, send a project key as a bearer token. Sessions then run in the key's project. An organization key does not work, because it is not bound to a project.

```sh
claude mcp add --transport http steel https://mcp.steel.dev/mcp \
  --header "Authorization: Bearer $STEEL_API_KEY"
```

Your shell puts the key's value into the command, so Claude Code saves the key in plain text in its configuration, `~/.claude.json`. That file is in your home directory, not in your project. Do not add `--scope project`, which writes the key to `.mcp.json` in your project, where it can be committed.

[MCP server](https://steel.dev/docs/control/mcp-server) explains the sign-in, projects and tools.

### Check the connection

With the CLI, check the skill and CLI first:

```sh
steel skills doctor
steel scrape https://example.com
```

`steel scrape` prints the page as Markdown. Then send Claude Code a first task:

```text
Use Steel to open example.com in a browser, report its title, and stop the session when finished.
```

Claude Code reports the title **Example Domain**.

With the MCP server, send Claude Code a prompt that needs a browser:

```text
Use Steel to open news.ycombinator.com and list the top five stories.
```

Claude Code calls the Steel tools and lists the stories. When it starts a session, the result has a link to watch the session live, in the form `https://app.steel.dev/sessions/SESSION_ID`.

> **Warning**
>
> A session costs browser time until it is released or it times out. Ask Claude Code to release each session when the task is done.

## Next steps

- [Claude Code overview](https://code.claude.com/docs/en/overview): Install Claude Code and learn how it works.
- [MCP tools](https://steel.dev/docs/reference/mcp-tools): The tools that Claude Code calls, such as `session_create`, `snapshot` and `click`.
- [Give Claude Code a real browser](https://steel.dev/blog/give-claude-code-a-real-browser): Claude Code works in Gmail with the CLI and the `steel-browser` skill, then turns the run into a script.
