MCP Server for ZenTao bug management with CAS SSO login
from $14/mo
Nothing to run from here
Delega is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
Open Installation—
p95 latency
—
call success
local
runs on your machine
—
calls last 7d
What it does
MCP server for Delega — task infrastructure for AI agents
Quickstart
# 1 — run it from where its publisher ships it
npx -y delega-mcp
# 2 — ask your agent something
> MCP server for Delega — task infrastructure for AI agents
Delega is free: there is no plan to choose, no cap to set and nothing that can bill you.
Publishernot claimed
DEAll 2 servers
delega-dev2 servers
2 categories
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. This one runs on your machine: your client starts Delega as a process under your own user, with your files and your network, so the tool surface below is what it can do to your computer rather than to a server somewhere else. It is scanned, signed and pinned to the version you choose — read the surface before you approve it.
Claude Codedeclared by this listing
This is a public server: you run it yourself and this marketplace is not in the path. Claude Code registers it in one command.
claude mcp add delega-mcp -- npx -y delega-mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
Free to install, and it runs from its publisher’s own package: no account, no key, no card.
What it asks of you
It reaches a system of yours, so it needs your own credential rather than the publisher’s: DELEGA_API_KEY. You set it after installing; the value is sealed here and sent to the server on each call.
What it writes
One config entry your client uses to start the process locally. A local server runs with your file system and your network, which is why it is priced without metering.
What you approve
44 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
List tasks from Delega. Visibility depends on your role: workers see tasks they created, were assigned, completed, or claimed; coordinators and admins see all account tasks — including other agents
Takes no parameters.
Example callreturns →
Get full details of a specific task including subtasks
Takes no parameters.
Example callreturns →
Attach a branch, commit, pull request, or URL link to a task. Use this when work in a repo, PR, or external artifact should travel with the task.
Takes no parameters.
Example callreturns →
List branch, commit, pull request, and URL links attached to a task.
Takes no parameters.
Example callreturns →
Create a new task in Delega
Takes no parameters.
Example callreturns →
List recurring task templates. Recurrences spawn normal task instances on schedule; completing an instance does not delete the schedule.
Takes no parameters.
Example callreturns →
Create a recurring task template. The hosted scheduler spawns normal task instances from this template and links them with source_recurrence_id.
Takes no parameters.
Example callreturns →
Update a recurring task template, including pausing/resuming with active=false/true.
Takes no parameters.
Example callreturns →
Delete a recurring task template. Existing spawned task instances remain as normal tasks.
Takes no parameters.
Example callreturns →
Update an existing task
Takes no parameters.
Example callreturns →
Assign a task to an agent (or unassign by passing null)
Takes no parameters.
Example callreturns →
Delegate a task: create a child task linked to a parent. The parent
Takes no parameters.
Example callreturns →
Get the full delegation chain for a task (root + all descendants, sorted by depth). Use this to inspect parent/child accountability.
Takes no parameters.
Example callreturns →
Read a task
Takes no parameters.
Example callreturns →
Merge keys into a task
Takes no parameters.
Example callreturns →
Read the append-only provenance ledger for a task
Takes no parameters.
Example callreturns →
Check whether a proposed task is similar to existing open tasks (TF-IDF + cosine similarity). Call this before create_task to avoid redundant work.
Takes no parameters.
Example callreturns →
Get quota and rate-limit information for the current plan. Hosted API only (api.delega.dev) — custom endpoints receive a clear error.
Takes no parameters.
Example callreturns →
Mark a task as completed. Attach
Takes no parameters.
Example callreturns →
Takes no parameters.
Example callreturns →
Takes no parameters.
Example callreturns →
Takes no parameters.
Example callreturns →
Release a task you have claimed back to the queue without completing it. Use when you cannot finish the work or another agent should take over — the task returns to open status and becomes immediately claimable. Leave a
Takes no parameters.
Example callreturns →
Takes no parameters.
Example callreturns →
Triage board: one call returning everything across the account that needs a human or coordinator — abandoned claims (a crashed/silent agent
Takes no parameters.
Example callreturns →
Delete a task permanently
Takes no parameters.
Example callreturns →
Add a comment to a task
Takes no parameters.
Example callreturns →
List all projects in Delega
Takes no parameters.
Example callreturns →
Get task statistics from Delega (totals, completed today, due today, overdue, by project)
Takes no parameters.
Example callreturns →
List all registered agents in Delega. Admin keys get the full view; coordinators get a read-only directory (name, role, activity) for resolving agent IDs on tasks.
Takes no parameters.
Example callreturns →
Register a new agent in Delega. Returns the API key (shown only at creation — save it!)
Takes no parameters.
Example callreturns →
Set an agent
Takes no parameters.
Example callreturns →
Delete an agent. The API may refuse if the agent has active tasks or is the last active agent.
Takes no parameters.
Example callreturns →
List all webhooks configured for your account (admin only)
Takes no parameters.
Example callreturns →
Create a webhook to receive event notifications (admin only). Events: task.created, task.updated, task.completed, task.deleted, task.assigned, task.delegated, task.commented, task.claimed, task.released, task.state_changed, task.linked
Takes no parameters.
Example callreturns →
Delete a webhook by ID (admin only)
Takes no parameters.
Example callreturns →
List all automation rules configured for your account, with run/failure counts (admin only). Hosted API only.
Takes no parameters.
Example callreturns →
Takes no parameters.
Example callreturns →
Update an automation rule (admin only). Only supplied fields change; setting active true re-enables a rule that was auto-disabled after repeated failures. Hosted API only.
Takes no parameters.
Example callreturns →
Delete an automation rule and its run log by ID (admin only). Hosted API only.
Takes no parameters.
Example callreturns →
List inbound connector sources with delivery counters (admin only). Hosted API only.
Takes no parameters.
Example callreturns →
Create an inbound connector: a signed public endpoint that turns external events (CI failures, alerts, calendars) into Delega tasks (admin only). The sender signs each POST body with HMAC-SHA256 (header X-Delega-Ingress-Signature: t=<unix>,v1=<hex of HMAC(secret,
Takes no parameters.
Example callreturns →
Update an inbound connector source (admin only). Only supplied fields change; pass rotate_secret true to mint a new signing secret (shown once — the old secret stops working immediately). Hosted API only.
Takes no parameters.
Example callreturns →
Delete an inbound connector source and its delivery log by ID (admin only). Its endpoint immediately returns 404. Hosted API only.
Takes no parameters.
Example callreturns →
Freeyour plan
$0 forever
- Every tool, no call limit
- No card, no account needed
- Source published under a licence you can read
- Runs on your machine — nothing of it reaches our gateway
- Nothing to cap, because nothing bills
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable. Delega costs nothing to install and nothing to call, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: $8.42
$16.58 left
ATrust score 99 / 100
Release 1.0.0 · scanned 26 Aug 2026
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
Threat score100
Client score99
Findings0 threat · 0 capability
Capabilityminimal
Coveragesource
Verificationrepo
Surface digesta55ee7384c9290616f46d92286fcf05de5b2f845cfe1530c3c12de3b25cdea80
Score vectorthreat 100 → client 99
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | minimal | capability blast radius (minimal) — client exposure if the model is manipulated | −0 |
| verification-discount | repo | publisher verification (public source) — no provenance, but the source is public and inspectable | −1 |
| coverage-honesty | source | inspection depth (source) — how much of the target the scan could see | −0 |
score = clamp(round(threatScore − E_cap − E_ver − E_cov), 0, 100). No model, no opinion, no network call at scoring time: the same methodology version against the same bytes always produces this number, and every line above is a field of the report rather than a summary of it.
What the scan could actually read
A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.
Tool surfaceread
Implementation sourceread
Package metadataread
Live transportnot available
Tools were statically extracted from the published source (11 recovered), not enumerated from a running server. Tool-poisoning, Unicode-smuggling, capability and toxic-flow analysis ran on this inferred surface, but a mis-parsed registration could be missed or mis-attributed, so tool-derived findings are capped below “confirmed”. To grade the real runtime surface, scan the running server: --command "npx -y <package>".
Capability — what it could do if the model were manipulated
Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. minimal is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| list_tasks | no tags | |
| get_task | no tags | |
| create_task | no tags | |
| update_task | no tags | |
| complete_task | no tags | |
| delete_task | no tags | |
| add_comment | no tags | |
| list_projects | no tags | |
| get_stats | no tags | |
| list_agents | no tags | |
| register_agent | no tags |
Toxic-flow graph
The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.
The public result for this release does not print the flow graph, so there is nothing to show here. That is not the same as "no paths were found": what the scan did read is above, under coverage.
Supply chain and provenance
Integrityfirst-seen
Surface digesta55ee7384c929061
Scanned2026-08-26
This is the first scan of this surface here, so there is nothing yet to compare it against.
Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.
Release history
Pinned to 1.0.0 — the install command below asks for that release. A pin is part of an install, so it is kept for this visit and written down when you install.
1.0.0
undated
installedNo release note was published with this version.
—
no reviews yet
Reviews are earned
Only accounts with at least 50 real tool calls against this server in the last 90 days can post. Ratings are weighted by how much the reviewer actually uses it, and publishers can reply once per review.
Reviews are earned
Writing one takes an account with at least 50 real tool calls against Delega in the last 90 days. That is the whole gate — there is no other way to post, which is why the counts beside each review are worth reading.
No reviews yet
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes an account with 50 real tool calls against it.