1. Conduid
  2. Developer Tools
  3. Python MCP
MCP server · Developer Tools

Python MCP

MCP Server to run python code locally

Unclaimed last commit a year ago devtools
51Fair

Scored 13 days ago · breakdown

About Python MCP

Python MCP is an MCP server published by Alec2435 in the Developer Tools category: mCP Server to run python code locally.

The repository has 54 stars and 15 forks, with the last commit a year ago. Six months or more without a commit doesn't mean the server is broken, but check the open issues before depending on it in production.

Install

From source
git clone https://github.com/Alec2435/python_mcp

This server has no ConduID identity, so agent calls to it are not receipted. Pin the version you install and review the source before granting it credentials.

Tools (1)

python_replExecutes Python code in a persistent session

Parameters not published.

Ask AI

✦

Ask AI about Python MCP

Powered by Claude · Grounded in docs

I know everything about Python MCP. Ask me about installation, configuration, usage, or troubleshooting.

Security checks

Static checks derived from the repository 6 days ago. Heuristics on the source, not an audit.

  • ✓README presentThe repository ships documentation.
  • !License declaredNo license file. Legally you have no right to use it in a product.
  • !Tests presentNo tests found. Behaviour changes may go unnoticed between versions.
  • ✓Dependencies pinnedA lockfile pins dependency versions.
  • !No dynamic code executionSource scan found eval or shell execution. Review how tool inputs reach it before granting credentials.
  • !Scoped permissionsDoesn't declare a permission scope. Assume it can do anything its process can.

README

python_local MCP Server

An MCP Server that provides an interactive Python REPL (Read-Eval-Print Loop) environment.

Components

Resources

The server provides access to REPL session history:

  • Custom repl:// URI scheme for accessing session history
  • Each session's history can be viewed as a text/plain resource
  • History shows input code and corresponding output for each execution

Tools

The server implements one tool:

  • python_repl: Executes Python code in a persistent session
    • Takes code (Python code to execute) and session_id as required arguments
    • Maintains separate state for each session
    • Supports both expressions and statements
    • Captures and returns stdout/stderr output

Configuration

Install

Claude Desktop

On MacOS: ~/Library/Application\ Support/Claude/claude_desktop_config.json On Windows: %APPDATA%/Claude/claude_desktop_config.json

Development

Building and Publishing

To prepare the package for distribution:

  1. Sync dependencies and update lockfile:
uv sync
  1. Build package distributions:
uv build

This will create source and wheel distributions in the dist/ directory.

  1. Publish to PyPI:
uv publish

Note: You'll need to set PyPI credentials via environment variables or command flags:

  • Token: --token or UV_PUBLISH_TOKEN
  • Or username/password: --username/UV_PUBLISH_USERNAME and --password/UV_PUBLISH_PASSWORD

Debugging

Since MCP servers run over stdio, debugging can be challenging. For the best debugging experience, we strongly recommend using the MCP Inspector.

You can launch the MCP Inspector via npm with this command:

npx @modelcontextprotocol/inspector uv --directory /path/to/python_local run python-local

Upon launching, the Inspector will display a URL that you can access in your browser to begin debugging.

README fetched from the repository 6 days ago. The original is authoritative.

Questions

About Python MCP

How do I install Python MCP?

No package has been published for this server, so install it from source: clone the repository and follow its README.

Is Python MCP safe to use with an AI agent?

Its trust score is 51 out of 100 (fair). It passes 2 of the 6 static security checks run so far; the failures are listed above. It has no ConduID identity yet, so agent calls to it are not receipted.

Is Python MCP still maintained?

The last commit was a year ago and 4 open issues. That's long enough that you should check whether the maintainer is responding to issues before depending on it.