Skip to main content
Glama
README.md
execution in a secure and scalable lab setup.

โš™๏ธ Lab Virtual MCP Server (Execute Code Remotely via Claude AI)
Create a virtual lab for users to run custom code remotely using the Model Context Protocol (MCP) and integrate with Claude AI or other clients.

  
<img src="video/test.gif" alt="description" height="300" width="900" />


๐Ÿ”— GitHub Repo
<pre>
๐Ÿ“ฆ https://github.com/Nuvepro-Technologies-Pvt-Ltd/McpSever_Remote_code_execution.git
</pre>
๐Ÿ“‚ This repo has moved to base/base-mcp

๐Ÿš€ What This Lab Server Does
๐Ÿง  Enables remote Python code execution through cline AI


๐Ÿงช Supports real-time lab scenarios (code evaluation, sandbox testing, etc.)

๐Ÿ“‹ Prerequisites
Ensure you have the following on your system:

โœ… Python 3.10.11

โœ… pip (Python package manager)

โœ… fastmcp (to serve the MCP endpoint)

โœ… uv (virtual environment manager, via scoop or curl)

โœ… Access to Claude Desktop or Cursor or cline (for testing)



๐Ÿงฑ Installation Steps

1. Clone the MCP Server Repo
<pre>
git clone https://github.com/Nuvepro-Technologies-Pvt-Ltd/McpSever_Remote_code_execution.git
</pre>

2. Set up Python Environment

<pre>
Set-ExecutionPolicy RemoteSigned -Scope CurrentUser
</pre>

<pre>
scoop install python
</pre>

<pre>
scoop install uv
</pre>




cd McpSever_Remote_code_execution

3. Set Up Virtual Environment

<pre>
python -m venv .venv
</pre>
<pre>
.\.venv\Scripts\activate   # Windows
</pre>
<pre>
source .venv/bin/activate  # macOS/Linux
</pre>

4. Install Dependencies

<pre>
pip install fastmcp
</pre>

<pre>
pip install cryptography
</pre>

<pre>
pip install shelve
</pre>

5. Run the Server
<pre>
fastmcp run app.py
</pre>
You now have a remote code execution server listening for requests via MCP.

๐Ÿงช MCP Client Configuration
For Claude Desktop / Cursor, update your mcp_config.json:


<pre>
{
  "mcpServers": {
    "CloudlabMcp": {
      "disabled": false,
      "timeout": 500,
      "type": "stdio",
      "command": "uv",
      "args": [
        "run",
        "--with",
        "fastmcp",
        "python",
        "%PROJECT_PATH%\\app.py"
      ],
      "env": {
        "API_KEY": "your_private_key",
        "Baseurl": "your seed phrase here",
        "compnaykey": "your_private_key"
      },
      "autoApprove": [*]
    }
  }
}


</pre>

Beofre start Mcp set path
<pre>
set PROJECT_PATH=D:\YourProject
</pre>
<pre>
cline run CloudlabMcp
</pre>

โœ… Available Tools (Prebuilt in MCP)

Tool Description
execute_code	Executes user-provided Python code


๐Ÿ’ก Recommendations for Lab Admins
โœ… Add sandboxing logic to app.py if users can run arbitrary code.

โœ… Use Docker or subprocess isolation for safer execution (optional).

โœ… Monitor logs and set execution timeouts.

TDQS

C2.9/5.0

Scored across 1 tool

Disambiguation5/5

With only one tool, there is no possibility of ambiguity or overlap between tools. The tool 'execute_code' has a clear, distinct purpose that cannot be confused with any other tool in the set.

Naming Consistency5/5

A single tool inherently has perfect naming consistency, as there are no other tools to compare it against. The name 'execute_code' follows a clear verb_noun pattern, which would be consistent if more tools were added.

Tool Count2/5

One tool is generally too few for a server's purpose, as it limits functionality and may not cover the domain adequately. For a 'Lab Virtual MCP Server' that likely involves code execution, additional tools for managing environments, listing sessions, or handling inputs/outputs would be expected.

Completeness1/5

The tool set is severely incomplete for the inferred domain of a lab or virtual environment. With only an 'execute_code' tool, there are obvious gaps such as creating or deleting environments, listing available sessions, handling file uploads/downloads, or monitoring execution status, which are essential for a coherent workflow.

Maintenance

ActivityInactive
ResponsivenessNo issues