foundry-sandbox-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
| logging | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| forge_testA | 在 Docker 容器中运行 forge test 命令。每次测试时创建新容器，测试完成后自动清理，确保全新环境。运行测试前会根据依赖清单文件自动安装依赖。 |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 1 tool
With only a single tool, there is no possibility of confusion or overlap; the purpose is entirely distinct.
The single tool name 'forge_test' follows a consistent verb_noun pattern, which is as consistent as possible with one tool.
The server has only 1 tool, which is borderline for a typical MCP server; more tools would be expected for a sandbox environment.
The server only provides a test runner, missing essential operations like compilation or deployment, leaving significant gaps for a Foundry sandbox.