LocalREPL MCP Server
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_shellA | Run a shell command inside a REPL context with structured output. |
| set_repl_cwdC | Change a REPL's tracked working directory for future shell calls. |
| get_repl_cwdB | Return the REPL's current working directory. |
| spawn_shellA | Spawn a long-running process. Returns a proc_id for follow-up calls. |
| tail_shell_outputA | Return the most recent lines from a spawned process's output. |
| send_to_shellB | Write to a spawned process's stdin. Useful for interactive REPLs. |
| kill_shellB | Send a signal to a spawned process. |
| wait_shellC | Block until a spawned process exits (or timeout). Returns exit info. |
| list_shellsA | Return info on all spawned processes (live and recently-exited). |
| reap_exitedA | Remove exited processes from the registry. Call occasionally to keep list_shells tidy, especially after running many short spawns. |
| query_command_historyA | Search the command execution log. |
| command_statsA | Aggregate metrics across the command log. |
| tag_commandC | Attach tags to a logged command for later recall. Useful for marking commands as e.g. 'flaky', 'slow', 'solved', 'security-review'. Replaces any existing tags on that row. |
| forget_commandB | Delete a command log row. Use when a logged command captured a secret (token in argv, etc.) that shouldn't persist on disk. |
| vacuum_memoryA | Keep only the most recent N rows and reclaim disk space. Call occasionally to prevent unbounded growth. |
| run_python_in_venvA | Run Python code inside a project's virtual environment. |
| find_venvA | Locate a virtual environment in the REPL's current directory. |
| create_python_replC | |
| run_python_in_replB | |
| list_active_replsA | List all active REPL instances and their IDs. |
| get_repl_infoC | |
| delete_replA | |
| initialize_modular_empowermentC | |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| test_prompt_workflow | A testing prompt to verify the external prompts system is working. |
| strategic_capability_enhancement | |
| repl_agent_system_prompt | Prompt template showing AI how to use the REPL Agent System. |
| data_analysis_workflow | A prompt template for data analysis workflow. |
| system_discovery_workflow | |
| simple_data_analysis_workflow | |
| agent_demo_simulation | |
| empowered_agent_basic_setup | A prompt template for Modular Empowerment Framework integration. Updated based on actual testing results. |
| advanced_workflow_orchestration | |
| collosal_acc_implementation | |
| basic_python_repl_workflow | A prompt template showing how to use the Python REPL. |
| basic_system_check | A prompt template to verify that the REPL server is working correctly. |
| full_empowerment_workflow | A prompt template showing how to use the Modular Empowerment Framework with Persistent Agents. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 23 tools
Each tool targets a distinct operation: REPL lifecycle, shell process management, command history logging, and virtual environment usage. No two tools have overlapping purposes; descriptions clearly differentiate between one-shot shell commands, long-running processes, and Python execution contexts.
All tool names follow a consistent verb_noun pattern in snake_case (e.g., create_python_repl, run_shell, query_command_history). The naming is predictable and intuitive, making it easy for an agent to infer functionality.
With 23 tools, the server covers a broad but coherent set of functionalities for local REPL and shell management. While slightly above the typical sweet spot, each tool serves a specific purpose and justifies its presence without feeling redundant.
The tool surface comprehensively covers the domain: REPL creation/deletion/inspection, Python execution (both in-REPL and in-venv), shell command execution (one-shot and long-running), process management, command logging, and history queries. No obvious gaps for the stated purpose.