What task formats does Obsidian Tasks MCP Server support?
The server supports both Obsidian Tasks emoji format (e.g., `🗓️`, `⏳`, `📅`) and Dataview format for task metadata.
@jfim
Basic information
Obsidian tasks MCP server
Add this server to your MCP-compatible client using the configuration below.
{
"mcpServers": {
"obsidian-tasks-mcp": {
"command": "npx",
"args": [
"@jfim/obsidian-tasks-mcp",
"/path/to/obsidian/vault"
]
}
}
}Tool list not available yet
This listing does not currently have a tool list to display. This does not mean the server has no tools; check its documentation for supported capabilities.
Fetch the live tool list by running this server in a temporary sandbox using the button above.
A Model Context Protocol (MCP) server that extracts and queries tasks from Obsidian markdown files using the Obsidian Tasks plugin format. Designed to enable AI-assisted task management with Claude via the MCP protocol.
Install globally via npm (npm install -g @jfim/obsidian-tasks-mcp) or run directly with npx. Specify the path to your Obsidian vault as a command-line argument when starting the server. Add the server configuration to your MCP-supporting client (e.g., Claude Desktop) using the JSON configuration shown in the README.
list_all_tasks and query_tasks.query_tasks tool with rich filter syntax (status, dates, tags, path, description, priority).The server supports both Obsidian Tasks emoji format (e.g., `🗓️`, `⏳`, `📅`) and Dataview format for task metadata.
Use `npx @jfim/obsidian-tasks-mcp /path/to/obsidian/vault`. No installation required.
It uses Obsidian Tasks query syntax. Filters include `done`/`not done`, date operators (e.g., `due today`, `due before YYYY-MM-DD`), tag filters (`tag includes #tag`), path filters, description filters, and priority filters.
Yes. Build the Docker image from the repository and run with a bind mount to your vault. Example configuration for Claude Desktop is included.
Yes. Run `npm test` to execute the test suite. See `TESTING.md` for more details.

Orcha is a unified context layer for AI tools and agents. It stores and indexes and exposes organizational, team, or individual knowledge. Files, structured databases, and connected sources live in one workspace, and age

One permissioned folder your team and your AI agents both log into.
Groundwork: company memory for your AI tools. Docs public. Source closed. Public proof needs no account.

Personal context for every AI: search, read, and write back to your private Markdown library of articles, threads, PDFs, notes, and captured ChatGPT/Claude/Gemini/Grok conversations. Remote server, OAuth 2.1 paste-and-au

The official Semantic-UI-React integration
Comments