Featured

Deploy OpenClaw in 60 seconds — 20% off logoDeploy OpenClaw in 60 seconds — 20% off

Launch OpenClaw on Hostinger in about 60 seconds and keep your agent live 24/7. Our referral link gives you 20% off, no coupon code needed.

Launch on Hostinger
Run your Hermes agent on Hostinger, fully managed logoRun your Hermes agent on Hostinger, fully managed

Launch Hermes on Hostinger in one click, fully managed, no VPS knowledge needed. Use code ZACAARON10 for 10% off.

Launch on Hostinger
Crawl and scrape any site into clean data, 10% off logoCrawl and scrape any site into clean data, 10% off

Firecrawl crawls and scrapes any site into clean markdown for your agent. Get 1,000 free credits, and new users get 10% off their first purchase.

Try Firecrawl free
Your own AI agent, running 24/7 with QwikClaw logoYour own AI agent, running 24/7 with QwikClaw

QwikClaw sets up and runs an always-on OpenClaw agent for you. One click, no config files, no server setup.

Deploy now
One API to scrape, enrich, and extract the internet. logoOne API to scrape, enrich, and extract the internet.

Context.dev gives your agents a single API to scrape, enrich, and extract live web data — no proxies, no parsers, no maintenance.

Start building free
SetupClaw: done-for-you OpenClaw for founders & exec teams logoSetupClaw: done-for-you OpenClaw for founders & exec teams

White-glove OpenClaw for founders and exec teams (4–50+ employees): we install, harden, integrate your tools, and maintain it — secured from day one.

Get it set up for you
SEO data APIs for your agent, $1 free credit logoSEO data APIs for your agent, $1 free credit

DataForSEO gives your agent live access to SERP results, keyword data, backlinks, and on-page SEO data through one API. New accounts get a $1 credit, good for up to 20,000 keyword or backlink lookups.

Try DataForSEO free
Reach 47,000+ AI builders

A flat monthly placement in front of developers actively installing AI tools. No lock-in, cancel anytime.

Advertise here

Works with

Claude CodeClaude DesktopCursorVS CodeClineCodex CLIOpenClaw+ any MCP client

Install to Claude Code

This server doesn't publish a one-line install command. Follow the setup in the source repository.

Summary

Enables AI assistants to manage Obsidian tasks with full CRUD operations, querying, and date-based filtering via MCP.

README.md

Obsidian Tasks MCP Server

An Obsidian plugin that exposes task management functionality via MCP (Model Context Protocol), enabling AI assistants like Claude to interact with your tasks directly.

Features

  • Full CRUD operations: Add, update, remove, and toggle tasks programmatically
  • Query tasks using Obsidian Tasks syntax with powerful filtering
  • Smart defaults: Tasks are added to today's Daily Note by default
  • Tasks plugin integration: When available, leverages Tasks plugin API for proper recurrence handling
  • Real-time vault sync: Uses Obsidian's Vault API for reliable file operations
  • Rich metadata support: Dates, priority, tags, recurrence rules

Installation

From GitHub Release

  1. Go to Releases
  2. Download main.js and manifest.json from the latest release
  3. In your vault, create folder: .obsidian/plugins/tasks-mcp/
  4. Copy the downloaded files into this folder
  5. Open Obsidian Settings > Community plugins
  6. Turn off "Restricted mode" if enabled
  7. Find "Tasks MCP Server" and enable it

Build from Source

git clone https://github.com/dss99911/obsidian-tasks-mcp.git
cd obsidian-tasks-mcp
npm install
npm run build

Copy main.js and manifest.json to your vault's .obsidian/plugins/obsidian-tasks-mcp/ folder.

Local Development

Setup

  1. Clone the repository:
   git clone https://github.com/dss99911/obsidian-tasks-mcp.git
  1. Install dependencies:
   cd obsidian-tasks-mcp
   npm install
  1. Identify your Obsidian vault's plugin folder:
   # Example: <YOUR_VAULT>/.obsidian/plugins/obsidian-tasks-mcp/

Development Workflow

Option 1: Symlink (Recommended)

Create a symlink from your vault's plugin folder to the source:

# Remove existing plugin folder if exists
rm -rf <YOUR_VAULT>/.obsidian/plugins/obsidian-tasks-mcp

# Create symlink
ln -s /path/to/obsidian-tasks-mcp <YOUR_VAULT>/.obsidian/plugins/obsidian-tasks-mcp

Now builds will automatically be available to Obsidian.

Option 2: Manual Copy

After each build, copy files to the plugin folder:

npm run build
cp main.js manifest.json <YOUR_VAULT>/.obsidian/plugins/obsidian-tasks-mcp/

Build Commands

# Production build
npm run build

# Development build with watch mode
npm run dev

Reload Plugin

After building, reload the plugin in Obsidian:

  1. Settings → Community plugins
  2. Toggle off "Tasks MCP Server"
  3. Toggle on "Tasks MCP Server"

Or restart Obsidian.

Configuration

MCP Client Setup

Add to your Claude Code MCP configuration (~/.claude/mcp.json or project .mcp.json):

{
  "mcpServers": {
    "obsidian-tasks": {
      "type": "http",
      "url": "http://localhost:3789/mcp"
    }
  }
}

Plugin Settings

In Obsidian Settings > Tasks MCP Server:

  • Server Port: Default 3789, configurable
  • Auto-start: Server starts automatically when Obsidian launches (default: on)

Tools

add_task

Add a new task to a file. If no filePath is provided, adds to today's Daily Note.

Parameters:

  • description (required): Task description
  • filePath: Target file path (defaults to Daily Note)
  • dueDate: Due date in YYYY-MM-DD format
  • scheduledDate: Scheduled date in YYYY-MM-DD format
  • startDate: Start date in YYYY-MM-DD format
  • priority: One of highest, high, medium, low, lowest
  • tags: Array of tags (with or without # prefix)
  • recurrence: Recurrence rule (e.g., "every day", "every week")

update_task

Update an existing task. Provide either taskId (from query results) or both filePath and lineNumber.

Parameters:

  • taskId: Task ID in format "filePath:lineNumber"
  • filePath + lineNumber: Alternative to taskId
  • description: New task description
  • status: One of incomplete, complete, cancelled, in_progress
  • dueDate: Due date (empty string to remove)
  • scheduledDate: Scheduled date (empty string to remove)
  • startDate: Start date (empty string to remove)
  • priority: Priority level or none to remove
  • tags: Array of tags (replaces existing)
  • recurrence: Recurrence rule (empty string to remove)

remove_task

Remove a task from a file.

Parameters:

  • taskId: Task ID in format "filePath:lineNumber"
  • filePath + lineNumber: Alternative to taskId

toggle_task

Toggle a task's completion status. When Tasks plugin is available, properly handles:

  • Completion dates
  • Recurring tasks (creates next occurrence)
  • Custom status symbols

Parameters:

  • taskId: Task ID in format "filePath:lineNumber"
  • filePath + lineNumber: Alternative to taskId

query_tasks

Search tasks using Obsidian Tasks query syntax. Each line is a filter with AND logic.

Supported filters:

| Category | Filters | |----------|---------| | Status | done, not done, cancelled, in progress | | Due date | due today, due before today, due after today, overdue, due YYYY-MM-DD, due before YYYY-MM-DD, due after YYYY-MM-DD, has due date, no due date | | Scheduled | scheduled today, scheduled before today, has scheduled date, no scheduled date | | Start date | starts today, starts before today, has start date, no start date | | Tags | has tags, no tags, tag includes #tag, tag does not include #tag | | Path | path includes <string>, path does not include <string> | | Description | description includes <string>, description does not include <string> | | Priority | priority is highest/high/medium/low/lowest/none | | Recurrence | is recurring, is not recurring | | Boolean | <filter1> AND <filter2>, <filter1> OR <filter2>, NOT <filter> |

Example: `` not done due before 2025-05-01 tag includes #work priority is high ``

list_tasks

Lists all tasks from a specific file or all markdown files with metadata including:

  • Status, description, file path, line number
  • Due date, scheduled date, start date, created date
  • Tags, priority, recurrence rules

get_tasks_by_date

Gets tasks for a specific due date with optional overdue task inclusion.

Parameters:

  • date (required): Due date in YYYY-MM-DD format
  • includeOverdue: Include overdue tasks (default: false)

API Endpoints

  • POST /mcp - MCP JSON-RPC endpoint
  • GET /sse - Server-Sent Events connection
  • GET /health - Health check (returns Tasks plugin availability)

Requirements

  • Obsidian v1.0.0+
  • Tasks plugin (optional, recommended for recurrence handling)

The plugin works without Tasks plugin installed. When Tasks plugin is available, toggle_task uses its API for proper recurrence handling.

Commands

  • Toggle MCP Server: Start/stop the server manually
  • Show MCP Server Status: Display current server status

Task Format

Recognizes standard Obsidian Tasks format:

  • Checkbox: - [ ] (incomplete), - [x] (complete), - [-] (cancelled), - [/] (in progress)
  • Due date: 📅 YYYY-MM-DD or 🗓️ YYYY-MM-DD
  • Scheduled date: ⏳ YYYY-MM-DD
  • Start date: 🛫 YYYY-MM-DD
  • Created date: ➕ YYYY-MM-DD
  • Priority: ⏫⏫ (highest), (high), 🔼 (medium), 🔽 (low), (lowest)
  • Recurrence: 🔁 every day/week/month
  • Tags: #tag1 #tag2

Example: ```

  • [ ] Complete project report 📅 2025-05-01 ⏳ 2025-04-25 #work ⏫

## Security Note

This plugin runs an HTTP server on localhost. Only local applications can connect to it. If you need remote access, consider using a secure tunnel.

## Documentation

- [Blog: Manage Obsidian Tasks with AI - Tasks MCP Plugin Guide](https://dss99911.github.io/tools/obsidian/2026/01/06/Obsidian-Tasks-MCP-Plugin.html) - Detailed guide with use cases and examples

## License

MIT License

See related servers & alternatives →

Related MCP servers

Browse all →

Related guides

Hand-picked reading to help you choose and use Files & Docs servers.