The agent creates, updates, or deletes tasks and development documentation within the ainote system, leveraging backend state management and automatic conflict resolution for reliable multi-device synchronization.
The agent connects to the ainote MCP server using the provided HTTP or stdio configuration. It first checks existing tasks or dev docs using read-only tools like list_tasks or list_dev_docs to understand the current state. Before performing destructive actions like delete_task or update_dev_doc, the agent verifies the target item's ID and content. It then executes the necessary create, update, or delete operations. The backend handles complex logic such as state tracking and sync conflicts, allowing the agent to focus on the user's intent. The agent should ensure that destructive calls are intentional, as indicated by the tool annotations.
- Category: Productivity and planning
- Effect: Changes data in your accounts
- MCP servers: ainote MCP (https://koskamo.com/explore/ainote-mcp)
- Source: ainote — Agent-native notes, tasks, memory & sync · ainote 개발자 문서 (https://docs.ainote.dev/)
- Source quote: "Tasks (5) list_tasks 🔒 ♻️ create_task update_task ♻️ delete_task ⚠️ ♻️"
- Playbook page: https://koskamo.com/explore/use-cases/manage-tasks-and-dev-docs-via-ainote-mcp
Prompt: Please list all current tasks in ainote. Then, create a new task titled 'Review PR #123' with the description 'Check for security vulnerabilities'. Finally, delete the task titled 'Old Bug Fix' if it exists.