delega-mcp
The delega-mcp server connects MCP-compatible clients to Delega task infrastructure, enabling natural language management of tasks, projects, and agents.
Task Management
List tasks – Retrieve tasks with filters by project, label, due date (today/upcoming/overdue), or completion status
Get task – Fetch full details of a specific task, including subtasks
Create task – Create tasks with title, description, labels, priority (1–4), due date, and project assignment
Update task – Modify any field of an existing task
Complete / Delete task – Mark tasks as completed or permanently delete them
Add comment – Attach a comment (with optional author) to a task
Delegate tasks – Create parent-child relationships for multi-agent handoffs, with chain visualization
Assign tasks – Assign or unassign tasks to specific agents
Merge context – Deep-merge persistent context data into tasks
Duplicate detection – Check for similar existing tasks before creation
Project Management
List all projects and retrieve task statistics (totals, completed today, due today, overdue, breakdowns by project)
Agent Management
List, register, and delete agents (registration returns an API key)
Additional Features
Webhook management – Create, list, and delete webhooks for event notifications (admin only)
Usage monitoring – Get quota and rate-limit information for hosted API users
Security – Secure API key handling via environment variables, key redaction in output, and HTTPS enforcement
Flexible deployment – Works with self-hosted Delega instances or the hosted api.delega.dev service
delega-mcp
MCP server for Delega — the task handoff layer for AI agents.
Connect any MCP-compatible client (Claude Code, Cursor, Codex, etc.) to Delega and manage tasks, projects, and agents through natural language.
Install
npm install -g @delega-dev/mcpRelated MCP server: Taskmaster MCP Server
Configure
Add to your MCP client config (e.g. Claude Code claude_code_config.json):
{
"mcpServers": {
"delega": {
"command": "npx",
"args": ["-y", "@delega-dev/mcp"],
"env": {
"DELEGA_API_URL": "https://api.delega.dev",
"DELEGA_AGENT_KEY": "dlg_your_agent_key_here"
}
}
}
}Environment Variables
Variable | Default | Description |
|
| Delega API endpoint. Defaults to the hosted API; custom |
| (none) | Agent API key for authenticated requests. Preferred for MCP configs; if both key env vars are set, this one wins. |
| (none) | Fallback alias accepted so the MCP, CLI, and SDK can share one env var when needed. |
|
| ⚠️ Development only. Set to |
Use https://api.delega.dev as the URL.
Security Notes
Non-local
DELEGA_API_URLvalues must usehttps://.Agent keys are passed through environment variables rather than command-line arguments, which avoids process-list leakage.
MCP tool output redacts full agent API keys by default.
Do not set
DELEGA_REVEAL_AGENT_KEYS=1in production. This flag exists for initial setup only. In production, a prompt-injected agent could exfiltrate keys fromregister_agentorlist_agentstool output. Keys are returned once at creation time; register a replacement agent if you need a new key.
Tools
Tool | Description |
| List tasks, filter by project, label, due date, completion |
| Get full task details including subtasks and task links |
| Attach a branch, commit, PR, or URL link to a task |
| List branch, commit, PR, and URL links attached to a task |
| Create a new task |
| List recurring task templates |
| Create a recurring task template ( |
| Update a recurring task template, including pausing/resuming with |
| Delete a recurring task template; existing spawned task instances remain |
| Update task fields (incl. |
| Assign a task to an agent (or pass |
| Delegate a task: create a child task linked to a parent (parent status flips to |
| Return the full delegation chain for a task (root + descendants, sorted by depth) |
| Merge keys into a task's persistent context blob (deep merge, not replace), recording provenance source |
| Read a task's persistent context blob, optionally with per-key provenance |
| Read the append-only provenance ledger for a task's context |
| Check whether proposed task content is similar to existing open tasks (TF-IDF + cosine similarity). Call before |
| Return quota + rate-limit info. Hosted API only ( |
| Claim the next available task from the queue for exclusive processing (work-queue semantics). Lease-based: default 300s, configurable 30-3600. Returns the task or reports an empty queue. Hosted API only. |
| Extend the lease on a claimed task. Call periodically while working so the claim isn't reclaimed. Hosted API only. |
| Release a claimed task back to the queue without completing it. Hosted API only. |
| Report |
| Mark a task as completed |
| Delete a task permanently |
| Add a comment to a task |
| List all projects |
| Get task statistics |
| List registered agents |
| Register a new agent (returns API key), optionally with a role preset |
| Set an agent's role: |
| Delete an agent (refused if agent has active tasks) |
| List all webhooks (admin only) |
| Create a webhook for event notifications, including |
| Delete a webhook by ID (admin only) |
Task output format
Task-returning tools (list_tasks, get_task, create_task, update_task, assign_task) render each task with assignment metadata when available:
[#42] Ship the release
Description: Cut RC, tag, push to npm
Project: Delega
Labels: release
Priority: 3
Due: 2026-04-20
Assigned to: Coordinator (#7)
Created by: planner (#3)
Completed: noAssigned to / Created by / Completed by lines are emitted only when the underlying field is populated. Custom /api-style endpoints return a nested agent object so the assignee renders as <display_name> (#id); the hosted api.delega.dev API returns the raw agent ID so it renders as #<id>.
Tasks that are part of a delegation chain also surface the chain metadata:
[#def] Draft intro
Status: delegated
Assigned to: Drafter (#3)
Created by: Coordinator (#7)
Delegation: depth 1, parent #abc, root #abc
Delegated by: Coordinator (#7)
Completed: no
Context keys: step, findings (2)Single-task tools (get_task, create_task, update_task, assign_task, delegate_task, update_task_context) use a detail render that pretty-prints the full context blob (truncated at 2000 chars). list_tasks uses the concise list render which shows Context keys: … instead.
get_task also shows attached task links when present:
Links:
branch: delega-dev/delega-api phase-3-github — https://github.com/delega-dev/delega-api/tree/phase-3-github
pr: delega-dev/delega-api 42 — https://github.com/delega-dev/delega-api/pull/42Delegation chains
get_task_chain returns the full parent/child chain for any task in the chain. Output is indented by delegation_depth:
Delegation chain (root #abc, depth 2, 2/4 complete):
[#abc] Write report (depth 0, delegated)
[#def] Draft intro (depth 1, completed)
[#jkl] Draft conclusion (depth 1, pending)
[#ghi] Research sources (depth 2, completed)Nodes are sorted by depth then creation order (matching the API's response ordering).
Recurring tasks
Recurring task tools manage templates. The hosted scheduler creates normal task instances from those templates; completing an instance does not delete or pause the recurrence.
list_recurrences, create_recurring_task, and update_recurrence render templates with their rule, next due timestamp, active state, skip-if-open behavior, and available agent metadata:
[#weekly-report] Weekly report
Rule: weekly, weekday 1
Timezone: America/Chicago
Next due: 2026-06-22T14:00:00Z
Active: yes
Skip if open: yes
Assigned to: Reporter (#7)Hosted API
Delega is a hosted service. Point DELEGA_API_URL at https://api.delega.dev — free up to 1,000 tasks/month.
Links
License
MIT
Maintenance
Latest Blog Posts
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/delega-dev/delega-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server