You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
This is a simple MCP-based interface for a sandboxed development environment.
4
+
5
+
## Local dev
6
+
7
+
Cloudchamber local dev isn't implemented yet, so we are doing a bit of a hack to just run the server in your local environment. Because of this, testing the container(s) and container manager locally is not possible at this time.
8
+
9
+
Do the following from within the sandbox-container app:
10
+
11
+
1. Copy the `.dev.vars.example` file to a new `.dev.vars` file.
12
+
2. Get the Cloudflare client id and secret from a team member and add them to the `.dev.vars` file.
13
+
3. Run `pnpm i` then `pnpm dev` to start the MCP server.
14
+
4. Run `pnpx @modelcontextprotocol/inspector` to start the MCP inspector client.
15
+
5. Open the inspector client in your browser and connect to the server via `http://localhost:8976/sse`.
16
+
17
+
Note: Temporary files created through files tool calls are stored in the workdir folder of this app.
This is a simple MCP-based interface for a sandboxed development environment.
3
+
This is a [Model Context Protocol (MCP)](https://modelcontextprotocol.io/introduction) server that supports remote MCP connections, with Cloudflare OAuth built-in.
4
4
5
-
## Local dev
5
+
It integrates tools for running a sandbox container with your MCP client. With this server you can allow your LLM to run arbitrary code, such as Node or Python, in a secure, sandboxed environment.
6
6
7
-
Cloudchamber local dev isn't implemented yet, so we are doing a bit of a hack to just run the server in your local environment. Because of this, testing the container(s) and container manager locally is not possible at this time.
7
+
## Tools
8
8
9
-
Do the following from within the sandbox-container app:
|**Container Lifecycle**|`container_initialize`| (Re)start a container. Containers are intended to be ephemeral and don't save any state. Containers are only guaranteed to last ~10m.|
12
+
||`container_ping`| Ping a container for connectivity |
13
+
|**Filesystem**|`container_file_write`| Write to a file |
14
+
||`container_files_list`| List all files in the work directory |
15
+
||`container_file_read`| Read the contents of a single file or directory |
16
+
||`container_file_delete`| Delete a single file or directory |
17
+
|**Execution**|`container_exec`| Run a command in the shell |
10
18
11
-
1. Copy the `.dev.vars.example` file to a new `.dev.vars` file.
12
-
2. Get the Cloudflare client id and secret from a team member and add them to the `.dev.vars` file.
13
-
3. Run `pnpm i` then `pnpm dev` to start the MCP server.
14
-
4. Run `pnpx @modelcontextprotocol/inspector` to start the MCP inspector client.
15
-
5. Open the inspector client in your browser and connect to the server via `http://localhost:8976/sse`.
19
+
This MCP server is still a work in progress, and we plan to add more tools in the future.
16
20
17
-
Note: Temporary files created through files tool calls are stored in the workdir folder of this app.
18
21
19
-
##Deploying
22
+
### Prompt Examples
20
23
21
-
1. Make sure the docker daemon is running
24
+
-`Create a visualization using matplotlib. Run it in the container that you can start`
25
+
-`Clone and explore this github repo: [repo link]. Setup and run the tests in your development environment`
26
+
-`Analyze this data using Python`
22
27
23
-
2. Disable WARP and run
28
+
## Access the remote MCP server from from any MCP Client
If your MCP client has first class support for remote MCP servers, the client will provide a way to accept the server URL (`https://bindings.mcp.cloudflare.com`) directly within its interface (for example in [Cloudflare AI Playground](https://playground.ai.cloudflare.com/)).
28
31
29
-
3. Add to your Claude config. If using with Claude, you'll need to disable WARP:
32
+
If your client does not yet support remote MCP servers, you will need to set up its respective configuration file using [mcp-remote](https://www.npmjs.com/package/mcp-remote) to specify which servers your client can access.
30
33
31
-
```
34
+
Replace the content with the following configuration:
-`container_initialize`: (Re)start a container. Containers are intended to be ephemeral and don't save any state. Containers are only guaranteed to last 10m (this is just because I have a max of like ~5 containers per account).
49
-
-`container_ping`: Ping a container for connectivity
50
-
-`container_exec`: Run a command in the shell
51
-
-`container_file_write`: Write to a file
52
-
-`container_files_list`: List all files in the work directory
53
-
-`container_file_read`: Read the contents of a single file or directory
54
-
-`container_file_delete`: Delete a single file or directory
55
-
56
-
## Resources
57
-
58
-
TODO
59
-
60
-
Tried implementing these, but MCP clients don't support resources well at all.
61
-
62
-
## Prompts
63
-
64
-
TODO
65
-
66
-
## Container support
47
+
Once you've set up your configuration file, restart MCP client and a browser window will open showing your OAuth login page. Proceed through the authentication flow to grant the client access to your MCP server. After you grant access, the tools will become available for you to use.
67
48
68
-
The container currently runs python and node. It's connected to the internet and LLMs can install whatever packages.
49
+
Interested in contributing, and running this server locally? See [CONTRIBUTING.md](CONTRIBUTING.md) to get started.
this.server.tool('container_files_list','List working directory file tree. This just reads the contents of the current working directory',{},async({})=>{
110
-
// Begin workaround using container read rather than ls:
'Read a specific file or directory. Use this tool if you would like to read files or display them to the user. This allow you to get a displayable image for the user if there is an image file.',
0 commit comments