
jfim/obsidian-tasks-mcp
Developer tools이 페이지는 AI로 자동 번역되었습니다. 기술적인 세부 사항은 원문을 확인하세요. 원문 보기
Obsidian tasks MCP server
개요
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) - Due dates - Scheduled dates - Start dates - Created dates - Tags - Priority - Recurrence rules This MCP server provides the following tools: Extracts all tasks from markdown files in a directory, recursively scanning through subfolders. - path (string, optional): The directory to scan for markdown files. If not specified, defaults to the first allowed directory. A JSON array of task objects, each containing: Searches for tasks based on Obsidian Tasks query syntax. Applies multiple filters to find matching tasks. - path (string, optional): The directory to scan for markdown files.
README
원문 README의 일부입니다. 원문 보기.
Obsidian Tasks MCP Server
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.
Features
- 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)
- Due dates
- Scheduled dates
- Start dates
- Created dates
- Tags
- Priority
- Recurrence rules
Tools
This MCP server provides the following tools:
list_all_tasks
Extracts all tasks from markdown files in a directory, recursively scanning through subfolders.
Input Parameters:
path(string, optional): The directory to scan for markdown files. If not specified, defaults to the first allowed directory.
Returns: A JSON array of task objects, each containing:
{
"id": "string", // Unique identifier (filepath:linenumber)
"description": "string", // Full text description of the task
"status": "complete" | "incomplete", // Task completion status
"filePath": "string", // Path to the file containing the task
"lineNumber": "number", // Line number in the file
"tags": ["string"], // Array of tags found in the task
"dueDate": "string", // Optional - YYYY-MM-DD format
"scheduledDate": "string", // Optional - YYYY-MM-DD format
"startDate": "string", // Optional - YYYY-MM-DD format
"createdDate": "string", // Optional - YYYY-MM-DD format
"priority": "string", // Optional - "high", "medium", or "low"
"recurrence": "string" // Optional - recurrence rule
}
query_tasks
Searches for tasks based on Obsidian Tasks query syntax. Applies multiple filters to find matching tasks.
Input Parameters:
path(string, optional): The directory to scan for markdown files. If not specified, defaults to the first allowed directory.query(string, required): The query string using Obsidian Tasks query syntax. Each line is treated as a filter.
Returns:
A JSON array of task objects that match the query, with the same structure as list_all_tasks.
Supported Query Syntax:
-
Status filters:
done- Show completed tasksnot done- Show incomplete tasks
-
Date filters (due):
- Note on semantics:
due todayis an exact match (only tasks due exactly today). Use range operators to include earlier/later dates. due today- Tasks due todaydue before today- Tasks due before today (exclusive)due after today- Tasks due after today (exclusive)due on or before today- Tasks due today or earlier (inclusive)due on or after today- Tasks due today or later (inclusive)due on YYYY-MM-DDordue YYYY-MM-DD- Tasks due on a specific date
- Note on semantics:
설치
npx @jfim/obsidian-tasks-mcp /path/to/obsidian/vault설정
{
"mcpServers": {
"obsidian-tasks": {
"command": "npx",
"args": [
"@jfim/obsidian-tasks-mcp",
"/path/to/obsidian/vault"
]
}
}
}