run-code
Run code snippet and return the result.
LABSCO SUMMARY
One call sits between a snippet and the answer to what it actually prints.
The parameters are the code and its languageId — there is no session id, no working directory, no file handle — so each call stands alone and nothing you define in one is waiting in the next. That makes it a scratchpad for settling a question about behaviour, not a place to build something up across several steps.
What it is
A single-tool server that runs a code snippet in a named language and returns the result.
What you get
- A snippet executed and its result returned to the conversation
- The language chosen explicitly through languageId, rather than guessed from the code
- One entry point to reason about: what goes in is code, what comes back is what it printed
Requirements
Node.js to run the server, and the interpreter or compiler for every language you want to run, on your PATH: the server calls the one already installed and brings none of its own. Each call then takes the snippet and a languageId naming its language.
Setup effort
One command — npx -y mcp-server-code-runner
USE CASES
01
Settling what a snippet actually prints
Hand over the code with its languageId and read the result, instead of reasoning about the output and being wrong about an edge case.
1 tool
Counted once with only startup setup. Other versions, modes or optional credentials may expose a different list.
BEFORE YOU INSTALL
What to know first
Tools you get
1 tool when we connected.
Requires
- npx on PATH
- The interpreter or compiler for each language you want to run, on PATH
CONTEXT COST
Light Standing cost
Rated by the size of the one tool definition that rides along on every turn
INSTALLATION
Connect your client
Add the block to your client, or run the command directly.
Server setup
Configuration file
JSON
{
"mcpServers": {
"mcp-server-code-runner": {
"command": "npx",
"args": [
"-y",
"mcp-server-code-runner"
]
}
}
}npx
TERMINAL
npx -y mcp-server-code-runner
