Files
e2b-dev--e2b/apps/web
Tomas Valenta 1203ccbad3 Add MCP experimental feature to beta (#936)
<!-- CURSOR_SUMMARY -->
> [!NOTE]
> Adds beta MCP support to JS/Python SDKs with template auto-selection,
config POST, MCP URL helpers, and codegen for MCP types/schemas.
> 
> - **SDKs (Beta MCP support)**:
>   - **JS SDK**:
> - Add `McpServer` types and export; extend `Sandbox.betaCreate` with
`mcp` option that auto-selects `mcp-gateway-v0`, configures MCP via POST
`/config` on port `50005` with retries, and expose `betaGetMcpUrl()`.
> - Add `wait(ms)` util; generate MCP types from `spec/mcp-server.json`;
new `generate:mcp` script and dev dep `json-schema-to-typescript`.
>   - **Python SDK**:
> - Generate and export `McpServer` (TypedDict); extend sync/async
`beta_create` with `mcp` option, auto-select default MCP template, POST
MCP config with retries, and add `beta_get_mcp_url()`; define `mcp_port`
and `default_mcp_template`.
> - Makefile: add `generate-mcp` target; include
`datamodel-code-generator` in tooling; update lockfile/pyproject deps.
> - **Tooling**:
> - Add `spec/mcp-server.json` schema; update codegen Dockerfile to
install `datamodel-code-generator`.
> -
> 
> <sup>Written by [Cursor
Bugbot](https://cursor.com/dashboard?tab=bugbot) for commit
cf3f175d310d4c242cd2e867efd801f5c04f2099. This will update automatically
on new commits. Configure
[here](https://cursor.com/dashboard?tab=bugbot).</sup>
<!-- /CURSOR_SUMMARY -->

---------

Co-authored-by: Jonas Scholz <Jonas.Scholz@bbscholz.de>
2025-10-09 08:37:32 +00:00
..
2024-07-17 11:25:55 +02:00
2024-07-17 11:25:55 +02:00
2024-07-17 11:25:55 +02:00
2024-07-17 11:25:55 +02:00
2025-07-03 12:59:32 +02:00
2025-10-08 23:00:33 +00:00
2024-07-17 11:25:55 +02:00
2024-07-17 11:25:55 +02:00
2024-07-17 11:25:55 +02:00
2024-07-17 11:25:55 +02:00
2024-10-14 12:22:42 -07:00
2024-07-17 11:25:55 +02:00
2024-10-15 11:51:53 -07:00
2025-04-01 13:44:27 +02:00

E2B Web App

This repository contains E2B Dashboard, documentation, and SDK references.

SDK References

The SDK references are generated from the source code in the packages folder. Each package has its own SDK reference generator found in {package-dir}/scripts/generate_sdk_ref.sh, it generates markdown files with the following schema: ./src/app/(docs)/docs/sdk-reference/{package-name}/{version}/{module-name}/page.mdx.

When pushed to main, a github workflow checks for diffs in the packages folder, and if any are found, the SDK reference generator is run and the result is auto-commited the incoming branch.

Finally, when building or running the dev server, a prebuild step is run beforehand to generate the SDK reference TOCs and routes in the sdk-reference directory. This can also be run manually using npm run prebuild.

note: sometimes you may see uncommited changes or untracked files in the sdk-reference directory, this is fine and the files can be ignored.