Keepsake MCP vs Timergy
A side-by-side look at the Keepsake MCP and Timergy MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Keepsake MCP for workplace & productivity work as a local process; choose Timergy 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 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.
Choose Timergy when
- You need dedicated capabilities in the Workplace & Productivity domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: No auth required.
- You want tools like
create_poll, get_poll, vote_on_poll.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Workplace & Productivity | Workplace & Productivity |
| Quality signal | 60/100 · Good | 57/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | API key required | No auth required |
| Pricing | BYOK (pay the provider) | Free |
| Required env vars | KEEPSAKE_API_KEY | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 1 | 1 |
| Directory activity | 3 views 0 installs 0 upvotes | 2 views 0 installs 0 upvotes |
| Tools | 80 | 22 |
| Full listing | View Keepsake MCP | View Timergy |
Tools & capabilities
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
Timergy tools 22
create_pollCreate a Timergy scheduling poll (like Doodle) where participants vote on preferred time slots. Provide a title and at least 2-5 time slot options with ISO 8601 date-times (include timezone, e.g. 2026-03-20T18:00:00+02:00 or use UTC with Z suffix). Returns a shareable URL to send to participants and a passphrase for admin access. The passphrase is automatically remembered for finalize_poll. If an API key or OAuth token is configured, the poll is created on the user's account instead (no passphrase; update_poll, invite_to_poll, list_my_polls and finalize work via the same auth). Set autoFinalize=true with a deadline to automatically pick the best option when the deadline passes. Use invitees to send email invitations with direct voting links. Workflow: create_poll -> share URL -> wait for votes -> get_results -> finalize_poll (or use auto-finalize).get_pollGet poll metadata and time slot options (but NOT votes). Returns title, status, deadline, location, and all available time slots with their option IDs. Use this to retrieve optionId values needed for vote_on_poll or finalize_poll. To see who voted, use get_results instead.vote_on_pollSubmit votes on a Timergy poll. First call get_poll to retrieve the available optionId values. Each vote maps an optionId to an availability: 'yes' (available), 'maybe' (might work), or 'no' (unavailable). A unique voter token is auto-generated per voter name. Resubmitting with the same voter name updates previous votes.get_resultsGet voting results for a Timergy poll, showing who voted yes/maybe/no for each time slot. Use this after participants have voted to see which slot has the most availability. To finalize, pick the optionId with the most 'yes' votes and call finalize_poll.finalize_pollFinalize a poll by picking the winning time slot. Call get_results first to find the best optionId. Uses the passphrase auto-saved from create_poll. If the MCP server was restarted since poll creation, provide the passphrase manually. Account-linked polls (created with API key/OAuth configured) have no passphrase; they are finalized via the same auth. This locks the poll and notifies participants who provided an email.suggest_best_optionAnalyze votes and suggest the best time slot for a poll. Returns all options ranked by score (yes=1, maybe=0.5). Tiebreaker: fewest no-votes, then earliest start. Use this before finalize_poll to let the AI pick the optimal slot, or to show the user a recommendation.send_reminderSend email reminders to poll participants who haven't voted yet. Requires the passphrase from create_poll (or API key/OAuth auth for account-linked polls). Only works for polls with invitations (email-based). Returns the number of emails sent and how many people already voted.auto_finalizeAutomatically finalize a poll by picking the best-scored time slot. Combines suggest_best_option + finalize_poll in one step. Requires the passphrase from create_poll (or API key/OAuth auth for account-linked polls). Notifies all participants.check_conflictsCheck which poll time slots conflict with the creator's calendar events. Requires authentication via per-call oauthToken/apiKey, or pre-configured via --oauth-token/--api-key CLI flags. Returns each option with conflict status, conflicting event names, and conflictEventDetails (eventId, connectionId, provider) usable with ignore_event. Use this to help the creator avoid double-booking.list_contactsSearch the user's Timergy address book by name or email. Use this before inviting people to find their email addresses. Contacts are auto-captured from invitations, votes, bookings, and Meeting Autopilot groups. Requires authentication via per-call oauthToken/apiKey, or pre-configured via --oauth-token/--api-key CLI flags. Optional query parameter to filter results.invite_to_pollInvite people to an existing poll by email. Use list_contacts first to find email addresses. Requires authentication via per-call oauthToken/apiKey, or pre-configured via --oauth-token/--api-key CLI flags. The poll must be open and owned by the authenticated user (create it with auth configured). Invitees receive an email with a direct voting link. Max 50 invitees per call.create_surveyCreate a Timergy survey (choice poll) where participants vote on text options instead of time slots. Provide a title and at least 2 text options (e.g. restaurant names, activity choices). Returns a shareable URL and a passphrase for admin access. Use for decisions like 'Where should we eat?', 'Which logo?', 'What activity?'. Workflow: create_survey -> share URL -> wait for votes -> get_results -> finalize_poll.- +10 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.
Keepsake MCP
{
"mcpServers": {
"nicolascroce-keepsake-mcp": {
"command": "npx",
"args": [
"-y",
"keepsake-mcp"
],
"env": {
"KEEPSAKE_API_KEY": "YOUR_KEEPSAKE_API_KEY_HERE"
}
}
}
}
Timergy
{
"mcpServers": {
"timergy-app-timergy": {
"command": "npx",
"args": [
"@timergy/mcp"
]
}
}
}
Frequently asked questions
Keepsake MCP is categorized under Workplace & Productivity and uses a local stdio subprocess. Timergy belongs to Workplace & Productivity and uses a local stdio subprocess. Pick Keepsake MCP for workplace & productivity work and Timergy 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.
Keepsake MCP is bring-your-own-key: usage is billed by the API provider you supply a key for. Auth: api key required. Timergy is listed as free. Auth: no auth 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 nicolascroce-keepsake-mcp and timergy-app-timergy as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Keepsake MCP has a quality signal of 60/100 (Good) with 3 views, 0 installs and 1 GitHub stars. Timergy has 57/100 (Good) with 2 views, 0 installs and 1 GitHub stars.
