praisonai-mcp host exposes four MCP tools that read and write the same todo store as the agent runtime (todo_add / todo_list / todo_update) — a todo added in Claude Desktop is visible to the runtime on the same machine, and vice versa.
praisonai-mcp serve --transport stdio, point Claude Desktop at it, and the assistant can list, add, complete, and delete the same todos.
Quick Start
1
Serve the host
2
Add a todo from an agent run
3
Read it back from your client
In Claude Desktop:
List my todos.The assistant calls
praisonai.todo.list and sees the todo the runtime wrote.Tools
Four tools share the runtime’s store and record schema (id int, task, priority, category, status).
The four tools were rebound to the runtime store in PraisonAI PR #4962. Before that fix they wrote to
~/.praison/todo.json in an incompatible schema (id as a UUID string, field name content) and were completely invisible to the runtime. If your workflow depended on the old path, migrate any records into ~/.praisonai/todos.json (or your workspace’s todos.json).Record Shape
The store is a JSON array — each todo carries an integerid and a task field.
Store Location
The MCP tools resolve the same file path aspraisonaiagents.tools.todo_tools.TodoTools._get_todo_file().
Never
~/.praison/todo.json — that was the old wrong path and is no longer read or written by any surface.
End-to-End Flow
Best Practices
Workspace switches the visible list
Workspace switches the visible list
A todo added inside
~/code/api-service/ writes to ~/code/api-service/todos.json. Switching directories switches the visible list — useful for keeping unrelated todos apart.Ids are integers under the hood
Ids are integers under the hood
The public MCP surface accepts strings, but the underlying id is an integer.
str(id) is safe; parse ids back as int.Delete is safe to retry
Delete is safe to retry
praisonai.todo.delete returns "Todo not found: <id>" when nothing matched, so a client can repeat a delete without failing hard.Migrate off the old path
Migrate off the old path
Any tooling that reads
~/.praison/todo.json is looking at the pre-#4962 layout, which is no longer written. Migrate to ~/.praisonai/todos.json or the workspace todos.json.Related
Todo CLI
Manage todos from the shell.
MCP Memory Tools
Four memory tools this host also exposes.
praisonai-mcp Package
The heavy MCP host that registers these tools.
Server: PraisonAI MCP
Deploying the full MCP host.