F
licenseNot graded
qualityB
maintenanceMCP server that provides tools to create and list tasks by consuming a REST API, allowing LLMs to manage a TODO list via natural language.
-
tocaro-mcp
Related Servers
Alternatives to tocaro-mcp
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityBmaintenanceMCP server for managing todo tasks, exposing tasks resource, add/complete task tools, and a daily summary prompt.-
- FlicenseNot gradedqualityCmaintenanceAn MCP server that provides todo management tools (add, list, complete, clear, summarize) and a resource for reading all todos, enabling Codex or other MCP clients to organize and track tasks via natural language.-
- 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.-
- FlicenseCqualityCmaintenanceA simple MCP server demonstrating resources, tools, and prompts using a local task list. It enables reading, creating, and analyzing tasks through MCP.1-
- 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.-
TDQS
A4.2/5.0
Scored across 10 tools
Disambiguation5/5
Each tool targets a distinct resource and action: users search, group members, groups, todo lists, tasks, and messages. Even where two tools return user codes, their scope is clearly separated (all users vs group members). No two tools appear to do the same thing.
Naming Consistency5/5
All tools follow the consistent `tocaro_<verb>_<noun>` pattern in snake_case. Verbs like search/list/get/create/invite/post are used predictably and match the operation performed. There are no mixed conventions or irregular names.
Tool Count5/5
Ten tools is well within the ideal range for a domain-specific server. Each tool covers a meaningful operation for Tocaro group, user, messaging, and task workflows without unnecessary duplication. The count feels appropriately scoped rather than sparse or bloated.
Completeness3/5
The surface covers creation and retrieval flows for groups, todo lists, and tasks, but missing update/delete operations leave obvious lifecycle gaps. There is also no way to read messages despite having post_message, which limits conversational workflows. The domain is clear, but several common operations are absent.
Maintenance
ActivityMaintained
ResponsivenessNo issues