Skip to content

Connect Claude to Steel

Set up your agent

Give your coding agent a Steel browser and the Steel skills, so that it browses and writes Steel code the right way. Learn more

Install the Steel CLI. It signs you in and installs the skills for your coding agents.

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

Or send this prompt to your coding agent, and it does the same:

Read https://setup.steel.dev/install.md and follow it to set up Steel for this coding client.
Then continue my requested task using the installed Steel skill.

Set up your agent →

Claude can drive a Steel cloud browser in a chat, and you write no code. It opens pages, reads them, clicks, types and fills forms, and you can watch each session live. Claude on the web and in the desktop app cannot run shell commands, so it uses Steel's hosted MCP server. You add one URL as a custom connector and sign in. Setup takes a few minutes.

Claude Code runs shell commands, so it fits the Steel CLI better. See Connect Claude Code to Steel.

Before you begin

  • A Steel account. Sign up at app.steel.dev.
  • Claude on the web or the Claude desktop app.

Set up the integration

Add the MCP server

The server URL is https://mcp.steel.dev/mcp. To add it to Claude, on the web or in the desktop app:

  1. Go to Customize > Connectors, click + Add, and then click Add custom connector.
  2. Enter Steel as the name and https://mcp.steel.dev/mcp as the server URL, and click Continue.
  3. Under Authentication, choose Sign in now. Under OAuth client, keep Use Claude's published identity. Click Add.
  4. Sign in to Steel. The sign-in page asks for your organization and one project. The sessions that Claude creates run in that project. If your organization requires two-step verification, set it up before you sign in.

In a chat, turn the connector on from the + button, under Connectors. On Team and Enterprise, an owner adds the connector in Organization settings > Connectors, and each member clicks Connect on it. Get started with custom connectors in the Claude Help Center has the details.

Another client that supports remote MCP servers over Streamable HTTP adds the same URL in its own settings for MCP servers. For an agent that runs without a person, such as in CI, the client can send an API key instead of the sign-in. MCP server shows how, and it lists what the server does.

Watch Claude browse

Send Claude this prompt:

Use Steel to open a browser, send me the live view link, and wait until I say I'm watching. Then open https://steel.dev/practice/news, list the top 3 stories, and stop the session.

Claude creates a session with session_create, whose result has the live view link, and the browser shows live in the conversation. In another client, open the link in a browser where you are signed in to Steel. Tell Claude that you are watching. You see the page open and Claude read it, and Claude then lists the stories and releases the session. After the release, the same link replays the session.

Ask Claude to release each session when the task is done. Set timeouts says when a session that Claude leaves open ends.

Next steps