todoist-tasks-core-openapi
Core Todoist REST API for listing, creating, updating, completing, reopening, and deleting tasks, plus listing, creating, updating, and deleting projects. The user supplies a Todoist personal token or OAuth token at connection time; no credential is included. Official documentation: https://developer.todoist.com/api/v1/
Connect this API to an AI agent Browse all specs
What you can do with todoist-tasks-core-openapi via MCP
Every endpoint below becomes a governed tool your AI agent (Claude, ChatGPT, or a customer-facing VX agent) can call — with scoped permissions, sandbox testing, and audit logs.
| Method | Path | Operation | Description |
|---|---|---|---|
| GET | /tasks |
listTasks | List tasks |
| POST | /tasks |
createTask | Create a task |
| GET | /tasks/{task_id} |
getTask | Get a task |
| POST | /tasks/{task_id} |
updateTask | Update a task |
| DELETE | /tasks/{task_id} |
deleteTask | Delete a task |
| POST | /tasks/{task_id}/close |
completeTask | Complete a task |
| POST | /tasks/{task_id}/reopen |
reopenTask | Reopen a completed task |
| GET | /projects |
listProjects | List projects |
| POST | /projects |
createProject | Create a project |
| GET | /projects/{project_id} |
getProject | Get a project |
| POST | /projects/{project_id} |
updateProject | Update a project |
| DELETE | /projects/{project_id} |
deleteProject | Delete a project |
Authentication
bearerAuth
Bearer token — sent as Authorization: Bearer <token>
Usage guide
Getting credentials
- Create or log in to an account at Todoist.
- Open Settings → Integrations.
- For personal use, copy your Todoist API token. For a multi-user integration, use the OAuth authorization flow described in the Todoist API documentation.
- When VX Agent asks for authentication, provide the token using Bearer authentication.
Keep the token private. Do not paste it into the Swagger file, marketplace description, prompts, or chat messages.
How to use this API
Use the Todoist API to organize personal and team work by reading, creating, updating, completing, reopening, and deleting tasks, as well as creating and managing projects.
A typical workflow is:
- Use
GET /projectsto find the correct project and obtain itsproject_id. - Use
GET /tasksto review existing tasks. You can filter by project, section, label, or a Todoist filter query such astodayoroverdue. - Use
POST /tasksto create a task with content, description, project, labels, priority, or a due date. - Use
POST /tasks/{task_id}to update a task when the user requests a change. - Use
POST /tasks/{task_id}/closeto complete a task andPOST /tasks/{task_id}/reopento reopen it. - Use
POST /projectsorPOST /projects/{project_id}to create or update project organization. - Use
DELETEoperations only when the user explicitly confirms permanent deletion.
Always inspect the current project and task list before making changes. Confirm the target project, task content, due date, priority, labels, and assignee before creating or updating work. Do not pass client-side tmp- placeholder IDs to the REST API; wait for the real server-assigned ID.
Safety and usage notes
Creating, updating, completing, reopening, or deleting tasks changes the user's productivity data. Ask for confirmation before making consequential changes, bulk updates, completing important work, or deleting tasks or projects.
Only access projects and tasks authorized by the connected user. Do not expose private task content, comments, project names, or personal information. Use narrow filters and pagination when reading large workspaces.
Do not delete tasks or projects unless the user explicitly requests it. Deleting a project can affect its tasks and may not be reversible. Do not expose the Todoist token or store it in the Swagger file.
Official documentation: Todoist API v1.
How to use this spec
- Create a free VX Agents account (sandbox tools included).
- Open the marketplace and connect “todoist-tasks-core-openapi” to an agent.
- Expose it as an MCP server for Claude/ChatGPT, or chat with it directly.