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 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 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.
- A Steel account. The CLI or the MCP server signs you in with it.
- A project key in the
STEEL_API_KEYenvironment variable, if Claude Code runs unattended. See 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 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.
curl -fsS https://setup.steel.dev | shIf you skipped the sign-in, run steel login.
If steel init did not install the steel-browser skill, install it for Claude Code:
npx skills add steel-dev/skills --skill steel-browser -a claude-code -gYou can also install it from Claude Code's plugin manager. Run these commands in Claude Code:
/plugin marketplace add steel-dev/skills
/plugin install steel-browser@steel-skillsRestart Claude Code so that it finds the new skill. To have Claude Code write Steel code, add the steel-developer skill too. 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:
claude mcp add --transport http steel https://mcp.steel.dev/mcpBy 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.
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 explains the sign-in, projects and tools.
Check the connection
With the CLI, check the skill and CLI first:
steel skills doctor
steel scrape https://example.comsteel scrape prints the page as Markdown. Then send Claude Code a first task:
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:
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.