Skip to main content

Manage your tasks without leaving Cursor

Cursor opens a folder and edits the files in it. Open your Obsidian vault and it can add, reschedule, and complete your tasks, which are plain markdown lines. Two setups get you there: register the taskforge MCP server for typed tools, or drop in a one-line rule pointing at your vault's contract file so Cursor writes tasks in your format from the first keystroke.

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.

Two ways to wire it up

The rules file is the fastest path and needs nothing installed. The MCP server adds typed tools if you want the agent to call add and complete rather than edit lines by hand. Pick one, or use both.

  1. Generate the vault contract

    Open your vault in TaskForge 3.0 or later, then Settings, AI & Agents, and keep "Generate agent files" on. TaskForge writes a taskforge/ folder describing your task format, which both setups below rely on.

  2. Open the vault as a folder in Cursor

    File, Open Folder, and choose your vault. Cursor now sees every note, including the taskforge/ contract, in its workspace.

  3. Point a rule at the contract

    Cursor does not yet auto-discover in-vault guides, so tell it where yours is. Add a project rule that references taskforge/agents.md, and Cursor reads it before writing any task.

    # .cursor/rules/taskforge.md
    When adding or editing tasks, first read taskforge/agents.md
    in this vault and follow its exact syntax and date format.
    One file, one line of intent. Cursor now matches a renamed field or a TaskNotes folder instead of guessing.
  4. Or add the MCP server for typed tools

    Prefer the agent to call tools? Add taskforge to Cursor's MCP config. npx fetches it on first run, and Cursor gets add_task, query_tasks, complete_task, and the rest.

    {
      "mcpServers": {
        "taskforge": {
          "command": "npx",
          "args": ["-y", "taskforge-md", "mcp", "--stdio"],
          "env": {
            "TASKFORGE_VAULT": "/path/to/your/vault"
          }
        }
      }
    }
    Save this as .cursor/mcp.json in the project, or add it in Cursor's MCP settings.

How Cursor gets your format right

Whichever setup you pick, the taskforge/ folder is the source of truth. The rules file sends Cursor to read agents.md; the MCP server exposes the same data as resources. Either way, Cursor writes a line your other tools can read, in your dialect, on the first try.

taskforge/agents.md Your task syntax in plain English. This is the file your .cursor rule points at.
taskforge/schema.json The machine-readable version, exposed to the MCP server as taskforge://schema.
taskforge/lists.json Your saved lists and where new tasks land, so "add this to my Work list" files it correctly.

Prompts that work

Ask Cursor in its chat panel with the vault open. It reads the contract, edits the markdown, and the change is a diff you can review before you accept it.

You ask Cursor

“Add a task for the client review packet, due Thursday, high priority.”

What lands in the file

- [ ] client review packet ⏫ 📅 2026-07-09

Cursor reads taskforge/agents.md first, so the priority marker and date format match this vault, not a generic guess.

You ask Cursor

“Read meeting-notes.md and add every action item to tasks/this-week.md, each due Friday.”

What lands in the file

- [ ] send the signed contract to legal 📅 2026-07-10

- [ ] book the venue deposit 📅 2026-07-10

The lines land in your vault. TaskForge shows them the next time it reads the vault, and your phone follows on the next sync.

Nothing leaves your machine

Cursor edits the local files in the folder you opened, and the taskforge MCP server, if you use it, runs locally too. No TaskForge account, no cloud. Your existing sync, iCloud, Dropbox, or Obsidian Sync, moves the edits to your other devices.

Questions people ask

Do I need the MCP server, or is the rules file enough?

The rules file is enough for most people. It points Cursor at taskforge/agents.md so it writes tasks in your format by editing files directly. Add the MCP server only if you want Cursor to call typed tools like add_task and complete_task instead.

Why does Cursor need a rule when Claude Code does not?

Cursor does not yet auto-discover in-vault guides, so it needs one line telling it where taskforge/agents.md is. It is a copy-paste you do once per vault. After that, Cursor reads the contract on its own.

Will the tasks show up in the TaskForge app?

Yes. Cursor edits the same markdown files TaskForge reads. The app picks up the change on that machine right away, and it reaches your phone once your vault sync runs.

Can I use both the rule and the MCP server?

Yes. The rule keeps free-form edits in your format, and the MCP server gives the agent typed tools for the actions it would rather call. They read the same contract, so they never disagree about your dialect.

Does this work with TaskNotes-style tasks?

Yes. If your vault uses TaskNotes, the contract describes those YAML fields and folders, so Cursor writes a valid TaskNotes task, not a plain checkbox line.

Related setups

Cursor is one editor among many. The AI overview covers the whole picture, and the MCP and CLI pages go deep on each surface.

Keep tasks in the editor you already live in.

Plain markdown in your own vault, edited by Cursor. TaskForge is free to download on iPhone, iPad, Mac, and Android.