MCP Python Interpreter

Created By
yzflya year ago
MCP Python Interpreter: run python code.
Overview

What is MCP Python Interpreter?

MCP Python Interpreter is a Model Context Protocol (MCP) server that allows large language models (LLMs) to interact with Python environments, execute Python code, manage files, and streamline development workflows.

How to use MCP Python Interpreter?

To use the MCP Python Interpreter, install it via pip or uv, configure it in Claude Desktop, and specify the working directory and Python path in the configuration file.

Key features of MCP Python Interpreter?

  • Environment Management: List and use different Python environments (system and conda)
  • Code Execution: Run Python code or scripts in any available environment
  • Package Management: List installed packages and install new ones
  • File Operations: Read and write files of any type (text, source code, binary)
  • Python Prompts: Templates for common Python tasks like function creation and debugging

Use cases of MCP Python Interpreter?

  1. Executing Python scripts in various environments.
  2. Managing Python packages and dependencies.
  3. Reading and writing files for data processing tasks.
  4. Debugging Python code with provided templates.

FAQ from MCP Python Interpreter?

  • Can I run any Python code?

Yes, you can run any Python code as long as it is compatible with the selected environment.

  • Is there a limit on file sizes?

Yes, the server has file size limits for reading and writing files to ensure security.

  • How do I ensure security while using the interpreter?

The interpreter operates within an isolated working directory and has strict file path security.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
yzfly
Star
8
Language
Python
License
View license

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago