Your TaskForge tasks are plain markdown lines in your Obsidian vault, so Claude can already add, edit, and reschedule them with direct folder access today. TaskForge 3.0 adds a dedicated MCP server so Claude Desktop can add a task, find what is overdue, reschedule it, or mark it done through typed tools instead of free-form edits. Either way, it touches the same files the app reads, on your machine, with no account and no cloud.
Coming in TaskForge 3.0
The TaskForge CLI and MCP server ship with the TaskForge 3.0 release. Everything on this page describes how they will work at launch. The TaskForge app is available today.
The quickest path is the MCP server, which Claude Desktop drives through a small set of tools. If you already give Claude direct access to a folder, it can edit the task files there instead. Both read the same vault.
Open your vault in TaskForge 3.0 or later, go to Settings, then AI & Agents, and leave "Generate agent files" on. TaskForge writes a taskforge/ folder describing your exact task format, so Claude gets your dialect right instead of guessing.
Open Claude Desktop's config file and add the taskforge server. npx fetches it the first time it runs, so there is nothing to install first. Set TASKFORGE_VAULT to the folder your notes live in.
Get Free - iOS & Mac 
Get Free - Android {
"mcpServers": {
"taskforge": {
"command": "npx",
"args": ["-y", "taskforge-md", "mcp", "--stdio"],
"env": {
"TASKFORGE_VAULT": "/path/to/your/vault"
}
}
}
} After a restart, Claude Desktop shows the taskforge tools in its tool list: add_task, query_tasks, get_task, update_task, complete_task, delete_task. If it cannot find the vault, the server still starts and returns a plain message telling Claude to set TASKFORGE_VAULT.
Now you talk to Claude the way you would a person. "What is overdue?" "Add a task to call the dentist on Friday." "Mark the invoice done." Claude picks the right tool, and the change lands in your markdown the moment it runs.
TaskForge writes three files into a visible taskforge/ folder in your vault. The MCP server reads them (and exposes them as resources) so Claude follows the way your vault actually writes tasks, whether that means Dataview [key:: value] fields, a renamed due date, or TaskNotes files. Nothing leaves your device to produce them.
| taskforge/agents.md | Your vault's task syntax in plain English: checkbox dialect, status symbols, renamed fields, date format, folder rules. |
| taskforge/schema.json | The same facts in machine-readable form, exposed to Claude as the taskforge://schema resource. |
| taskforge/lists.json | Your saved lists and where a new task should land, so "add this to Work" files it correctly. |
Every call re-reads the vault from disk, so Claude always acts on the current files. If you edit a task in Obsidian mid-conversation, the next tool call sees it.
You ask Claude
“What is overdue in my vault? Push anything that can wait to Monday and raise the priority on what cannot.”
What lands in your vault
- [ ] renew the domain 📅 2026-07-13
- [ ] pay the contractor invoice ⏫ 📅 2026-07-09
Claude reads your tasks with query_tasks, then rewrites the dates and priority in place with update_task. The reschedule shows up in TaskForge and in Obsidian at the same time.
You ask Claude
“Add a task to prep the Monday review, high priority, due this Friday.”
What lands in your vault
- [ ] prep the Monday review ⏫ 📅 2026-07-10
add_task writes the line into your vault's default target, formatted the way your vault writes tasks. It is in TaskForge the next time the app reads the vault.
The taskforge MCP server reads and writes the markdown files in the vault you point it at, and nothing else. No account, no API key, no TaskForge server in the loop. Whatever already syncs your vault, iCloud, Dropbox, or Obsidian Sync, carries Claude's edits to your other devices.
Yes. Connect Claude Desktop to your Obsidian vault through the taskforge MCP server and Claude can add, find, reschedule, and complete tasks through six tools. The tasks are plain markdown lines, so TaskForge and Obsidian both show Claude's edits.
Either works. The MCP server gives Claude Desktop typed tools and structured errors it can self-correct against. If you instead run Claude with direct access to your vault folder, it can edit the markdown task lines the same way you would in Obsidian.
Only to Claude, which you already chose to run. The taskforge server itself is local: it touches the markdown files in your vault and makes no network calls. There is no TaskForge account or cloud.
Claude Desktop is the usual choice, since that is where the MCP client lives. Claude Code works too, and if you use it there is a dedicated walkthrough for the terminal workflow.
delete_task makes the model echo the task's exact current title back before anything is removed, which catches a stale or hallucinated id. And because your vault is a plain folder, git, iCloud, or Obsidian Sync already version it, so any bad edit is one revert away.
TaskForge works with any file-capable agent, not only Claude. The AI overview covers the whole picture; the MCP and CLI pages go deep on each surface.
Plain markdown in your own vault. TaskForge is free to download on iPhone, iPad, Mac, and Android.