Delega MCP vs Dreamwork
A side-by-side look at the Delega MCP and Dreamwork MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Delega MCP for workplace & productivity work as a local process; choose Dreamwork for workplace & productivity over a hosted endpoint. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Delega MCP when
- You need dedicated capabilities in the Workplace & Productivity domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: API key required.
- You have the keys it needs:
DELEGA_API_URL, DELEGA_AGENT_KEY, DELEGA_API_KEY, DELEGA_REVEAL_AGENT_KEYS, DELEGA_REVEAL_WEBHOOK_SECRETS. - You want tools like
list_tasks, get_task, link_task.
Choose Dreamwork when
- You need dedicated capabilities in the Workplace & Productivity domain.
- You prefer a remote HTTP/SSE transport.
- Its auth model fits you: API key required.
- You want tools like
list_matches, get_job, save_job.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Workplace & Productivity | Workplace & Productivity |
| Quality signal | 64/100 · Good | 71/100 · Great |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Remote HTTP/SSE |
| Auth | API key required | API key required |
| Pricing | BYOK (pay the provider) | Not declared |
| Required env vars | DELEGA_API_URLDELEGA_AGENT_KEYDELEGA_API_KEYDELEGA_REVEAL_AGENT_KEYSDELEGA_REVEAL_WEBHOOK_SECRETS | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 1 | 11 |
| Directory activity | 4 views 0 installs 0 upvotes | 2 views 0 installs 0 upvotes |
| Tools | 44 | 69 |
| Full listing | View Delega MCP | View Dreamwork |
Tools & capabilities
Delega MCP tools 44
list_tasksList 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' work, so act only on tasks assigned to you or unowned ones you claim, and coordinate on teammates' tasks via add_comment. Optionally filtered by project, label, due date, or completion status. To resume work at the start of a session, call with completed:false, then use get_task_context on your tasks to recover prior decisions and state instead of starting from zero.get_taskGet full details of a specific task including subtaskslink_taskAttach 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.list_task_linksList branch, commit, pull request, and URL links attached to a task.create_taskCreate a new task in Delegalist_recurrencesList recurring task templates. Recurrences spawn normal task instances on schedule; completing an instance does not delete the schedule.create_recurring_taskCreate a recurring task template. The hosted scheduler spawns normal task instances from this template and links them with source_recurrence_id.update_recurrenceUpdate a recurring task template, including pausing/resuming with active=false/true.delete_recurrenceDelete a recurring task template. Existing spawned task instances remain as normal tasks.update_taskUpdate an existing task's fieldsassign_taskAssign a task to an agent (or unassign by passing null)delegate_taskDelegate a task: create a child task linked to a parent. The parent's status flips to 'delegated'. Use this (not assign_task) for multi-agent handoffs so the delegation chain is recorded.- +32 more on the listing page
Dreamwork tools 69
list_matchesReturns the account's ranked live match pool with job id, its Dreamwork page url, title, company, location, remote terms, salary, dates, match percent and saved/applied state. Filters narrow that pool; nextCursor continues a page with identical filters, and null ends the walk. A page holds 10 jobs by default and limit accepts up to 50; the next page is the previous nextCursor, which keeps the page size it was issued with. addedAfter supports overlapping discovery windows because listings can become servable after first discovery. notes describe applied filters and coverage.get_jobReturns one saved or corpus role by id with full description, company, location and remote terms, salary, posted date, match score, saved state, board column, application id, material readiness and work-eligibility verdict. url is the Dreamwork listing page; sourceUrl is the employer's direct posting. eligible is true for an unrestricted role or a confirmed allowed country, false for a high-confidence restriction excluding confirmed countries, and null when eligibility is unknown. Only false blocks applying or Autopilot: null means eligibility is not yet known, so proceed with applying — the application itself surfaces any real restriction. whyItMatches may be empty when no matcher explanation is stored.save_jobSaves one role to the account's pipeline at SAVED as a bookmark. No application is submitted or queued until apply is called. Application materials may start preparing in the background. An already saved role returns a no-op receipt.dismiss_matchHides one listing from the account's match feed, job alerts and Autopilot until the account restores or saves it. The receipt offers undo for one minute; restore_match reverses it at any time and list_dismissed_matches lists dismissed listings. The supplied reason is not stored. It does not hide other listings from the same company and does not move or remove an existing pipeline card.restore_matchReverses a dismissal of one listing so it can return to the account's match feed, job alerts and Autopilot. Restoring a listing that is not dismissed returns a no-op receipt. Restoring does not save the listing. A closed listing stays out of the feed.list_dismissed_matchesReturns the account's dismissed listings, newest first, with listing id, title, company, Dreamwork page url, dismissal time and whether the listing is still active. total counts all dismissed listings. limit defaults to 20 and accepts up to 50; nextOffset continues the list and null ends it.get_pipelineReturns saved and applied roles as board cards with column, application id and last-updated time. total and counts cover all matching records; complete identifies whether cards are truncated by limit. limit defaults to 50 cards and accepts up to 100; there is no next page, so when complete is false narrow the read with status. Column values describe board state and do not establish employer receipt or response.move_pipelineMoves one role's board card to the requested column using the account holder's reported state. No employer is contacted. APPLIED records an application rather than submitting one; INTERVIEWING creates a durable interview record. WITHDRAWN removes the card from the active board. Closing a role can remove its listing from the feed. A receipt offers undo only when reversible.mark_applied_offsiteRecords an application the account holder submitted outside Dreamwork. Exactly one of matchId, listingId or url names the role; a role not yet in the pipeline is added in Applied without generating materials, and an unlisted URL is imported in the background. appliedAt (YYYY-MM-DD or ISO 8601, not in the future) is the reported application date and defaults to now; repeating the call with a new appliedAt corrects it. attestation:true is required and represents the person's confirmation that submission occurred. Recorded roles are excluded from matches and Autopilot. Applications Dreamwork is still sending are refused. There is no undo. This call does not send an application.import_jobFetches a public job-posting URL and imports it as a private role in the account's pipeline. Extraction runs asynchronously and the card appears when it finishes. A posting already held by Dreamwork returns completed without another fetch.cancel_applyStops a queued or in-progress application when submission can still be prevented. Already submitted applications cannot be recalled; the receipt reports that boundary.generate_packQueues a tailored resume, cover letter and employer-question answers for one saved role. assets optionally selects a subset; omission requests all three. Each request spends one pack allowance, regardless of subset, and generation settles asynchronously. Existing materials can be overwritten by generation.- +57 more on the listing page
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
Delega MCP
{
"mcpServers": {
"delega-dev-delega-mcp": {
"command": "npx",
"args": [
"-y",
"@delega-dev/mcp"
],
"env": {
"DELEGA_API_URL": "YOUR_DELEGA_API_URL_HERE",
"DELEGA_AGENT_KEY": "YOUR_DELEGA_AGENT_KEY_HERE",
"DELEGA_API_KEY": "YOUR_DELEGA_API_KEY_HERE",
"DELEGA_REVEAL_AGENT_KEYS": "YOUR_DELEGA_REVEAL_AGENT_KEYS_HERE",
"DELEGA_REVEAL_WEBHOOK_SECRETS": "YOUR_DELEGA_REVEAL_WEBHOOK_SECRETS_HERE"
}
}
}
}
Dreamwork
{
"mcpServers": {
"dreamwork-2": {
"command": "npx",
"args": [
"-y",
"@dreamworkhq/mcp"
]
}
}
}
Frequently asked questions
Delega MCP is categorized under Workplace & Productivity and uses a local stdio subprocess. Dreamwork belongs to Workplace & Productivity and uses a remote HTTP/SSE transport. Pick Delega MCP for workplace & productivity work and Dreamwork for workplace & productivity.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
Delega MCP is bring-your-own-key: usage is billed by the API provider you supply a key for. Auth: api key required. Dreamwork has no declared pricing — check the project's own site. Auth: api key required. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add delega-dev-delega-mcp and dreamwork-2 as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Delega MCP has a quality signal of 64/100 (Good) with 4 views, 0 installs and 1 GitHub stars. Dreamwork has 71/100 (Great) with 2 views, 0 installs and 11 GitHub stars.