How abhiz123/todoist-mcp-server works
Todoist MCP Server exposes Todoist task operations as MCP tools for a client such as Claude. The principal workflow is a client tool request, server-side dispatch and validation, then a Todoist API action and a text response. Search-based update, completion, and deletion first retrieve tasks and match task names; retrieval also applies filters. These responsibilities are implemented in one source file, so the graph separates runtime roles without implying separate modules. The README documents the full tool set; source excerpts show the key calls, but omit some handler details.
Main entry points: index.ts MCP server
Components 8
MCP Runtime
- stdio transport
src/index.ts - MCP server
src/index.ts - Tool definitions
src/index.ts - Request dispatch
src/index.ts
Task Operations
- Task handlers
src/index.ts - Search and filtering
src/index.ts - Todoist API
Other components
- Claude / MCP client
Connections 8
- Claude / MCP client → stdio transport: sends MCP requests
README.md - stdio transport → MCP server: connects transport
src/index.ts - MCP server → Tool definitions: lists tools
src/index.ts - MCP server → Request dispatch: dispatches calls
src/index.ts - Request dispatch → Task handlers: routes tool calls
src/index.ts - Task handlers → Search and filtering: matches and filters
src/index.ts - Task handlers → Todoist API: creates and mutates tasks
src/index.ts - Search and filtering → Todoist API: retrieves tasks
src/index.ts