Connect OpenCode to Steel
OpenCode can open pages, click, type and fill forms in a Steel session. OpenCode runs shell commands, so give it the Steel CLI and the steel-browser skill, and it runs steel commands in its shell. If OpenCode cannot run the steel command, for example on Windows without WSL, add the Steel MCP server instead. It gives OpenCode browser tools, and Steel hosts it, so there is nothing to install.
Before you begin
- OpenCode, installed on your machine. See the OpenCode docs.
- A Steel account. The CLI or the MCP server signs you in with it.
- A project key in the
STEEL_API_KEYenvironment variable, if OpenCode 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 OpenCode, 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 OpenCode:
npx skills add steel-dev/skills --skill steel-browser -a opencode -gRestart OpenCode so that it finds the new skill. steel skills paths shows where each skill is installed. To have OpenCode 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 OpenCode cannot run the steel command. Add the server for every project:
opencode mcp add steel --global --url https://mcp.steel.dev/mcpLeave out --global to add the server to the current project only. Then sign in:
opencode mcp auth steelOn the Steel sign-in page, pick the organization and project. The sessions that OpenCode creates run in that project. opencode mcp list shows whether the server is connected.
To skip the sign-in, for example in CI, have OpenCode send a project key as a bearer token. OpenCode reads the key from STEEL_API_KEY when it connects. Sessions then run in the key's project.
opencode mcp add steel --global --url https://mcp.steel.dev/mcp --header 'Authorization=Bearer {env:STEEL_API_KEY}'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 OpenCode a first task:
Use Steel to open example.com in a browser, report its title, and stop the session when finished.OpenCode reports the title Example Domain.
With the MCP server, send OpenCode a prompt that needs a browser:
Use Steel to open news.ycombinator.com and list the top five stories.OpenCode 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.