cinch-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| CINCH_API_KEY | Yes | Your Cinch API key. | |
| CINCH_BASE_URL | No | Override the API endpoint. | https://api.cinch.codes |
| CINCH_TIMEOUT_MS | No | Client-side timeout in ms. The API caps execution at 10s regardless. | 20000 |
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 |
|---|---|
| execute_codeA | Execute Python or JavaScript in a secure, isolated, disposable sandbox and return its output. The sandbox is a gVisor-isolated container on Cinch's infrastructure with no access to the user's machine, filesystem, or network, so it is safe to run code you generated yourself, code from an untrusted source, or code whose behaviour you are unsure about. Use it whenever running code gives a more reliable answer than reasoning about it: checking a script works, exact calculations, parsing or transforming data, testing a regex, verifying language behaviour. The environment is deliberately minimal. Read these limits before writing code:
|
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
Only one tool exists, so there is no possibility of confusing it with others. The tool's purpose is clearly stated, making selection unambiguous.
The single tool name 'execute_code' follows a clear verb_noun pattern and accurately reflects its function. Consistency is trivially maintained.
At one tool, the server is minimal but appropriate for its narrow purpose of code execution. It is not a trivial tool, and no additional tools seem necessary for the described sandbox functionality.
The server fully covers its stated domain: executing Python and JavaScript in a sandbox. All necessary parameters and constraints are documented, and there are no obvious missing operations for this focused use case.