Schema | MCP Todo.txt Integration

MCP Todo.txt Integration

Describes the environment variables required to run the server.

Name	Required	Description	Default
`TODO_FILE_PATH`	No	The path to the Todo.txt file. If not set, the default path is `todo.txt` in the project root.	todo.txt

Features and capabilities supported by this server

Functions exposed to the LLM to take actions

Name	Description
add-taskB	Add a new task to the todo list. Description must be plain text. Priority must be a single uppercase letter (A-Z). Contexts must start with @, projects with +.
complete-taskB	Mark a task as completed by its 1-based ID.
delete-taskB	Delete a task by its 1-based ID.
list-tasksC	List all tasks, optionally filtered by priority, context, project, or metadata.
search-tasksB	Search for tasks containing a query string.
sort-tasksC	Sort tasks by priority, creation date, or completion date.
filter-tasksC	Filter tasks by specific criteria (priority, context, project).
add-metadataB	Add custom metadata (key-value pairs) to a task by ID.
remove-metadataC	Remove specific metadata keys from a task by ID.
batch-operationsB	Perform batch operations (update, delete, mark-complete) on tasks matching criteria.
update-taskC	Update a task's fields (description, priority, contexts, projects, metadata) by ID.

Interactive templates invoked by user choice

Name	Description
`suggest-context-tasks`
`suggest-project-tasks`

Contextual data attached and managed by the client

Name	Description
`tasks`

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/guifelix/mcp-server-todotxt'

If you have feedback or need assistance with the MCP directory API, please join our Discord server