Overview
ActionDrivenNote documentation
Learn the action-centered workflow, then connect compatible AI clients through the remote ActionDrivenNote MCP server.
ActionDrivenNote combines action planning, a full note inside every action, selective long-term knowledge, and optional MCP access for compatible AI clients. The documentation explains exact behavior; the blog explores the thinking and workflows behind the product.
Start here
Basics
Start with your first action
Learn the core Plan → Think → Keep workflow in a few minutes.
MCP
Connect a compatible AI client
Understand the endpoint, authorization flow, capabilities, and connection requirements.
MCP
Review what an AI client can access
See how OAuth authorization and read or write scopes govern every MCP connection.
The core model
Four objects carry most of the workflow:
- Action: something you want to move forward, with status, timing, hierarchy, and a document.
- Action document: the writing space for research, drafts, decisions, files, and newly discovered actions.
- Tag: a topic that connects selected actions to long-term knowledge. Tags can be nested.
- Action relationship: parent and child actions that break a larger outcome into smaller moves.
Completion changes the planning state of an action. It does not erase its document. Adding tags makes useful completed work easier to browse as knowledge.
MCP documentation
The remote MCP server gives compatible clients permissioned access to actions, documents, tags, and assets. Start with the MCP overview, then review security and permissions before approving write access.