declaw-mcp-server
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| DECLAW_DOMAIN | No | Custom API domain (for on-prem deployments) | |
| DECLAW_API_KEY | Yes | Your Declaw API key |
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 | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| create_sandboxB | Create a new secure sandbox environment. Returns a sandbox_id to use with other tools. |
| kill_sandboxA | Destroy a sandbox and release its resources. |
| list_sandboxesA | List all active sandboxes for the current API key. |
| run_commandA | Execute a shell command inside a sandbox. Returns stdout, stderr, and exit code. |
| read_fileB | Read a text file from a sandbox. |
| write_fileA | Write text content to a file in a sandbox. Creates parent directories automatically. |
| list_filesA | List files and directories at a given path in a sandbox. |
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 7 tools
Each tool has a clearly distinct purpose: sandbox lifecycle (create, kill, list) versus in-sandbox operations (run command, read/write file, list files). No overlapping functionality.
All tools follow a consistent verb_noun snake_case pattern (create_sandbox, kill_sandbox, run_command, read_file, etc.), with predictable alignment between verbs and actions.
Seven tools is well-scoped for a sandbox server, covering both lifecycle management and common file/command operations without redundancy or bloat.
Core lifecycle and file operations are covered, but there is no file delete or directory removal tool, which would be a natural expectation for file management in a sandbox.