Obsidian Tasks MCP Server

Created By
jfima year ago
Obsidian tasks MCP server
Overview

What is Obsidian Tasks MCP?

Obsidian Tasks MCP is a Model Context Protocol (MCP) server designed for extracting and querying tasks from Obsidian markdown files, enabling AI-assisted task management through integration with Claude.

How to use Obsidian Tasks MCP?

To use the server, install it via npm or clone the repository. Run the server with the path to your Obsidian vault, and it will extract tasks from markdown files.

Key features of Obsidian Tasks MCP?

  • Extracts tasks from markdown files compatible with the Obsidian Tasks plugin.
  • Identifies completed and pending tasks along with their metadata.
  • Provides tools for listing all tasks and querying tasks based on various filters.

Use cases of Obsidian Tasks MCP?

  1. Managing personal tasks and to-do lists in Obsidian.
  2. Integrating with AI tools for enhanced task management.
  3. Automating task extraction for project management.

FAQ from Obsidian Tasks MCP?

  • Can I use this with any markdown file?

Yes, as long as the markdown file follows the Obsidian Tasks format.

  • Is there a way to filter tasks?

Yes, you can filter tasks by status, due dates, tags, and more using the query syntax.

  • Is it necessary to install it globally?

No, you can use it directly with npx without installing it globally.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
jfim
Star
0
Language
TypeScript
License
-

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

2 days ago