Skip to content

Todoist

Updated View as Markdown

Review active Todoist work and create a clearly scoped task after you approve its details.

Example workflows

Copy a prompt into your connected AI client after connecting this integration. Choose resources you can access and review the supported command before running it.

Plan the next work session

Read one page of my active Todoist tasks. Build a short planning list from returned task content, project IDs, priorities and due dates. Keep task IDs and URLs where available, distinguish unscheduled work, and ask before reading another cursor page. Do not complete, reschedule or reprioritize tasks.

Explore this command: todoist.tasks.list

Create a task with a clear outcome

Help me turn a follow-up into one Todoist task. Ask for the task content and destination project, and clarify any intended due date. Show the exact proposed content, project ID and supported fields before creating it. After my approval, create it once and return the task ID and URL when supplied.

Explore this command: todoist.tasks.create

What you can do (4)

What you can do

Available commands: 4 (3 read, 1 write). Enable only the commands your application needs.

Command Effect
List one page of Todoist projects — todoist.projects.list Read
List a page of active tasks — todoist.tasks.list Read
Create a Todoist task — todoist.tasks.create Write
Read one task — todoist.tasks.get Read

Connect and use

Connect and use

This connection uses your provider account.

Connect this integration, enter your provider credentials, choose commands and save. Complete provider authorization if prompted.

Get your provider credentials

Follow these steps for Todoist, then enter the issued values in the connection form below.

  1. Find your Todoist API token in Settings > Integrations > Developer and paste it into this connection. This personal token inherits your account access; keep it private and revoke it when no longer needed. Enable selected commands. Use projects.list for IDs and tasks.list with its returned cursor for further pages. This implementation uses the current /api/v1 API, not the retired REST v2 endpoint.

Official credential setup

Where to enter credentials

In the integration page, sign in, choose your workspace and open Connect. If a Credentials choice is shown, select Use my credentials. Fill the following connection fields and save. Provider credentials belong in this form, never in an MCP configuration or tool input.

Connection field Requirement
Todoist API token Required

Open API keys and create a Tooluse.net key for the enabled commands.

Set TOOLUSE_API_KEY in your client and use the shared MCP configuration.

Configure Claude Code, Codex or Cursor once

Permissions and results

If you have more than one workspace, check the selected workspace in the connection or API-key dialog before saving. Roles, enabled commands, expiry and revocation use Tooluse.net's existing permissions. Disabling a connection or revoking a key immediately prevents new calls.

Send one Claude tool_use block per request. Keep the same Idempotency-Key when retrying the same request; use a new key for a new call. The response includes the shared Tooluse.net receipt and Claude tool_result. Check both HTTP status and the returned tool result before treating a call as successful.

Your connection's daily allowance and key permissions also apply. Adding a connection does not make a provider request.

Calls return the shared execution receipt and a Claude tool_result. Provider output varies by operation; consult the provider documentation for its response fields. Unconfirmed calls should be checked before retrying.

Call from your client

Use the shared MCP configuration. Refresh your client's tool list after saving the connection or changing key permissions, then call the returned tool name with the example input below.

Configure Claude Code, Codex or Cursor once

Discover your enabled tools

List permitted tools in Claude format. Read every page using page and size (maximum 100) until all results have been received. Use the returned name, not a catalog capability identifier, in the tool_use block.

curl 'https://api.tooluse.net/v1/tools' \
  -H "Authorization: Bearer $TOOLUSE_API_KEY"

Find this command in the tool list permitted by your key. Replace svc_FROM_YOUR_TOOL_LIST with its returned name. Use a new Idempotency-Key for each new call and retain it when retrying that same call.

HTTP call

curl 'https://api.tooluse.net/v1/tool-calls' \
  -H "Authorization: Bearer $TOOLUSE_API_KEY" \
  -H 'Content-Type: application/json' \
  -H 'Idempotency-Key: replace-with-a-new-call-id' \
  --data '{
  "type": "tool_use",
  "id": "toolu_example",
  "name": "svc_FROM_YOUR_TOOL_LIST",
  "input": {}
}'

Send one Claude tool_use block per request. Keep the same Idempotency-Key when retrying the same request; use a new key for a new call. The response includes the shared Tooluse.net receipt and Claude tool_result. Check both HTTP status and the returned tool result before treating a call as successful.

Commands

List one page of Todoist projects — todoist.projects.list

List one page of Todoist projects

This is a read operation. Provider rate limits and data access rules still apply.

Connect and use

Parameters

Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.

Parameter Type Required in parent Description Constraints
query object Optional additionalProperties: false
query.limit integer Optional minimum: 1; maximum: 100
query.cursor string Optional minLength: 1

Full JSON Schema

Full JSON Schema

Example input

{}

At most 1 provider requests per invocation; timeout: 30 seconds.

List a page of active tasks — todoist.tasks.list

List a page of active tasks

This is a read operation. Provider rate limits and data access rules still apply.

Connect and use

Parameters

Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.

Parameter Type Required in parent Description Constraints
query object Optional additionalProperties: false
query.limit integer Optional minimum: 1; maximum: 100
query.cursor string Optional minLength: 1
query.project_id string Optional minLength: 1

Full JSON Schema

Full JSON Schema

Example input

{}

At most 1 provider requests per invocation; timeout: 30 seconds.

Create a Todoist task — todoist.tasks.create

Create a Todoist task

This operation can change provider data. Review the input before allowing an agent to call it.

Connect and use

Parameters

Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.

Parameter Type Required in parent Description Constraints
body object Required additionalProperties: false
body.content string Required minLength: 1
body.project_id string Optional
body.description string Optional
body.due_string string Optional
body.priority integer Optional minimum: 1; maximum: 4

Full JSON Schema

Full JSON Schema

Example input

{
  "body": {
    "content": "Example task"
  }
}

At most 1 provider requests per invocation; timeout: 30 seconds.

Read one task — todoist.tasks.get

Read one task

This is a read operation. Provider rate limits and data access rules still apply.

Connect and use

Parameters

Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.

Parameter Type Required in parent Description Constraints
path object Required additionalProperties: false
path.taskId string Required minLength: 1

Full JSON Schema

Full JSON Schema

Example input

{
  "path": {
    "taskId": "example"
  }
}

At most 1 provider requests per invocation; timeout: 30 seconds.

Errors

Check the key's expiry, revocation, workspace and allowed operations.

Reuse the same idempotency key only for the same request.

The connection or provider limit has been reached. Check the receipt before retrying.

Test the connection

Open the integration's commands below to inspect parameters and examples. Start with a read command for an account or resource you can access. Refresh your client's tool list, use the returned tool name, and check the execution result and usage. Provider charges and permissions still apply. Never test a write against production data without reviewing it.

Official provider documentation

Type to search…

↑↓ navigate↵ selectEsc close