Akiflow MCP Server
Related Servers
Alternatives to Akiflow MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityAmaintenanceUnofficial MCP server for Akiflow that enables AI agents to manage tasks, projects, and calendar via the Model Context Protocol.236 npmMIT
- AlicenseNot gradedqualityFmaintenanceMCP server for TickTick task management. Enables AI assistants to create, update, list, search, and complete tasks via natural language.16 npm28MIT
- AlicenseNot gradedqualityDmaintenanceEnables AI assistants to manage TickTick tasks, projects, habits, and focus sessions through the MCP server.141MIT
- AlicenseNot gradedqualityBmaintenanceMCP server enabling AI assistants to interact with ClickUp workspaces, including task management, comments, time tracking, and document operations.12 npmMIT
- AlicenseNot gradedqualityDmaintenanceMCP server for the Google Tasks API that enables AI agents to read, create, update, delete, and manage Google Tasks.48 npmMIT
- AlicenseNot gradedqualityDmaintenanceMCP server that enables AI agents to manage Dida365/TickTick tasks, projects, tags, and habits through natural language, with full CRUD, search, and advanced V2 capabilities.2MIT
TDQS
Scored across 22 tools
Each tool targets a distinct action or resource. Even within the task-related tools (add, edit, schedule, timeslot operations), the descriptions clearly differentiate purposes, so an agent can reliably select the correct one.
Most tools follow verb_noun pattern (e.g., add-event, get-tasks). Minor deviations include 'create-task-from-action-item' uses 'create' instead of 'add', and 'mark-done' uses a state instead of a noun. Overall, predictable.
22 tools is somewhat high but justified by the server's broad scope covering tasks, events, time slots, recordings, and briefs. A few tools could be merged (e.g., get-recording and get-recordings), but the count is still reasonable.
The tool surface covers core CRUD for tasks, events, and time slots, plus meeting briefs and recordings. Missing operations include delete for events/tasks and create for projects/tags, but these are acceptable gaps given the domain.