piston-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 | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| run_codeB | Runs given code in the given language in the Piston remote code execution engine. Parameterslanguage: str Programming language to run code in. code : str Code to run. Returnstr Output of code execution. |
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 ambiguity or overlap with other tools.
With a single tool named 'run_code', the naming is consistent and follows a clear verb_noun pattern.
A single tool is borderline for a code execution server; it may be sufficient but feels thin compared to typical implementations that also expose language listing or version info.
The server only provides code execution but lacks essential operations like listing supported languages, which agents would likely need to use the server effectively.