Skip to main content
Glama
deenesjakoruzh
AnEntrypoint

MCP-REPL

by AnEntrypoint
OverviewSchemaRelated ServersScoreDiscussions
JavaScript
Local

gm-exec

ПРИМЕЧАНИЕ: Если вы ищете mcp-repl, glootie или GM... теперь они находятся по адресу: http://github.com/anEntrypoint/gm

Инструмент для выполнения кода для клиентов MCP и CLI. Поддержка нескольких языков (JS/TS, Python, Go, Rust, C, C++, Deno, Java, bash). Построен на базе Bun с изоляцией процессов под управлением PM2.

Related MCP server: MCP QuickJS Runner

MCP-сервер

Добавьте в конфигурацию вашего MCP-клиента:

{
  "mcpServers": {
    "gm-exec": {
      "command": "bunx",
      "args": ["gm-exec", "--mcp"]
    }
  }
}

Или установите глобально:

bun install -g gm-exec
gm-exec --mcp

CLI

bunx gm-exec-cli exec --cwd=/app "console.log('hello')"
bunx gm-exec-cli bash --cwd=/app "npm install && npm test"
bunx gm-exec-cli exec --lang=python --cwd=/app "print('hello')"
bunx gm-exec-cli exec --file=script.js

Команды

gm-exec-cli exec [options] <code>     Execute code (waits up to 15s, then backgrounds)
  --lang=<lang>                        nodejs (default), python, go, rust, c, cpp, java, deno
  --cwd=<dir>                          Working directory
  --file=<path>                        Read code from file

gm-exec-cli bash [--cwd=<dir>] <cmd>  Execute bash commands, same 15s ceiling

gm-exec-cli status <task_id>           Poll status + drain output of a background task
gm-exec-cli close <task_id>            Delete a background task

gm-exec-cli runner start               Start the runner manually (PM2, no autorestart)
gm-exec-cli runner stop                Stop the runner
gm-exec-cli runner status              Show runner PM2 status

Фоновое выполнение

Для команд установлен жесткий лимит в 15 секунд. Если выполнение продолжается дольше, процесс переводится в фоновый режим, и вы получаете идентификатор задачи с инструкциями по мониторингу:

Backgrounded after 15s — task still running.
Task ID: task_3

Watch output:
  gm-exec-cli status task_3
  gm-exec-cli close task_3
  gm-exec-cli runner stop

Среда выполнения автоматически запускается перед каждой командой и останавливается после — за исключением случаев, когда задача была переведена в фоновый режим; в этом случае среда остается активной до тех пор, пока вы принудительно ее не остановите.

Поддерживаемые языки

Язык

Среда выполнения

JavaScript / TypeScript

Node.js / Bun

Python

python3

Go

go run

Rust

rustc

C

gcc

C++

g++

Java

javac + java

Deno

deno run

bash / sh / zsh

shell

Требования

curl -fsSL https://bun.sh/install | bash

Available Tools

1 tool
executeA

Execute code in JS/TS, Go, Rust, Python, C, C++, or bash with auto-runtime detection. Primary tool for testing hypotheses before implementation. Supports both code snippets and shell commands.

ParametersJSON Schema
NameRequiredDescriptionDefault
workingDirectoryYesPath to working directory for execution.
codeNoCode to execute. Include timeouts for network/async operations to prevent hangs.
commandsNoBash commands (single or array for planned batch executions)
runtimeNoExecution runtime (default: auto-detect)
timeoutNoTimeout in milliseconds (default: 240000)

TDQS

A3.5/5.0
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations provided, the description carries the full burden of behavioral disclosure. It mentions auto-runtime detection and supports for code/shell commands, but doesn't cover critical aspects like permissions, rate limits, error handling, or output format, leaving gaps for a mutation tool.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is concise and front-loaded, with two sentences that efficiently convey the tool's purpose and key features without unnecessary details. Every sentence adds value, making it easy to understand quickly.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's complexity (executing code in multiple languages), no annotations, and no output schema, the description is incomplete. It lacks details on behavioral traits, error handling, and return values, which are crucial for safe and effective use.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so the schema fully documents all 5 parameters. The description adds minimal value beyond the schema, mentioning code snippets and shell commands which map to 'code' and 'commands' parameters, but doesn't provide additional syntax or usage details.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool's purpose as executing code in multiple languages with auto-runtime detection, distinguishing it as a primary tool for testing hypotheses. It specifies both code snippets and shell commands as inputs, though without sibling tools, differentiation isn't applicable.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description implies usage for testing hypotheses before implementation, providing some context, but lacks explicit guidance on when to use this tool versus alternatives, prerequisites, or exclusions. No sibling tools exist to compare against.

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. 8 tool updatesv1.0.0
    • Removedastgrep_analyze
    • Removedastgrep_lint
    • Removedastgrep_replace
    • Removedastgrep_search
    • Addedexecute
    • Removedexecutedeno
    • Removedexecutenodejs
    • Removedsearchcode
  2. 7 tool updates
    • First observedastgrep_analyze
    • First observedastgrep_lint
    • First observedastgrep_replace
    • First observedastgrep_search
    • First observedexecutedeno
    • First observedexecutenodejs
    • First observedsearchcode
Install Server
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

TDQS

A3.5/5.0
Disambiguation5/5

With only one tool, there is no possibility of ambiguity or overlap between tools. The single tool 'execute' has a clear, distinct purpose that cannot be confused with any other tool in this set.

Naming Consistency5/5

Since there is only one tool, naming consistency is inherently perfect. The tool name 'execute' follows a simple verb pattern, and there are no other tools to compare it against for inconsistency.

Tool Count2/5

A single tool is generally too few for a server's purpose, as it limits functionality and flexibility. While the tool is versatile (supporting multiple languages and shell commands), the server likely has a broader scope (e.g., code execution and testing) that could benefit from additional tools for tasks like debugging, logging, or result analysis.

Completeness2/5

The server appears to be focused on code execution and testing, but with only one tool, there are significant gaps in coverage. For example, there are no tools for managing execution environments, handling dependencies, validating code, or analyzing results, which are common needs in such domains.

Maintenance

ActivityInactive
ResponsivenessNo issues

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

Related MCP Servers

  • MCP QuickJS Runner

    jlucaso1
    F
    license
    Not graded
    quality
    D
    maintenance
    Provides secure execution of arbitrary JavaScript code within a sandboxed QuickJS WASM environment, allowing language models or other MCP clients to safely run JavaScript code snippets without compromising the host system.
    4
    -

  • Node.js Sandbox MCP Server

    alfonsograziano
    F
    license
    Not graded
    quality
    D
    maintenance
    Enables running arbitrary JavaScript code in isolated Docker containers with on-the-fly npm dependency installation, supporting both ephemeral one-shot executions and persistent sandbox environments.
    134
    157
    -

  • Node Code Sandbox MCP

    mozicim
    F
    license
    A
    quality
    B
    maintenance
    A secure Node.js execution environment that allows coding agents and LLMs to run JavaScript dynamically, install NPM packages, and retrieve results while adhering to the Model Control Protocol.
    7
    134
    4
    -

Appeared in Searches

Latest Blog Posts

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/AnEntrypoint/gm-exec'

If you have feedback or need assistance with the MCP directory API, please join our Discord server