delega-mcp

MCP server for Delega — task infrastructure for AI agents.

Connect any MCP-compatible client (Claude Code, Cursor, Codex, etc.) to your Delega instance and manage tasks, projects, and agents through natural language.

Install

npm install -g @delega-dev/mcp

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": "http://127.0.0.1:18890",
        "DELEGA_AGENT_KEY": "dlg_your_agent_key_here"
      }
    }
  }
}

Environment Variables

For the hosted tier, use https://api.delega.dev as the URL.

Security Notes

• Non-local DELEGA_API_URL values must use https://.
• 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=1 in production. This flag exists for initial setup only. In production, a prompt-injected agent could exfiltrate keys from create_agent or list_agents tool output. Keys are returned once at creation time; use rotate_agent_key if you need a new one.

Tools

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: no

Assigned to / Created by / Completed by lines are emitted only when the underlying field is populated. Self-hosted Delega returns a nested agent object so the assignee renders as <display_name> (#id); the hosted api.delega.dev tier 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.

Delegation 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).

Self-Hosted vs Hosted

Self-hosted (free): Run your own Delega instance, point DELEGA_API_URL at it.

Hosted: Use https://api.delega.dev — free up to 1,000 tasks/month.

Links

• Delega — Main site
• GitHub — Source code
• API Docs — REST API reference

License

MIT