Skip to main content
Glama
Obsidian Todos MCP Server

Obsidian Todos MCP Server

by mtuckerb

Obsidian Todos MCP Server

Model Context Protocol (MCP) server that provides AI assistants with direct access to Obsidian todos through the Local REST API.

Features

  • πŸ” List todos - Get all incomplete todos from your vault

  • βž• Add todos - Create new todos in today's daily note

  • ✏️ Update todos - Modify existing todos or mark them complete

  • πŸ“Š Get stats - View todo statistics by file

Related MCP server: Obsidian MCP Server

Prerequisites

  1. Obsidian with the following plugins installed and enabled:

    • Local REST API

    • Dataview

    • Todos REST API (this plugin)

  2. Node.js 18+ installed

Installation

From npm (coming soon)

npm install -g obsidian-todos-mcp-server

From source

cd mcp-server
npm install
npm run build

Configuration

Environment Variables

  • OBSIDIAN_API_URL - Base URL for the REST API (default: http://localhost:27124)

  • OBSIDIAN_API_KEY - API key if authentication is enabled

Claude Desktop Configuration

Add to your claude_desktop_config.json:

{
  "mcpServers": {
    "obsidian-todos": {
      "command": "npx",
      "args": ["-y", "obsidian-todos-mcp-server"],
      "env": {
        "OBSIDIAN_API_URL": "http://localhost:27124"
      }
    }
  }
}

Or use the direct binary name after npm link:

{
  "mcpServers": {
    "obsidian-todos": {
      "command": "obsidian-todos-mcp",
      "env": {
        "OBSIDIAN_API_URL": "http://localhost:27124"
      }
    }
  }
}

Or if running from source:

{
  "mcpServers": {
    "obsidian-todos": {
      "command": "node",
      "args": ["/path/to/obsidian-todos-api/mcp-server/dist/index.js"],
      "env": {
        "OBSIDIAN_API_URL": "http://localhost:27124"
      }
    }
  }
}

Available Tools

list_todos

Lists all incomplete todos from your Obsidian vault.

Example:

// No parameters needed
await use_mcp_tool({
  server_name: "obsidian-todos",
  tool_name: "list_todos",
  arguments: {}
});

add_todo

Adds a new todo to today's daily note.

Parameters:

  • text (string, required) - The todo text

Example:

await use_mcp_tool({
  server_name: "obsidian-todos",
  tool_name: "add_todo",
  arguments: {
    text: "Review pull requests"
  }
});

update_todo

Updates an existing todo (mark complete, change text, etc.).

Parameters:

  • file (string, required) - Path to file containing the todo

  • line (number, required) - Line number of the todo (0-indexed)

  • text (string, optional) - New text for the todo

  • completed (boolean, optional) - Mark as complete/incomplete

Example:

await use_mcp_tool({
  server_name: "obsidian-todos",
  tool_name: "update_todo",
  arguments: {
    file: "Daily/2025-10-31.md",
    line: 5,
    completed: true
  }
});

get_todo_stats

Get statistics about your todos.

Example:

await use_mcp_tool({
  server_name: "obsidian-todos",
  tool_name: "get_todo_stats",
  arguments: {}
});

Development

# Watch mode for development
npm run dev

# Build for production
npm run build

# Test the server
echo '{"jsonrpc":"2.0","id":1,"method":"tools/list"}' | node dist/index.js

Troubleshooting

Connection Issues

  1. Ensure Obsidian Local REST API is running

  2. Check the API URL is correct (default: http://localhost:27124)

  3. Verify the Todos REST API plugin is enabled in Obsidian

Authentication Errors

If you have authentication enabled in Local REST API:

  1. Set the OBSIDIAN_API_KEY environment variable

  2. Or update your Claude Desktop config with the API key

License

MIT

Available Tools

5 tools
add_todoA

Add a new todo to today's daily note in Obsidian

Inputs: text (required).

get_todo_statsC

Get statistics about todos (total, by file, etc.)

Inputs: no named parameters.

list_due_datesB

List all due dates from tables under # Due Dates headings in Obsidian

Inputs: start, end, query.

list_todosC

List all incomplete todos from Obsidian vault using Dataview

Inputs: status, completed, path, tag, +1 more.

update_todoC

Update an existing todo in Obsidian (mark complete, change text, etc.)

Inputs: file (required), line (required), text, completed.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    A3.5/5.0

    Scored across 5 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: add, update, list incomplete todos, list due dates, and get statistics. No overlap or ambiguity.

    Naming Consistency5/5

    All tools follow a consistent verb_noun pattern in snake_case (e.g., add_todo, list_todos, update_todo), making them predictable and easy to understand.

    Tool Count5/5

    With 5 tools, the server is well-scoped for a todo management domain. Each tool covers a core operation without excess or deficiency.

    Completeness4/5

    Covers create (add), read (list, stats, due dates), and update, but lacks a delete tool. This is a minor gap that agents can work around, but it's not fully complete.

    Maintenance

    ActivityInactive
    ResponsivenessOutdated data

    Related MCP Connectors

    Related MCP Servers