3 #execution MCP Servers & Clients
Every MCP server and client below is tagged #execution — install one to give Claude, Cursor, VS Code, or any other MCP-compatible client access to execution tools.
すべて
MGC Blackbox – Local Encrypted Execution Layer
zkeviny
A local encrypted execution layer for AI agents. Provides sealed scripts, protected subprocess execution, and secure local storage.
Dce Mcp Server
BE-DCE
MCP server for DCE (Better Execute) — connects AI agents to EOS execution data: Rocks, Scorecards, V/TO, Level 10 meetings, to-dos, and topics. 13 read/write tools. Works with Claude, Cursor, and other MCP clients.
Python Exec Sandbox
lu-zhengda
Sandboxed Python execution for AI agents. Scripts run in ephemeral, isolated environments (bubblewrap on Linux, Docker on macOS) with PEP 723 inline dependencies — zero host pollution, zero leftover venvs, zero package conflicts. Supports multi-version Python (3.13–3.15), configu
Frequently asked questions
What is a #execution MCP server?
- An MCP server tagged #execution implements the Model Context Protocol so AI assistants like Claude, Cursor, and VS Code can access execution-related tools, data, or APIs.
How many #execution MCP servers and clients are there?
- mcp.so currently lists 3 MCP servers and clients tagged #execution.
How do I install a #execution MCP server?
- Open any server below and copy its install snippet into Claude Desktop, Cursor, VS Code, or another MCP client's configuration — remote servers need no separate download.