---
site: steel.dev
collection: docs
canonical_url: https://steel.dev/docs/integrations/opencode
markdown_url: https://steel.dev/docs/integrations/opencode.md
content_signal: ai-input=yes, ai-train=yes, search=yes
title: Connect OpenCode to Steel
description: Give OpenCode a cloud browser with the Steel CLI and its skills, or with the Steel MCP server.
summary: Give OpenCode a cloud browser with the Steel CLI and its skills, or with the Steel MCP server.
type: integration-guide
reviewed: 2026-11-16
prerequisites: []
related:
  - https://steel.dev/docs/integrations/claude-code.md
  - https://steel.dev/docs/integrations/codex.md
  - https://steel.dev/docs/integrations/cursor.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 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](https://steel.dev/docs/control/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](https://steel.dev/docs/control/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](https://opencode.ai/docs/).
- 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 OpenCode 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 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.

```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 OpenCode:

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

Restart 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](https://steel.dev/docs/control/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:

```sh
opencode mcp add steel --global --url https://mcp.steel.dev/mcp
```

Leave out `--global` to add the server to the current project only. Then sign in:

```sh
opencode mcp auth steel
```

On 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.

```sh
opencode mcp add steel --global --url https://mcp.steel.dev/mcp --header 'Authorization=Bearer {env:STEEL_API_KEY}'
```

[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 OpenCode a first task:

```text
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:

```text
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`.

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

## Next steps

- [MCP servers](https://opencode.ai/docs/mcp-servers/): How OpenCode adds, signs in to and lists MCP servers, in OpenCode's own docs.
- [MCP tools](https://steel.dev/docs/reference/mcp-tools): What each browser tool does when OpenCode calls it.
- [Skills](https://steel.dev/docs/control/skills): Add the skills that debug failed sessions and handle bot detection.
