Skip to main content
Glama
iota-uz

repl-mcp

by iota-uz
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault

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

CapabilityDetails
tools
{
  "listChanged": true
}
logging
{}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}

Tools

Functions exposed to the LLM to take actions

NameDescription
execute_pythonA

Persistent Python REPL — use instead of python3 -c, heredocs or cmd | python3 via Bash. Also the way to BATCH MCP WORK: the injected mcp bridge reaches your project, global (user-scope) and plugin MCP servers, so one loop replaces N separate tool calls — for f in files: mcp.call('telegram-mcp', 'download_media', **f).

State (variables, imports, functions) survives across calls: a warm call takes ~0.1s vs ~3s for each fresh python3 Bash spawn. Full filesystem access — open(), absolute paths, and ~ all work. Top-level await is supported (e.g. await client.get(url) with httpx).

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

Deploy Server
Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

TDQS

A4.7/5.0

Scored across 1 tool

Disambiguation5/5

With only one tool, there is no possibility of confusion or overlap. The tool's purpose is unambiguous and clearly described.

Naming Consistency5/5

The single tool follows a clear verb_noun pattern (execute_python), and there are no other tools to create inconsistency.

Tool Count5/5

The server is purpose-built as a Python REPL, and a single tool fully satisfies that narrow scope. The tool is powerful and not trivial, so the count is appropriate.

Completeness5/5

The tool covers all expected REPL functionality: persistent state, filesystem access, top-level await, and MCP bridging. There are no obvious gaps for the stated domain.

Maintenance

ActivityMaintained
ResponsivenessUnresponsive

Resources