How to connect E2b MCP with VS Code

How to connect E2b MCP with VS Code VS Code is the most popular code editor out there. With its recent AI makeover, it can do more than just help you write code. You can connect your applications to it and let LLMs automate many of the mundane tasks in your workflow. In this guide, I will explain how to connect E2b with VS Code in the most secure and robust way possible via Composio.

E2b logoE2b
Api Key

E2b is an open-source platform for running code in secure, sandboxed environments. It enables safe multi-language code execution for AI-powered apps.

27 Tools

How to connect E2b MCP with VS Code

VS Code is the most popular code editor out there. With its recent AI makeover, it can do more than just help you write code. You can connect your applications to it and let LLMs automate many of the mundane tasks in your workflow.

In this guide, I will explain how to connect E2b with VS Code in the most secure and robust way possible via Composio.

Also integrate E2b with

Why use Composio?

Composio provides:

  • Access to 1,000+ managed apps from a single MCP endpoint. This makes it convenient for agents to run cross-app workflows.
  • Programmatic tool calling. Allows LLMs to write its code in a remote workbench to handle complex tool chaining. Reduces to-and-fro with LLMs for frequent tool calling.
  • Large tool response handling outside the LLM context. This minimizes context bloat from large tool responses.
  • Dynamic just-in-time access to thousands of tools across hundreds of apps. Composio loads the tools your agent needs, so LLMs are not overwhelmed by tools they do not need.

Integrate E2b MCP with VS Code

1. Install with one click

Click the button below to add Composio to VS Code. You will be prompted to authorize. This requires VS Code 1.99+ with GitHub Copilot.

+Install in VS Code

2. Or add manually

Open or create .vscode/mcp.json in your project root and add the following configuration:

bash
{
  "servers": {
    "composio": {
      "type": "http",
      "url": "https://connect.composio.dev/mcp"
    }
  }
}

3. Authorize

Click the install button to authorize VS Code to connect to Composio. VS Code will detect OAuth and prompt you to sign in.

VS Code MCP server install screen for Composio

A browser window will open to authorize.

Composio authorization browser window

4. Authenticate E2b and start working

Back in VS Code chat, ask the agent to connect to E2b or give it any E2b-related task.

For example, ask it to:

  • "Run a Python script to analyze CSV data"
  • "Execute JavaScript code to validate user input"
  • "Start a sandbox and list installed packages"

It will prompt you to authenticate and authorize access to E2b.

That is it. Composio tools are now available in VS Code, and your E2b account is ready to use.

Way Forward

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.

  • Connect Calendar to turn threads into scheduled meetings automatically.
  • Connect Slack or Teams to post summaries, approvals, and alerts where your team works.
  • Connect Notion, Linear, Jira, or Asana to convert requests into tickets, tasks, and docs.
  • Connect Drive, Dropbox, or OneDrive to fetch, file, and share attachments without manual steps.
  • Connect HubSpot or Salesforce to log customer context, update records, and draft follow-ups.

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.

TOOLS

Supported Tools

Every E2b action and event your agent gets out of the box.

Connect to Sandbox

Tool to connect to an existing E2B sandbox and retrieve its details.

Create Template

Tool to create a new E2B template with specified configuration.

Create Webhook

Tool to register a new webhook to receive sandbox lifecycle events for the team.

Delete Sandbox

Tool to terminate and permanently delete a running E2B sandbox instance.

Delete Webhook

Tool to unregister a webhook and stop receiving lifecycle events.

Check API Health

Tool to check the health status of the E2B API.

Get Sandbox

Tool to retrieve detailed information about a specific sandbox by its ID.

Get Sandbox Logs

Tool to retrieve logs from a specific E2B sandbox instance.

Get Sandbox Lifecycle Events

Tool to retrieve the latest lifecycle events for a particular sandbox instance.

Get Sandbox Metrics

Tool to retrieve timestamped CPU, memory, and disk usage metrics for a sandbox.

Get Team Metrics

Tool to retrieve timestamped CPU, memory, and disk usage metrics for a team.

Get Team Maximum Metrics

Tool to retrieve the maximum value for a specific team metric in a given interval.

Get Template Build Status

Tool to get the status of a template build.

Get Template Files

Tool to get an upload link for a tar file containing build layer files.

Get Webhook Configuration

Tool to retrieve the current webhook configuration for a specific webhook.

List All Sandboxes

Tool to list all running and paused sandboxes associated with your team.

List Sandboxes Metrics

Tool to retrieve timestamped CPU, memory, and disk usage metrics for multiple sandboxes.

List Team Sandbox Lifecycle Events

Tool to retrieve the latest lifecycle events across all sandboxes associated with the team.

List All Templates

Tool to list all available E2B templates for your team.

List All Webhooks

Tool to retrieve all registered webhooks for your team.

Pause Sandbox

Tool to pause a running E2B sandbox preserving its filesystem and memory state.

Create Sandbox

Tool to create a new E2B sandbox from a template.

Set Sandbox Timeout

Tool to set the timeout for an E2B sandbox.

Refresh Sandbox

Tool to refresh an E2B sandbox and extend its time to live.

Start Template Build

Tool to start a build for an E2B template.

Update Template

Tool to update an E2B template configuration.

Update Webhook Configuration

Tool to update an existing webhook configuration including URL, enabled status, and subscribed events.

FAQ

Frequently asked questions

With a standalone E2b MCP server, the agents and LLMs can only access a fixed set of E2b tools tied to that server. However, with the Composio Tool Router, agents can dynamically load tools from E2b and many other apps based on the task at hand, all through a single MCP endpoint.

Yes, you can. VS Code fully supports MCP integration. You get structured tool calling, message history handling, and model orchestration while Tool Router takes care of discovering and serving the right E2b tools.

Yes, absolutely. You can configure which E2b scopes and actions are allowed when connecting your account to Composio. You can also bring your own OAuth credentials or API configuration so you keep full control over what the agent can do.

All sensitive data such as tokens, keys, and configuration is fully encrypted at rest and in transit. Composio is SOC 2 Type 2 compliant and follows strict security practices so your E2b data and credentials are handled as safely as possible.

Start with E2b.It takes 30 seconds.

Managed auth, hosted MCP servers, and every E2b tool your agent needs.Free to start.

Start building