Side-by-Side Model Context Protocol Comparison
Kanboard MCP vs Keepsake MCP
In-depth architectural comparison of the Kanboard MCP and Keepsake 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
Kanboard MCP
Workplace & Productivity · Local stdio
Quality: 60/100 (Good) | Auth: API Key required
Keepsake MCP
Workplace & Productivity · Local stdio
Quality: 59/100 (Good) | Auth: API Key required
Verdict Summary: Choose Kanboard MCP if you need specialized Workplace & Productivity tools running via a local process. Choose Keepsake 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 Kanboard 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 (Free / Open Source).
- You have access to required keys:
KANBOARD_URL, KANBOARD_USERNAME, KANBOARD_API_TOKEN. - Primary tools included: add_project_user, attach_file_to_task, close_task.
Choose Keepsake 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:
KEEPSAKE_API_KEY. - Primary tools included: .
Feature & Specification Comparison
Tools & Capabilities Breakdown
Kanboard MCP Tools (39)
add_project_user
Add a user to a Kanboard project with the given role. Role defaults to 'project-member' if not specified. Use list_project_users to find user ids and list_projects to find project ids; to unlink a member use remove_project_user. Returns { user_id, project_id, role } on success.
attach_file_to_task
Upload a file to a Kanboard task as an attachment. Provide either file_path (local file) or content_base64 (inline base64 content) — not both. project_id is resolved automatically from the task (no need to provide it). Maximum file size: 5 MB (5,242,880 bytes) — larger files return VALIDATION_ERROR before any HTTP request is made. Returns { file_id } on success.
close_task
Close (archive) an active Kanboard task. The task is set inactive and leaves the active board but is preserved — this is NOT a delete. Reversible: restore it with reopen_task. To permanently remove a task instead, use delete_task. Returns { ok: true, task_id } on success.
create_column
Add a column to a Kanboard project board. Project resolved from explicit project_id/project_identifier or .kanboard.yaml. To reorder it use move_column, to rename or change its WIP limit use update_column, to remove it use delete_column. Returns { column_id } on success.
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).
Kanboard MCP Configuration
Keepsake MCP Configuration
Frequently Asked Questions
More alternatives to Kanboard MCPMore alternatives to Keepsake MCPWorkplace & Productivity category hub