Megaplan MCP vs Keepsake MCP
A side-by-side look at the Megaplan MCP and Keepsake MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Megaplan MCP for workplace & productivity work as a local process; choose Keepsake 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 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.
Choose Keepsake 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:
KEEPSAKE_API_KEY. - You want tools like
list_contacts, get_contact, create_contact.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Workplace & Productivity | Workplace & Productivity |
| Quality signal | 59/100 · Good | 60/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | Not declared | API key required |
| Pricing | Not declared | BYOK (pay the provider) |
| Required env vars | MEGAPLAN_DOMAINMEGAPLAN_TOKENMEGAPLAN_LOGINMEGAPLAN_PASSWORDPORT | KEEPSAKE_API_KEY |
| Verified owner | Community listing | Community listing |
| GitHub stars | 2 | 1 |
| Directory activity | 1 views 0 installs 0 upvotes | 3 views 0 installs 0 upvotes |
| Tools | 18 | 80 |
| Full listing | View Megaplan MCP | View Keepsake MCP |
Tools & capabilities
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
Keepsake MCP tools 80
list_contactsList contacts with pagination, sorting, field selection and filters (linked company, has_company, updated_since)get_contactGet a contact with recent interactions, tags, and statscreate_contactCreate a new contact (`company` links it to a company record, created if missing)update_contactUpdate contact fieldsdelete_contactPermanently delete a contactsearch_contactsAccent-insensitive search by name, email, notes, phone and linked company namesget_contact_timelineUnified chronological feed of all items for a contactlist_companiesList all companiesget_companyGet company with linked contacts and tagscreate_companyCreate a new companyupdate_companyUpdate company fieldsdelete_companySoft-delete (or permanent delete) a company- +68 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.
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"
}
}
}
}
Keepsake MCP
{
"mcpServers": {
"nicolascroce-keepsake-mcp": {
"command": "npx",
"args": [
"-y",
"keepsake-mcp"
],
"env": {
"KEEPSAKE_API_KEY": "YOUR_KEEPSAKE_API_KEY_HERE"
}
}
}
}
Frequently asked questions
Megaplan MCP is categorized under Workplace & Productivity and uses a local stdio subprocess. Keepsake MCP belongs to Workplace & Productivity and uses a local stdio subprocess. Pick Megaplan MCP for workplace & productivity work and Keepsake 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.
Megaplan MCP has no declared pricing — check the project's own site. Keepsake MCP is bring-your-own-key: usage is billed by the API provider you supply a key for. 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 megaplan-mcp and nicolascroce-keepsake-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Megaplan MCP has a quality signal of 59/100 (Good) with 1 views, 0 installs and 2 GitHub stars. Keepsake MCP has 60/100 (Good) with 3 views, 0 installs and 1 GitHub stars.