A
licenseNot graded
qualityC
maintenanceMCP server for Todoist API integration, allowing management of tasks, projects, sections, labels, and comments through natural language.
9 npm
MIT
Bullet MCP
by davebream
Related Servers
Alternatives to Bullet MCP
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityFmaintenanceMCP server for TickTick task management. Enables AI assistants to create, update, list, search, and complete tasks via natural language.53 npm29MIT
- AlicenseAqualityDmaintenanceAn MCP server that enables LLM clients to manage tasks, timers, and notes in Rhizm through natural language commands. It provides tools for task operations, time tracking, and note management via API integration.116 npmMIT
- FlicenseNot gradedqualityDmaintenanceMCP server that exposes a TODO list API to AI assistants, enabling natural language management of tasks with create, read, update, and delete operations.-
- FlicenseNot gradedqualityCmaintenanceA simple MCP server that turns a JSON file into a todo list, letting users add, list, complete, delete, and clear tasks through natural language in MCP-compatible clients.-
- AlicenseAqualityAmaintenanceMCP server for Taskboi task management, enabling project and task operations with recurrence and priority support via the Taskboi API.164 npmApache 2.0
TDQS
A3.8/5.0
Scored across 10 tools
Disambiguation4/5
Most tools have clear, distinct purposes: entry CRUD, collection read, tag read. The only potential confusion is between list_entries and list_current, as both return scheduled items, but the descriptions clarify list_current is for the current period/overdue while list_entries uses presets or calendar queries.
Naming Consistency4/5
The naming follows a consistent verb_noun pattern for the majority of tools: list_entries, create_entry, get_entry, update_entry, delete_entry, list_collections, get_collection, list_tags, get_tag. The outlier is list_current, which uses an adjective instead of a noun, but it's still readable and not jarring.
Tool Count5/5
With 10 tools, the server is well-scoped for its purpose of managing Bullet entries and referencing collections/tags. Each tool serves a distinct function and the count is within the ideal 3-15 range, making the surface neither too sparse nor overwhelming.
Completeness2/5
Entry CRUD is partially covered: create, list, get, and delete are present, but update_entry only changes the title, leaving no way to update status, schedule, or associations. Collections and tags are read-only, with no create/update/delete, so agents cannot manage these entities through the server, which is a significant functional gap.
Maintenance
ActivityInactive
ResponsivenessNo issues