delegations-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., "@delegations-mcp run devteam:implement to add error handling to the login function"
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.
delegations-mcp
An MCP server that exposes a library of delegation prompts as tools. A smart orchestrator LLM uses these tools to hand off bounded tasks to a reduced LLM or coding agent, which receives a fully-constructed, self-contained prompt requiring no broader context.
Configuration
Config is discovered by walking up from the working directory, then merged with
~/.delegations.toml. Project config extends global; library blocks merge
field-by-field (project overrides global per field).
# .delegations.toml
[agent]
executable = "copilot"
args = ["--model", "gpt-4o-mini", "--prompt", "Instructions in: {prompt_path}"]
output_dir = "/tmp" # where prompts and transcripts are written
[library.devteam]
path = "./library/devteam"
test_executable = "/usr/bin/python3"
test_args = ["-m", "pytest"]{prompt_path} in agent args is replaced with the path to the rendered prompt file.
Related MCP server: multi-model-mcp
Running
The server must run on the host filesystem — the agent it spawns edits files directly and needs access to your project.
stdio mode — recommended, zero config
The MCP client spawns the server automatically, inheriting its working directory. Config is discovered from there. No setup required beyond installing the package.
MCP client config (e.g. Claude Desktop):
{
"mcpServers": {
"delegations": {
"command": "uv",
"args": ["run", "--directory", "/path/to/delegations-mcp", "delegations-mcp"]
}
}
}HTTP mode — persistent session server
Useful when multiple agents share a session: the registry is loaded once, and
the async lock for lock: true delegations is shared across all connections.
Run from your project directory (so config discovery finds .delegations.toml):
cd /your/project
delegations-mcp --transport http --port 8000
# or: uv run --directory /path/to/delegations-mcp delegations-mcp --transport httpConnect your MCP client to http://localhost:8000/mcp. One server instance per
project — the working directory at startup determines which config and libraries
are used.
Tools exposed
Tool | Description |
| Lists available delegations; refreshes registry from disk |
| Returns full details and merged input schema for a delegation |
| Runs a delegation; returns |
Delegation names are library:delegation (e.g. devteam:implement).
Libraries
See library/devteam/README.md for the bundled
devteam library. See docs/library-implementation.md
to author your own.
Available Tools
3 toolsget_delegationC
Get full details for a delegation by its library:name.
Inputs: name (required). Returns: object
list_delegationsB
List all available delegations. Also refreshes the registry from disk.
Inputs: no named parameters. Returns: result
run_delegationC
Run a delegation by its library:name. Returns summary, prompt_path, transcript_path.
Inputs: name (required), inputs. Returns: object
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 3 tools
Each tool has a clearly distinct purpose: get_delegation retrieves details for a specific delegation, list_delegations lists all delegations and refreshes the registry, and run_delegation executes a delegation and returns results. There is no overlap in functionality, making tool selection unambiguous.
All tool names follow a consistent verb_noun pattern with snake_case: get_delegation, list_delegations, run_delegation. The naming is predictable and readable, with no deviations in style or convention.
With only 3 tools, the set feels thin for a delegations management server, as it lacks operations like create, update, or delete delegations. However, the tools cover basic retrieval, listing, and execution, which might be sufficient for a minimal scope.
The tools provide read and execute capabilities (get, list, run), but there are notable gaps in lifecycle management, such as creating, updating, or deleting delegations. This could limit agent workflows that require full CRUD operations, though the existing tools support core usage.
Maintenance
Related MCP Connectors
Nifty's MCP server — exposes tasks, projects, messages, and files as tools for AI agents.
MCP server for your apps' tools and custom tools, plus hosted AI agents and approval-gated workflows
Hosted MCP server and Agent Skills for specs, engineering threads, and project memory.
LLM Orchestration Agent (Mcp)
Related MCP Servers
- AlicenseNot gradedqualityCmaintenanceMCP server that enables AI agents to run a deterministic orchestration loop with decomposition, subagent execution, and review feedback across multiple LLM backends.60MIT
- FlicenseAqualityDmaintenanceAn MCP server that exposes tools for sub-agent style reasoning across multiple LLM providers, enabling delegation of prompts to various models and running critique loops, debates, red-teaming, and answer ranking.6-
- AlicenseAqualityDmaintenanceLocal MCP server that exposes delegation tools for Codex, Claude, and Antigravity CLI, enabling an orchestrator agent to assign tasks to these sub-agents via non-interactive CLI commands.3MIT
- AlicenseNot gradedqualityDmaintenanceMCP server that enables delegation of small coding implementations to a cheaper language model with propose_patch and apply_patch tools, while the primary agent retains architecture, review, and approval.MIT