We manage OAuth, API Key, token refresh, and scopes, you just build.
Try for FreeThis guide explains how to connect E2b MCP to OpenCode using Composio Connect, which simplifies OAuth, API changes, and reliability concerns.
There are two ways to set this up:
Composio provides a single MCP server or CLI tool that exposes a set of meta-tools, allowing you to:
Install the Composio CLI, authenticate, and initialize your project:
During login, you will be redirected to the sign-in page. Finish the flow and you are all set.
Once the CLI is installed, it is essentially done. Give OpenCode access to your apps with these steps:
You can also connect E2b to OpenCode by adding Composio as an MCP server through the OpenCode CLI.
This launches an interactive prompt.
| Field | Value |
|---|---|
| Name | composio |
| Type | remote |
| URL | https://connect.composio.dev/mcp |
| Require OAuth | Yes |
| Have client ID | No |
Alternatively, you can skip the interactive prompt and paste the configuration directly into your OpenCode config file.
Open your global OpenCode config:
Add this under the mcp key and save the file.
Authenticate the Composio MCP server you just added:
This opens a browser session. Authorize Composio and you are done.
Now, in the chat, ask the agent to connect to E2b or give it any E2b-related task.
For example, ask it to:
It will prompt you to authenticate and authorize access to E2b.
That is it. Composio tools are now available in OpenCode, and your E2b account is ready to use.
Now that E2b is connected, extend your setup by connecting the other apps you already use every day, so your agent can run true cross-app workflows end to end.
Start with one workflow you do repeatedly, then keep adding apps as you find new handoffs. With everything behind a single MCP endpoint, your agent can coordinate multiple tools safely and reliably in one conversation.
