mcp-server-code-runner
Servidor MCP de Code Runner
Servidor MCP para ejecutar fragmentos de código y mostrar el resultado.
Admite la ejecución de múltiples lenguajes de programación: JavaScript, PHP, Python, Perl, Perl 6, Ruby, Go, Lua, Groovy, PowerShell, BAT/CMD, BASH/SH, F# Script, C# Script, VBScript, TypeScript, CoffeeScript, Scala, Swift, Julia, Crystal, OCaml Script, R, AppleScript, Elixir, Clojure, Racket, Scheme, AutoHotkey, AutoIt, Kotlin Script, Dart, Haskell, Ni, Lisp, Kit, V, SCSS, Sass . La lista completa se puede consultar aquí en constants.ts .
Configuración
npx para VS Code
Instale el servidor Code Runner MCP en VS Code usando los siguientes botones:
Alternativamente, puede agregar la configuración en settings.json :
{
"mcp": {
"inputs": [],
"servers": {
"mcp-server-code-runner": {
"command": "npx",
"args": [
"-y",
"mcp-server-code-runner@latest"
],
}
}
}
}npx para Claude Desktop
Configuración en claude_desktop_config.json :
{
"mcpServers": {
"mcp-server-code-runner": {
"command": "npx",
"args": [
"-y",
"mcp-server-code-runner@latest"
],
}
}
}Estibador
Utilice VS Code como ejemplo. Instale el servidor MCP de Code Runner en VS Code usando los siguientes botones:
Alternativamente, puede agregar la configuración en settings.json :
{
"mcp": {
"inputs": [],
"servers": {
"mcp-server-code-runner": {
"command": "docker",
"args": [
"run",
"--rm",
"-i",
"formulahendry/mcp-server-code-runner"
]
}
}
}
}Problema con npx en Windows
En Windows, es posible que los servidores MCP no puedan conectarse con npx .
Puedes probar las dos soluciones alternativas siguientes:
usar bunx
Instalar Bun .
En la configuración, cambie
npxporbunx.
usar cmd
A continuación se muestra la configuración de VS Code en settings.json :
{
"mcp": {
"inputs": [],
"servers": {
"mcp-server-code-runner": {
"command": "cmd",
"args": [
"/c",
"npx",
"-y",
"mcp-server-code-runner@latest"
],
}
}
}
}Related MCP server: MCP Expr Lang
Ejecutar contransporte HTTP Streamable
npm install -g mcp-server-code-runner@latest
mcp-server-code-runner --transport httpUso
Antes de utilizar Code Runner MCP Server, asegúrese de que el intérprete o compilador del lenguaje de programación que desea ejecutar esté configurado en la variable de entorno PATH .
Pruebe las siguientes indicaciones en la aplicación que ha configurado Code Runner MCP Server:
Run the JavaScript Code: console.log(5+6)Where is temporary folder in my OS? Use run-code toolHow many CPUs do I have in my machine? Use run-code tool


Construye tu propio servidor MCP
¿Quieres crear tu propio servidor MCP? ¡Prueba el Generador Yeoman para Servidor MCP y crea tu proyecto!
Available Tools
1 toolrun-codeC
Run code snippet and return the result.
| Name | Required | Description | Default |
|---|---|---|---|
| code | Yes | Code Snippet | |
| languageId | Yes | Language ID |
TDQS
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description carries the full burden of behavioral disclosure. It mentions running code and returning results but lacks critical details like execution environment, security implications, timeout limits, error handling, or resource constraints, which are essential for safe and effective use.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single, efficient sentence that front-loads the core purpose without unnecessary words. It is appropriately sized for the tool's function, making it highly concise and well-structured.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the complexity of code execution (which involves security, performance, and error handling), the description is insufficient. With no annotations, no output schema, and minimal behavioral details, it fails to provide complete context for safe and informed use, especially for a tool that could have significant side effects.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The description does not add meaning beyond the input schema, which has 100% coverage with clear descriptions for both parameters (code and languageId). Since the schema fully documents the parameters, the baseline score of 3 is appropriate, as the description provides no additional semantic context.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description 'Run code snippet and return the result' clearly states the action (run) and resource (code snippet) with a specific outcome (return result). It distinguishes the tool's function effectively, though it lacks sibling differentiation since no sibling tools exist, making a 5 unnecessary.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description provides no guidance on when to use this tool, such as for testing, debugging, or specific contexts, and offers no alternatives or exclusions. It only states what the tool does without usage context, leaving the agent to infer applicability.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections. Dates show when Glama detected each change.
1 tool update
- First observed
run-code
TDQS
With only one tool, there is no possibility of ambiguity or overlap between tools. The tool 'run-code' has a clearly distinct and singular purpose.
The single tool name 'run-code' follows a clear verb_noun pattern. Since there is only one tool, consistency is inherently perfect with no deviations.
A single tool for a code runner server feels thin and limited in scope. It suggests the server may not fully cover the domain, as typical code execution might benefit from additional tools like listing environments or managing sessions.
The tool surface is severely incomplete for a code runner domain. It only provides execution without supporting operations like listing available languages, checking code syntax, or managing execution environments, which are common in such contexts.
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Related MCP Connectors
MCP server to assist with JxBrowser development.
MCP server for understanding Javascript internals from ECMAScript specification.
Related MCP Servers
- AlicenseBqualityNot gradedmaintenanceMCP server for collecting code from files and directories into a single markdown document.28MIT
- AlicenseNot gradedqualityDmaintenanceMCP Server around https://expr-lang.org1MIT
- AlicenseAqualityAmaintenanceMCP Server to previewing mermaid diagrams. https://github.com/veelenga/claude-mermaid/2536203MIT
- AlicenseBqualityDmaintenanceMCP server for managing Claude Code conversation sessions1278MIT
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/formulahendry/mcp-server-code-runner'
If you have feedback or need assistance with the MCP directory API, please join our Discord server