Delega MCP Server

Task management API for AI agents. Create, delegate, and track tasks via MCP.

Remote serverstreamable-http

What is the Delega MCP server?

Most planning and project tracking work still happens through a UI a human drives. Delega MCP server moves it into the conversation instead. Task management API for AI agents. Create, delegate, and track tasks via MCP.

The short version

MCP server for Delega — a production task-coordination system for AI agents.

Getting it running

Because this one is hosted, setup is mostly authentication — you point your client at the endpoint and approve access. Nothing runs on your machine, so there is no runtime to keep patched.

The tools it exposes

The server publishes 14 tools. What each one is for:

  • list_tasks — List tasks, filter by project, label, due date, completion
  • get_task — Get full task details including subtasks and task links
  • link_task — Attach a branch, commit, PR, or URL link to a task
  • list_task_links — List branch, commit, PR, and URL links attached to a task
  • create_task — Create a new task (optional evidence_policy: 'required' forces completion evidence)
  • list_recurrences — List recurring task templates
  • create_recurring_task — Create a recurring task template (daily, weekly, monthly, or yearly)
  • update_recurrence — Update a recurring task template, including pausing/resuming with active
  • delete_recurrence — Delete a recurring task template; existing spawned task instances remain
  • update_task — Update task fields (incl. assigned_to_agent_id)
  • assign_task — Assign a task to an agent (or pass null to unassign)
  • delegate_task — Delegate a task: create a child task linked to a parent (parent status flips to delegated). Use this for multi-agent handoffs — assign_task does not

What it needs from you

Configuration is passed through the environment: DELEGA_API_URL, DELEGA_AGENT_KEY, DELEGA_API_KEY. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.

Things to watch

  • Your data travels to the provider's service, so the usual questions apply about what you send and what they retain.
  • With 14 tools registered it takes up a noticeable share of the context window; turn it off in projects that never touch Delega.
  • Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
  • Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.

How it compares

Plenty of planning and project tracking servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Delega's toolset — list_tasks, get_task, link_task and 11 more — is a fair guide to whether it matches your workflow. It is maintained by delega-dev; worth a glance at recent repository activity before you build anything load-bearing on it.

SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.

Available tools

ToolWhat it does
list_tasksList tasks, filter by project, label, due date, completion
get_taskGet full task details including subtasks and task links
link_taskAttach a branch, commit, PR, or URL link to a task
list_task_linksList branch, commit, PR, and URL links attached to a task
create_taskCreate a new task (optional evidence_policy: 'required' forces completion evidence)
list_recurrencesList recurring task templates
create_recurring_taskCreate a recurring task template (daily, weekly, monthly, or yearly)
update_recurrenceUpdate a recurring task template, including pausing/resuming with active
delete_recurrenceDelete a recurring task template; existing spawned task instances remain
update_taskUpdate task fields (incl. assigned_to_agent_id)
assign_taskAssign a task to an agent (or pass null to unassign)
delegate_taskDelegate a task: create a child task linked to a parent (parent status flips to delegated). Use this for multi-agent handoffs — assign_task does not create a delegation chain.
get_task_chainReturn the full delegation chain for a task (root + descendants, sorted by depth)
update_task_contextMerge keys into a task's persistent context blob (deep merge, not replace), recording provenance source

How to install the Delega MCP server

{
  "mcpServers": {
    "delega": {
      "command": "npx",
      "args": ["-y", "@delega-dev/mcp"],
      "env": {
        "DELEGA_API_URL": "your-value",
        "DELEGA_AGENT_KEY": "your-value",
        "DELEGA_API_KEY": "your-value"
      }
    }
  }
}

Add to claude_desktop_config.json, then restart Claude Desktop.

Configuration

VariableDescriptionRequired
DELEGA_API_URLEndpoint or connection string the server talks to.Yes
DELEGA_AGENT_KEYCredential the server authenticates with.Yes
DELEGA_API_KEYCredential the server authenticates with.Yes

Example prompts to try

  • Use Delega to list tasks.
  • Use Delega to get task.
  • Use Delega to link task.

Frequently asked questions

It connects Delega to MCP-compatible AI assistants such as Claude and Cursor, exposing 14 tools (list_tasks, get_task, link_task, and more) that the assistant can call on your behalf. Instead of copying data back and forth by hand, the assistant works with Delega directly.