Pylpex MCP
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@Pylpex MCP tokenize this Pylpex code: x = 5 + 3"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Pylpex MCP
This is a MCP server for Pylpex interpreter.
Installation
Assuming you are using Claude Desktop and have uv installed, follow these instructions to set up the Pylpex MCP server:
Clone the repository:
git clone https://github.com/Golto/pylpex-mcp.git
cd pylpex-mcpInstall dependencies:
uv syncThis command reads the pyproject.toml file and installs all the required dependencies.
Configure your Claude Desktop settings to use this MCP server:
Go to your Claude Desktop settings, then to the Developer Settings tab, click on "Edit config" and add the following configuration to your claude_desktop_config.json:
{
"mcpServers": {
"Pylpex": {
"command": "uv",
"args": [
"--directory",
"$ABSOLUTE/PATH/TO/THE/PROJECT/pylpex-mcp",
"run",
"mcp",
"run",
"main.py"
]
}
}
}You may want to replace uv with the absolute path to the uv executable. To find uv location, use which uv on Linux/MacOS or where uv on Windows. Also, replace $ABSOLUTE/PATH/TO/THE/PROJECT/pylpex-mcp with the absolute path to the project directory. --directory argument is required for uv to find the project with dependencies.
Note: Running
uv run mcp install main.pywill install the MCP server in your Claude Desktop settings directly. But it may not work because of the--directoryargument missing.
Close and reopen your Claude Desktop application to apply the changes.
Verify that the Pylpex server is running by checking the status in the Developer Settings tab.
You should see the Pylpex tools available in your Claude Desktop interface.
Related MCP server: MCP Python Interpreter
Tools
At this point, you should have access to the following tools:
run: Execute Pylpex code and return the result.
tokenize: Convert Pylpex code into tokens for analysis. Use the Lexer component of the Pylpex interpreter.
get_variables: Get all variables in the current interpreter state.
reset: Reset the interpreter state.
Resources
get_documentation: Get the documentation of the Pylpex language. It gives you the syntax and the available functions.
get_examples: Get examples of Pylpex code as code snippets.
More details
For more details about the Pylpex language, you can check the Pylpex github repository.
Note: The Pylpex language is still in development and may change in the future. And it's in french...
Available Tools
4 toolsget_variablesB
Get all variables in the current interpreter state.
Inputs: no named parameters. Returns: Réponse de variables
resetB
Reset the interpreter state.
Inputs: no named parameters. Returns: Réponse de réinitialisation
runA
Execute Pylpex code and return the result.
Pylpex is a custom programming language. Before executing code:
Check pylpex://documentation for syntax reference
Review pylpex://examples for working patterns
Ensure code follows Pylpex syntax conventions
Args: code: Valid Pylpex source code to execute
Returns: The evaluated result of the code execution
Example usage: run("2 + 2") # Returns: 4 run("function double(x) { return x * 2 } double(5)") # Returns: 10
Inputs: code (required). Returns: Réponse d'exécution
tokenizeB
Convert Pylpex code into tokens for analysis.
Args: code: Valid Pylpex source code to tokenize
Returns: List of tokens with their types, values, and positions
Inputs: code (required). Returns: Réponse de tokenisation Pylpex
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 4 tools
Each tool has a clearly distinct purpose with no overlap: get_variables retrieves interpreter state, reset clears it, run executes code, and tokenize analyzes code structure. The descriptions make these roles unambiguous, preventing agent misselection.
All tool names follow a consistent verb-based pattern (get_variables, reset, run, tokenize) without mixing conventions. The naming is straightforward and predictable, enhancing readability and agent usability.
With 4 tools, the count is reasonable for a language interpreter server, covering core operations like execution, state management, and analysis. It could benefit from additional tools (e.g., for debugging or syntax validation) but is well-scoped for basic functionality.
The toolset covers essential interpreter workflows: running code, inspecting state, resetting state, and tokenizing code. Minor gaps exist, such as lack of tools for step-through debugging or syntax checking, but agents can work around these with the provided tools.
Related MCP Connectors
Build Apps and run code in 30 languages — sandboxed, with persistent sessions for agent loops.
Write, type-check and run AILANG in a sandbox, with Z3-proved contracts and docs search.
AI-native programming language and toolchain for accountable, verifiable agent-driven development.
I do everything related to coding and execution tasks
Related MCP Servers
- FlicenseNot gradedqualityCmaintenanceEnables safe execution of Python code with AI assistance and integration with Model Context Protocol tools.1-
- FlicenseNot gradedqualityNot gradedmaintenanceEnables LLMs to interact with Python environments, execute code or scripts, manage packages, and read/write files within an isolated working directory.-
- FlicenseNot gradedqualityAmaintenanceEnables LLMs to interact with Python environments, run code and scripts, manage packages, and read or write files within a configured working directory.-
- FlicenseNot gradedqualityAmaintenanceEnables LLMs to interact with local Python environments, execute code and scripts, manage packages, and read or write files within an isolated working directory.-