SubMCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SUBMCP_ROOT | No | Sandbox root. Every sub-agent file operation is confined here. | server cwd |
| SUBMCP_MODEL | No | Model for sub-agents. | stepfun-ai/step-3.7-flash |
| SUBMCP_TOP_P | No | Nucleus sampling. | 0.95 |
| NVIDIA_API_KEY | Yes | Your NIM key. Without it the server still starts; list_agents works and delegate returns setup instructions. | |
| SUBMCP_TIMEOUT | No | Wall-clock ceiling per delegation, seconds. | 240 |
| SUBMCP_BASE_URL | No | OpenAI-compatible endpoint. Point it at a self-hosted NIM if you have one. | https://integrate.api.nvidia.com/v1 |
| SUBMCP_THINKING | No | step-3.7-flash reasons by default; off is faster and cheaper for delegated grunt work. | 0 |
| SUBMCP_MAX_STEPS | No | Tool-call budget per delegation. | 12 |
| SUBMCP_MAX_TOKENS | No | Max tokens per NIM completion. | 4096 |
| SUBMCP_ALLOW_SHELL | No | Global kill switch for shell commands. Off. Booleans accept 1, true, yes, on. | 0 |
| SUBMCP_ALLOW_WRITE | No | Global kill switch for file edits. Off. Booleans accept 1, true, yes, on. | 0 |
| SUBMCP_TEMPERATURE | No | Sampling temperature. | 0.2 |
| SUBMCP_MAX_PARALLEL | No | Concurrency cap for delegate_parallel. | 4 |
| SUBMCP_MAX_OUTPUT_CHARS | No | Truncation limit on any single tool result fed back to the sub-agent. | 20000 |
Capabilities
Features and capabilities supported by this server
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| delegateA | Run a bounded sub-agent on the user's NVIDIA NIM account and return its written report. Reach for this to keep large, mechanical, or exploratory work out of your own context: tracing how a feature flows across many files, auditing a directory for a pattern, summarising an unfamiliar module or dependency, drafting a migration plan, reviewing a diff. The sub-agent reads the repository itself and spends NIM tokens doing it; you only receive the finished report.
Parameters: task - self-contained instructions, including the output format you want back. profile - "general" (default), "researcher", "coder", or "reviewer". Researcher for read-and-explain sweeps, coder for focused edits, reviewer for critique. files - paths to hand over up front so the sub-agent doesn't waste steps hunting. write - allow file edits. Off by default, and ignored entirely unless the server was started with SUBMCP_ALLOW_WRITE=1. Leave it off for investigation. model - override the NIM model for this run (default stepfun-ai/step-3.7-flash). max_steps - tool-call budget for this run (default 12). Returns a markdown report: the sub-agent's findings, plus the model used, how many steps
it took, which tools it called, and any files it changed. The sub-agent is sandboxed to
the server's root directory, is read-only unless For several independent subtasks, call |
| delegate_parallelA | Run several independent sub-agents at once and return every report in one answer. This is the tool to use whenever the work splits into pieces that do not depend on each
other: "summarise each of these four modules", "check these three services for the same
misconfiguration", "for each failing test, find the cause". Running them concurrently on
one NIM connection is much faster than calling Every string in Parameters: tasks - list of self-contained task strings, one sub-agent each. profile - "general" (default), "researcher", "coder", or "reviewer"; applies to all. files - paths handed to every sub-agent up front. model - override the NIM model (default stepfun-ai/step-3.7-flash). Concurrency is capped at SUBMCP_MAX_PARALLEL (default 4); extra tasks queue. All
sub-agents are read-only here - there is no Returns one markdown document with a |
| list_agentsA | Show what SubMCP can do right now: profiles, model, sandbox root, and capability gates. Call this before your first |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/Animuni-Express/SubMCP'
If you have feedback or need assistance with the MCP directory API, please join our Discord server