Obsidian Tasks MCP Server

Obsidian tasks MCP server

Local serverstdio

What is the Obsidian Tasks MCP server?

Connect Obsidian Tasks to Claude, Cursor or any other MCP client and it stops being a tab you switch to. Obsidian tasks MCP server. The obsidian tasks mcp server is what makes that connection.

What the server does

A Model Context Protocol (MCP) server for extracting and querying Obsidian Tasks from markdown files. Designed to work with Claude via the MCP protocol to enable AI-assisted task management.

  • Extract tasks from Obsidian markdown files with a format compatible with the Obsidian Tasks plugin
  • Identify completed and pending tasks
  • Access task metadata including:
  • Status (complete/incomplete)
  • Scheduled dates
  • Created dates

Available tools

The toolset is worth reading before you wire it up, because it tells you what the integration is really for:

  • list_all_tasks — Extracts all tasks from markdown files in a directory, recursively scanning through subfolders
  • query_tasks — Searches for tasks based on Obsidian Tasks query syntax. Applies multiple filters to find matching tasks
  • Installation — The Installation tool exposed by this server
  • Testing — See TESTING.md for detailed information about the test suite

Installation

Installation goes through your MCP client rather than a global install: point it at without on npm and it is fetched when the client starts. The copy-paste blocks for Claude Desktop, Claude Code and Cursor are further down this page.

Where it fits

This sits in the planning and project tracking group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. Obsidian Tasks's toolset — list_all_tasks, query_tasks, Installation and 1 more — is a fair guide to whether it matches your workflow. It is maintained by jfim; worth a glance at recent repository activity before you build anything load-bearing on it.

This entry was verified against Obsidian Tasks's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.

Worth knowing first

  • It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
  • Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.

Available tools

ToolWhat it does
list_all_tasksExtracts all tasks from markdown files in a directory, recursively scanning through subfolders.
query_tasksSearches for tasks based on Obsidian Tasks query syntax. Applies multiple filters to find matching tasks.
InstallationThe Installation tool exposed by this server.
TestingSee [TESTING.md](TESTING.md) for detailed information about the test suite.

How to install the Obsidian Tasks MCP server

If you installed from source:

```json
{
  "mcpServers": {
    "obsidian-tasks": {
      "command": "node",
      "args": [
        "/path/to/obsidian-tasks-mcp/dist/src/index.js",
        "/path/to/obsidian/vault"
      ]
    }
  }
}

Configuration as documented by the project. Restart the client after saving.

Example prompts to try

  • Use Obsidian Tasks to list all tasks.
  • Use Obsidian Tasks to query tasks.
  • Use Obsidian Tasks to Installation.

Frequently asked questions

The server supports both Obsidian Tasks emoji format (e.g., `🗓️`, `⏳`, `📅`) and Dataview format for task metadata.