@doist/todoist-mcp 0.0.1 → 10.0.0

package/LICENSE

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2025 Doist
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

package/README.md

@@ -1,45 +1,221 @@
-# @doist/todoist-mcp
+# Todoist MCP Server
 
-## ⚠️ IMPORTANT NOTICE ⚠️
+> **Note:** This package was previously named `@doist/todoist-ai`. The old name continues to work as a thin shim that re-exports from `@doist/todoist-mcp`, but new installs should use `@doist/todoist-mcp` directly.
 
-**This package is created solely for the purpose of setting up OIDC (OpenID Connect) trusted publishing with npm.**
+Library for connecting AI agents to Todoist. Includes tools that can be integrated into LLMs,
+enabling them to access and modify a Todoist account on the user's behalf.
 
-This is **NOT** a functional package and contains **NO** code or functionality beyond the OIDC setup configuration.
+These tools can be used both through an MCP server, or imported directly in other projects to
+integrate them to your own AI conversational interfaces.
 
-## Purpose
+## Using tools
 
-This package exists to:
-1. Configure OIDC trusted publishing for the package name `@doist/todoist-mcp`
-2. Enable secure, token-less publishing from CI/CD workflows
-3. Establish provenance for packages published under this name
+### 1. Add this repository as a dependency
 
-## What is OIDC Trusted Publishing?
+```sh
+npm install @doist/todoist-mcp
+```
 
-OIDC trusted publishing allows package maintainers to publish packages directly from their CI/CD workflows without needing to manage npm access tokens. Instead, it uses OpenID Connect to establish trust between the CI/CD provider (like GitHub Actions) and npm.
+### 2. Import the tools and plug them to an AI
 
-## Setup Instructions
+Here's an example using [Vercel's AI SDK](https://ai-sdk.dev/docs/ai-sdk-core/generating-text#streamtext).
 
-To properly configure OIDC trusted publishing for this package:
+```js
+import { findTasksByDate, addTasks } from '@doist/todoist-mcp'
+import { TodoistApi } from '@doist/todoist-sdk'
+import { streamText } from 'ai'
 
-1. Go to [npmjs.com](https://www.npmjs.com/) and navigate to your package settings
-2. Configure the trusted publisher (e.g., GitHub Actions)
-3. Specify the repository and workflow that should be allowed to publish
-4. Use the configured workflow to publish your actual package
+// Create Todoist API client
+const client = new TodoistApi(process.env.TODOIST_API_KEY)
 
-## DO NOT USE THIS PACKAGE
+// Helper to wrap tools with the client
+function wrapTool(tool, todoistClient) {
+    return {
+        ...tool,
+        execute(args) {
+            return tool.execute(args, todoistClient)
+        },
+    }
+}
 
-This package is a placeholder for OIDC configuration only. It:
-- Contains no executable code
-- Provides no functionality
-- Should not be installed as a dependency
-- Exists only for administrative purposes
+const result = streamText({
+    model: yourModel,
+    system: 'You are a helpful Todoist assistant',
+    tools: {
+        findTasksByDate: wrapTool(findTasksByDate, client),
+        addTasks: wrapTool(addTasks, client),
+    },
+})
+```
 
-## More Information
+## Using as an MCP server
 
-For more details about npm's trusted publishing feature, see:
-- [npm Trusted Publishing Documentation](https://docs.npmjs.com/generating-provenance-statements)
-- [GitHub Actions OIDC Documentation](https://docs.github.com/en/actions/deployment/security-hardening-your-deployments/about-security-hardening-with-openid-connect)
+### Quick Start
 
----
+You can run the MCP server directly with npx:
 
-**Maintained for OIDC setup purposes only**
+```bash
+npx @doist/todoist-mcp
+```
+
+### Setup Guide
+
+The Todoist MCP server is available as a streamable HTTP service for easy integration with various AI clients:
+
+**Primary URL (Streamable HTTP):** `https://ai.todoist.net/mcp`
+
+#### Claude Desktop
+
+1. Open Settings → Connectors → Add custom connector
+2. Enter `https://ai.todoist.net/mcp` and complete OAuth authentication
+
+#### Cursor
+
+Create a configuration file:
+
+- **Global:** `~/.cursor/mcp.json`
+- **Project-specific:** `.cursor/mcp.json`
+
+```json
+{
+    "mcpServers": {
+        "todoist": {
+            "command": "npx",
+            "args": ["-y", "mcp-remote", "https://ai.todoist.net/mcp"]
+        }
+    }
+}
+```
+
+Then enable the server in Cursor settings if prompted.
+
+#### Claude Code (CLI)
+
+The fastest setup is the official Todoist plugin, which wires up the MCP server for you:
+
+```bash
+/plugin marketplace add doist/todoist-mcp
+/plugin install todoist@doist
+```
+
+OAuth runs in your browser the first time you use a Todoist tool. See [Anthropic's plugin docs](https://code.claude.com/docs/en/plugins-reference) for more.
+
+If you'd rather configure the MCP server manually, run:
+
+```bash
+claude mcp add --transport http todoist https://ai.todoist.net/mcp
+```
+
+Then launch `claude`, execute `/mcp`, and select the `todoist` MCP server to authenticate.
+
+#### Visual Studio Code
+
+1. Open Command Palette → MCP: Add Server
+2. Select HTTP transport and use:
+
+```json
+{
+    "servers": {
+        "todoist": {
+            "type": "http",
+            "url": "https://ai.todoist.net/mcp"
+        }
+    }
+}
+```
+
+#### Other MCP Clients
+
+```bash
+npx -y mcp-remote https://ai.todoist.net/mcp
+```
+
+For more details on setting up and using the MCP server, including creating custom servers, see [docs/mcp-server.md](docs/mcp-server.md).
+
+## Features
+
+A key feature of this project is that tools can be reused, and are not written specifically for use in an MCP server. They can be hooked up as tools to other conversational AI interfaces (e.g. Vercel's AI SDK).
+
+This project is in its early stages. Expect more and/or better tools soon.
+
+Nevertheless, our goal is to provide a small set of tools that enable complete workflows, rather than just atomic actions, striking a balance between flexibility and efficiency for LLMs.
+
+For our design philosophy, guidelines, and development patterns, see [docs/tool-design.md](docs/tool-design.md).
+
+### Available Tools
+
+For a complete list of available tools, see the [src/tools](src/tools) directory.
+
+#### OpenAI MCP Compatibility
+
+This server includes `search` and `fetch` tools that follow the [OpenAI MCP specification](https://platform.openai.com/docs/mcp), enabling seamless integration with OpenAI's MCP protocol. These tools return JSON-encoded results optimized for OpenAI's requirements while maintaining compatibility with the broader MCP ecosystem.
+
+## Dependencies
+
+- MCP server using the official [@modelcontextprotocol/sdk](https://github.com/modelcontextprotocol/typescript-sdk?tab=readme-ov-file#installation)
+- Todoist Typescript API client [@doist/todoist-sdk](https://github.com/Doist/todoist-sdk)
+
+## MCP Server Setup
+
+See [docs/mcp-server.md](docs/mcp-server.md) for full instructions on setting up the MCP server.
+
+## Local Development Setup
+
+See [docs/dev-setup.md](docs/dev-setup.md) for full setup instructions and [CONTRIBUTING.md](CONTRIBUTING.md) for contributor workflows and quality checks.
+
+### MCP Apps
+
+This project includes support for **MCP Apps** – interactive UI widgets rendered inline in AI chat interfaces. Widgets provide rich visual representations of tool outputs (e.g., task lists) instead of plain text.
+
+See [docs/mcp-apps.md](docs/mcp-apps.md) for the widget architecture, build pipeline, and development workflow.
+
+### Quick Start
+
+After cloning and setting up the repository:
+
+- `npm start` - Build and run the MCP inspector for testing
+- `npm run dev` - Development mode with auto-rebuild and restart
+- `npm run tool:list` - List available tools for direct execution
+- `npm run tool -- <tool-name> '<json-args>'` - Run a tool directly without MCP
+
+When using `npm run tool`, include `--` before tool arguments so npm forwards them to `scripts/run-tool.ts`.
+
+Example check before write operations:
+`npm run tool -- user-info '{}'`
+This confirms which Todoist account the current `TODOIST_API_KEY` is connected to.
+
+`run-tool` uses `TODOIST_API_KEY` from your `.env` file (created from `.env.example` by `npm run setup`). Use a test account or a temporary project when running write operations to avoid modifying real data.
+
+## Contributing
+
+See [CONTRIBUTING.md](CONTRIBUTING.md) for:
+
+- Development workflow
+- Running tools directly with `scripts/run-tool.ts`
+- Testing and quality checks
+- Commit conventions
+
+## Releasing
+
+This project uses [release-please](https://github.com/googleapis/release-please) to automate version management and package publishing.
+
+### How it works
+
+1. Make your changes using [Conventional Commits](https://www.conventionalcommits.org/):
+    - `feat:` for new features (minor version bump)
+    - `fix:` for bug fixes (patch version bump)
+    - `feat!:` or `fix!:` for breaking changes (major version bump)
+    - `docs:` for documentation changes
+    - `chore:` for maintenance tasks
+    - `ci:` for CI changes
+
+2. When commits are pushed to `main`:
+    - Release-please automatically creates/updates a release PR
+    - The PR includes version bump and changelog updates
+    - Review the PR and merge when ready
+
+3. After merging the release PR:
+    - A new GitHub release is automatically created
+    - A new tag is created
+    - The `publish` workflow is triggered
+    - The package is published to npm

package/dist/filter-helpers.d.ts

@@ -0,0 +1,51 @@
+import { TodoistApi } from '@doist/todoist-sdk';
+export declare const RESPONSIBLE_USER_FILTERING: readonly ["assigned", "unassignedOrMe", "all"];
+export type ResponsibleUserFiltering = (typeof RESPONSIBLE_USER_FILTERING)[number];
+/**
+ * Resolves a responsible user name/email to user ID and email.
+ * @param client - Todoist API client
+ * @param responsibleUser - User identifier (can be user ID, name, or email)
+ * @returns Object with userId and email, or undefined if not provided
+ * @throws Error if user cannot be found
+ */
+export declare function resolveResponsibleUser(client: TodoistApi, responsibleUser: string | undefined): Promise<{
+    userId: string;
+    email: string;
+} | undefined>;
+/**
+ * Appends a filter component to a query string with proper ' & ' separator.
+ * @param query - The existing query string
+ * @param filterComponent - The filter component to append
+ * @returns The updated query string
+ */
+export declare function appendToQuery(query: string, filterComponent: string): string;
+/**
+ * Builds a query filter string for responsible user filtering that can be appended to a Todoist filter query.
+ * @param resolvedAssigneeId - The resolved assignee ID (if provided)
+ * @param assigneeEmail - The assignee email (if provided)
+ * @param responsibleUserFiltering - The filtering mode ('assigned', 'unassignedOrMe', 'all')
+ * @returns Query filter string (e.g., "assigned to: email@example.com" or "!assigned to: others")
+ */
+export declare function buildResponsibleUserQueryFilter({ resolvedAssigneeId, assigneeEmail, responsibleUserFiltering, }: {
+    resolvedAssigneeId: string | undefined;
+    assigneeEmail: string | undefined;
+    responsibleUserFiltering?: ResponsibleUserFiltering;
+}): string;
+/**
+ * Filters tasks based on responsible user logic:
+ * - If resolvedAssigneeId is provided: returns only tasks assigned to that user
+ * - If no resolvedAssigneeId: returns only unassigned tasks or tasks assigned to current user
+ * @param tasks - Array of tasks to filter (must have responsibleUid property)
+ * @param resolvedAssigneeId - The resolved assignee ID to filter by (optional)
+ * @param currentUserId - The current authenticated user's ID
+ * @returns Filtered array of tasks
+ */
+export declare function filterTasksByResponsibleUser<T extends {
+    responsibleUid?: string;
+}>({ tasks, resolvedAssigneeId, currentUserId, responsibleUserFiltering, }: {
+    tasks: T[];
+    resolvedAssigneeId: string | undefined;
+    currentUserId: string;
+    responsibleUserFiltering?: ResponsibleUserFiltering;
+}): T[];
+//# sourceMappingURL=filter-helpers.d.ts.map

package/dist/filter-helpers.d.ts.map

@@ -0,0 +1 @@
+{"version":3,"file":"filter-helpers.d.ts","sourceRoot":"","sources":["../src/filter-helpers.ts"],"names":[],"mappings":"AAAA,OAAO,KAAK,EAAE,UAAU,EAAE,MAAM,oBAAoB,CAAA;AAGpD,eAAO,MAAM,0BAA0B,gDAAiD,CAAA;AACxF,MAAM,MAAM,wBAAwB,GAAG,CAAC,OAAO,0BAA0B,CAAC,CAAC,MAAM,CAAC,CAAA;AAElF;;;;;;GAMG;AACH,wBAAsB,sBAAsB,CACxC,MAAM,EAAE,UAAU,EAClB,eAAe,EAAE,MAAM,GAAG,SAAS,GACpC,OAAO,CAAC;IAAE,MAAM,EAAE,MAAM,CAAC;IAAC,KAAK,EAAE,MAAM,CAAA;CAAE,GAAG,SAAS,CAAC,CAaxD;AAED;;;;;GAKG;AACH,wBAAgB,aAAa,CAAC,KAAK,EAAE,MAAM,EAAE,eAAe,EAAE,MAAM,GAAG,MAAM,CAQ5E;AAED;;;;;;GAMG;AACH,wBAAgB,+BAA+B,CAAC,EAC5C,kBAAkB,EAClB,aAAa,EACb,wBAA2C,GAC9C,EAAE;IACC,kBAAkB,EAAE,MAAM,GAAG,SAAS,CAAA;IACtC,aAAa,EAAE,MAAM,GAAG,SAAS,CAAA;IACjC,wBAAwB,CAAC,EAAE,wBAAwB,CAAA;CACtD,GAAG,MAAM,CAmBT;AAED;;;;;;;;GAQG;AACH,wBAAgB,4BAA4B,CAAC,CAAC,SAAS;IAAE,cAAc,CAAC,EAAE,MAAM,CAAA;CAAE,EAAE,EAChF,KAAK,EACL,kBAAkB,EAClB,aAAa,EACb,wBAA2C,GAC9C,EAAE;IACC,KAAK,EAAE,CAAC,EAAE,CAAA;IACV,kBAAkB,EAAE,MAAM,GAAG,SAAS,CAAA;IACtC,aAAa,EAAE,MAAM,CAAA;IACrB,wBAAwB,CAAC,EAAE,wBAAwB,CAAA;CACtD,GAAG,CAAC,EAAE,CAWN"}