Clickup MCP vs Megaplan MCP
A side-by-side look at the Clickup MCP and Megaplan MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Clickup MCP for workplace & productivity work as a local process; choose Megaplan MCP for workplace & productivity as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Clickup 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:
CLICKUP_API_TOKEN, CLICKUP_TEAM_ID. - You want tools like
clickup_whoami, clickup_get_spaces, clickup_get_folders.
Choose Megaplan MCP when
- You need dedicated capabilities in the Workplace & Productivity domain.
- You prefer a local stdio subprocess transport.
- You have the keys it needs:
MEGAPLAN_DOMAIN, MEGAPLAN_TOKEN, MEGAPLAN_LOGIN, MEGAPLAN_PASSWORD, PORT. - You want tools like
get_tasks, get_task, create_task.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Workplace & Productivity | Workplace & Productivity |
| Quality signal | 64/100 · Good | 57/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | API key required | Not declared |
| Pricing | Not declared | Not declared |
| Required env vars | CLICKUP_API_TOKENCLICKUP_TEAM_ID | MEGAPLAN_DOMAINMEGAPLAN_TOKENMEGAPLAN_LOGINMEGAPLAN_PASSWORDPORT |
| Verified owner | Community listing | Community listing |
| GitHub stars | 4 | 2 |
| Directory activity | 2 views 0 installs 0 upvotes | 2 views 0 installs 0 upvotes |
| Tools | 40 | 18 |
| Full listing | View Clickup MCP | View Megaplan MCP |
Tools & capabilities
Clickup MCP tools 40
clickup_whoamiGet current user info and list of workspaces with membersclickup_get_spacesList all spaces in a workspaceclickup_get_foldersList folders in a space (includes nested lists)clickup_get_listsGet lists in a folder, or folderless lists in a space. Provide either folder_id or space_id.clickup_get_listGet a single list's details including its statusesclickup_create_listCreate a new list in a folder or as a folderless list in a spaceclickup_delete_listDelete a list. This is permanent and cannot be undone.clickup_get_taskGet a task by its IDclickup_create_taskCreate a new task in a listclickup_update_taskUpdate a task. Assignees use add/rem arrays, not a flat list.clickup_get_tasksList tasks in a list with optional filtersclickup_search_tasksSearch tasks across an entire workspace- +28 more on the listing page
Megaplan MCP tools 18
get_tasksList tasks from Megaplan, filtered by status code(s), responsible user, and free-text search.get_taskGet a single Megaplan task by ID with full details.create_taskCreate a task in Megaplan with name, description, responsible user, and deadline.update_taskUpdate an existing Megaplan task (name, description, responsible, deadline, status).get_dealsList deals from Megaplan, filtered by status code(s), responsible user, and free-text search.get_dealGet a single Megaplan deal by ID with full details.create_dealCreate a deal in Megaplan. Requires a program (pipeline) ID — discover it via get_deal_programs.update_dealUpdate an existing Megaplan deal (name, responsible, amount, description, status).get_projectsList projects from Megaplan, filtered by status code(s) and free-text search.get_projectGet a single Megaplan project by ID with full details.get_employeesList employees from Megaplan with free-text search and department filter.get_deal_programsList deal programs (pipelines). Use this to find the program_id required by create_deal.- +6 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.
Clickup MCP
{
"mcpServers": {
"clickup-mcp": {
"command": "npx",
"args": [
"@cavort-it-systems/clickup-mcp"
],
"env": {
"CLICKUP_API_TOKEN": "YOUR_CLICKUP_API_TOKEN_HERE",
"CLICKUP_TEAM_ID": "YOUR_CLICKUP_TEAM_ID_HERE"
}
}
}
}
Megaplan MCP
{
"mcpServers": {
"megaplan-mcp": {
"command": "npx",
"args": [
"-y",
"@theyahia/megaplan-mcp"
],
"env": {
"MEGAPLAN_DOMAIN": "YOUR_MEGAPLAN_DOMAIN_HERE",
"MEGAPLAN_TOKEN": "YOUR_MEGAPLAN_TOKEN_HERE",
"MEGAPLAN_LOGIN": "YOUR_MEGAPLAN_LOGIN_HERE",
"MEGAPLAN_PASSWORD": "YOUR_MEGAPLAN_PASSWORD_HERE",
"PORT": "YOUR_PORT_HERE"
}
}
}
}
Frequently asked questions
Clickup MCP is categorized under Workplace & Productivity and uses a local stdio subprocess. Megaplan MCP belongs to Workplace & Productivity and uses a local stdio subprocess. Pick Clickup MCP for workplace & productivity work and Megaplan MCP 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.
Clickup MCP has no declared pricing — check the project's own site. Auth: api key required. Megaplan MCP has no declared pricing — check the project's own site. 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 clickup-mcp and megaplan-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Clickup MCP has a quality signal of 64/100 (Good) with 2 views, 0 installs and 4 GitHub stars. Megaplan MCP has 57/100 (Good) with 2 views, 0 installs and 2 GitHub stars.