AgentExecMPC
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MCP_TRANSPORT | No | Transport protocol for MCP server (stdio or sse) | stdio |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| shellA | |
| execute_codeA | |
| install_packageA | |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 3 tools
Each tool targets a distinct function: executing code, installing packages, and running shell commands. There is no overlap in their purposes.
All tool names follow a consistent verb_noun snake_case pattern (execute_code, install_package, shell). 'Shell' is a noun but functions as a clear command name.
With only 3 tools, the server is tightly scoped for code execution and environment management. Each tool serves a necessary role without clutter.
The set covers core operations: running code, installing packages, and shell access. A minor gap is the lack of package uninstallation or listing, but the essential workflows are present.