Delega MCP vs Primer MCP — MCP Server Comparison | AllMCPs
Side-by-Side Model Context Protocol Comparison
Delega MCP vs Primer MCP
In-depth architectural comparison of the Delega MCP and Primer MCP MCP servers. Compare execution transports, security boundaries, tool capabilities, quality scores, and ready-to-paste client installation snippets for Claude, Cursor, Windsurf, and VS Code.
At a Glance & Executive Verdict
Delega MCP
Workplace & Productivity · Local stdio
Quality: 63/100 (Good) | Auth: API Key required
Primer MCP
Workplace & Productivity · Local stdio
Quality: 52/100 (Good) | Auth: No auth required
Verdict Summary: Choose Delega MCP if you need specialized Workplace & Productivity tools running via a local process. Choose Primer MCP if your workspace requires Workplace & Productivity integration with local subprocess execution. Both servers can be configured concurrently in your client's mcpServers manifest.
Which MCP Server Should You Choose?
Choose Delega MCP when:
You need dedicated capabilities in the Workplace & Productivity domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: API Key required (BYOK (Pay Provider Direct)).
You have access to required keys: DELEGA_API_URL, DELEGA_AGENT_KEY, DELEGA_API_KEY, DELEGA_REVEAL_AGENT_KEYS, DELEGA_REVEAL_WEBHOOK_SECRETS.
Task management API built for AI agents. Create, delegate, and track tasks with agent identity, delegation chains, lifecycle webhooks, and persistent context. Self-hosted or hosted tier at delega.dev.
A Jira-lite MCP server that guides planning-first workflows for AI-assisted development.
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' 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_task
Get full details of a specific task including subtasks
link_task
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.
list_task_links
List branch, commit, pull request, and URL links attached to a task.
create_task
Ready-to-Paste Client Configurations
Paste either (or both) of these JSON server blocks into your client config file (e.g. claude_desktop_config.json or ~/.cursor/mcp.json).
Delega MCP is categorized under Workplace & Productivity and uses a local stdio subprocess. In contrast, Primer MCP belongs to Workplace & Productivity using local stdio subprocess. Select Delega MCP when you need capabilities focused on workplace & productivity and Primer MCP when you require tools for workplace & productivity.
List recurring task templates. Recurrences spawn normal task instances on schedule; completing an instance does not delete the schedule.
create_recurring_task
Create a recurring task template. The hosted scheduler spawns normal task instances from this template and links them with source_recurrence_id.
update_recurrence
Update a recurring task template, including pausing/resuming with active=false/true.
delete_recurrence
Delete a recurring task template. Existing spawned task instances remain as normal tasks.
update_task
Update an existing task's fields
assign_task
Assign a task to an agent (or unassign by passing null)
delegate_task
Delegate 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 tools listed on main page
Primer MCP Tools (15)
init_project
Create the `primer/` ticket store and add the workflow section to CLAUDE.md
plan_epic
Create an epic — the top-level container for a body of work
record_adr
Record an architecture decision: context, decision, rejected alternatives, consequences
create_story
Create a story under an epic — a deliverable with acceptance criteria
create_task
Create a task under a story — a concrete unit of work with a testable outcome
create_spike
Create a spike — a timeboxed investigation to answer a question
start_task
Move a task to in-progress
complete_task
Mark a task completed with notes on what was done
verify_task
Verify a completed task with evidence (point at the commit)
complete_spike
Close a spike with findings
list_actionable
List what can be acted on right now, with epic context and recommendations