Taskpile.app

MCPAI代理

提供方 twomasc

AI代理 未标注 OAuth 授权 社区 / 第三方 Claude DesktopClaudeCursorVS Code

Never forget a thing. Stay focused on what matters today. Taskpile is a personal task tracker that catches every thought, errand, or "I should…" in seconds — from Claude, ChatGPT, Cursor, Le Chat, Lovable, or any MCP-compatible chat client.

一句话选型结论

按资料字段整理

Taskpile.app 属于AI代理类 MCP 服务器,传输方式未标注,OAuth 授权,可直接接入 Claude Desktop、Claude、Cursor 等,没有现成安装命令,需按官方文档接入。接入前先确认权限范围;涉及写入、删除或付款的操作,建议先在测试环境验证。

分类AI代理 传输方式未标注 鉴权OAuth 授权 部署方式未标注
GitHub 星标 未标注 仓库热度,无公开仓库时显示未标注
工具数 未标注 暴露给模型的工具数量
资源 / 提示词 0 / 0 资源与提示词模板数量
维护方 社区 / 第三方 核验等级 仅资料核对

工具与能力

AI代理
数量来自来源目录的标注,具体工具清单以官方文档为准
工具数量未标注暴露给模型可调用的工具个数
资源数量0可读取的资源条目
提示词数量0内置提示词模板数量

能力标签

tasks task management productivity todo personal planner workflow

支持客户端

适用场景

taskstask managementproductivity

安装与配置

未标注 OAuth 授权
上游未给出传输方式
  1. 1
    准备运行环境

    按官方文档确认运行环境(常见为 Node.js 或 Python),装好后再执行安装命令。

  2. 2
    安装服务

    复制上面的安装命令执行;命令里带占位符的位置,换成自己的密钥或路径。

  3. 3
    写入客户端配置

    在客户端的 MCP 配置里填好启动命令和参数,保存后完全退出客户端再打开,让新配置生效。

  4. 4
    验证是否可用

    连接成功后随便调一个只读工具,确认能返回结果,再接入正式流程。

典型使用场景

3 类
按分类与标签整理的常见用法,具体以官方文档为准
给代理接外部能力

让代理在任务中途调用搜索、数据库等真实工具。

多步任务编排

把一串操作拆成步骤,由代理按顺序执行。

自动化重复流程

把固定流程交给代理跑,减少手工操作。

选择建议

选之前先看这几条
按条目字段给出的判断,不替你决定用不用

值得选的地方

  • 已适配 Claude Desktop、Claude、Cursor,换客户端不用重新研究配置。

先想清楚的地方

  • 没有现成安装命令,需要按官方文档自己填启动命令和参数。
  • 使用前要准备好OAuth 授权对应的凭据,并按最小权限配置。
  • 资料没标注工具数量,实际能力要装好后确认。
  • 版本更新与行为细节以官方仓库为准。

更适合

  • 需要在AI代理场景里让模型直接调用外部能力的人。
  • 已经在用 Claude Desktop、Claude 的用户,接入路径最短。
  • 想先快速试一下、能接受在本地或自有环境跑服务的人。

不太适合

  • 不方便管理密钥或第三方授权的人。
  • 需要厂商级 SLA 和技术支持的生产环境。

同类对比

6 个同类
同分类里挑最接近的几条,字段以各自详情页为准
MCP 服务器工具数传输方式部署方式安装命令最后核验
Taskpile.app当前 未标注 未标注 未标注 无 未标注
Filesystem 560c4363 13 未标注 本地部署 无 2026-05-17
Server Everything (everything) 11 stdio · 本地进程 本地部署 有 2026-05-17
Time 7365cb6d 2 SSE · 服务端推送 远程部署 有 2026-05-18
Everything Claude Code 未标注 stdio · 本地进程 本地部署 有 2026-05-17
Openmemory 557e1585 未标注 stdio · 本地进程 本地部署 有 2026-05-17

服务器档案

AI代理
字段来自项目仓库与公开索引,中文说明由本站标注
提供方twomasc上游标注的维护方 twomasc
分类AI代理本站按上游分类展示
连接方式未标注上游未给出传输方式
鉴权方式OAuth 授权远程服务建议用最小权限凭据
维护方社区 / 第三方核验等级 仅资料核对
包名 / 运行时未标注 · Cross-platform本地安装时用到的包标识与运行时
部署类型未标注上游给出的部署形态
最近核验未标注上游最后核验时间

详细介绍

6.7 KB
来自项目仓库与上游目录的原文,未做删改

Taskpile MCP

Public documentation for Taskpile's Model Context Protocol server.

Never forget a thing. Stay focused on today. Taskpile is a personal task tracker built around two verbs: pile in, sort out. Capture anything the moment it shows up, from Claude, ChatGPT or any MCP-compatible client, or in the app at taskpile.app. A two-minute daily review turns the pile into one short Today list; everything else waits its turn.

Taskpile is listed in the Claude connectors directory.

  • App:
  • MCP endpoint: https://taskpile.app/api/mcp
  • Transport: Streamable HTTP (JSON-RPC 2.0)
  • Protocol versions supported: 2025-11-25, 2025-06-18, 2025-03-26, 2024-11-05

This repository contains only public-facing documentation for the MCP integration. The Taskpile app itself is a hosted commercial product: its source isn't here, but everything you need to connect a client and use the MCP tools is.

Connecting

Any MCP-compatible client can connect by pointing at the URL above. Authentication uses OAuth 2.1 with Dynamic Client Registration + PKCE. The client handles this automatically; users sign in to Taskpile in a browser tab when prompted.

Verified clients:

Client Status
Claude.ai (Connectors) ✅
Claude Desktop (via mcp-remote) ✅
Claude Code ✅
ChatGPT (Connectors) ✅
Le Chat (Mistral) ✅
Cursor ✅
Zed ✅
MCP Inspector ✅
Lovable.app ✅

Quick start by client

See examples/ for ready-to-paste config snippets:

  • Claude Desktop
  • Cursor
  • Cline (VS Code)
  • MCP Inspector

For hosted clients like Claude.ai and ChatGPT, add Taskpile via their built-in connector UI and paste the URL above; no local config needed.

Tools

Taskpile exposes 72 tools spanning task CRUD, projects, tags, colors, search, bulk operations, teams, and account integrations like morning digest and task reminders. The full machine-readable schema (names, descriptions, JSON Schema for inputs and outputs) is in tools.json, generated from the server's tool schema.

tools/list is tailored to the account, so a client usually sees fewer than 72: team administration tools appear once the user belongs to a team, project-member tools once they have a shared project, assignment/triage tools once they can reach a team-owned project, and search/fetch only for OpenAI clients. Hidden tools stay callable; the entry points (create_team, convert_project_to_shared, invite_to_project, list_received_invitations, accept_invitation) are always listed.

A quick taste:

  • create_task, list_tasks, update_task, complete_task, delete_task
  • assign_horizon (today_morning, tomorrow, next_week, etc.), delegate_task, set_recurrence
  • list_projects, create_project, archive_project
  • search_tasks (free-text + status/horizon filters)
  • bulk_complete, bulk_archive (reversible, prefer it over bulk_delete), bulk_delete, bulk_assign_horizon (up to 200 ids per call)
  • changes_since (incremental sync: deletions are not reported, so reconcile with a full fetch periodically; capped at 500 rows per call), get_today, get_review_queue
  • list_closed_tasks (what got completed in a date range)
  • get_morning_digest, configure_morning_digest, get_task_reminders, configure_task_reminders
  • list_colors, create_color, update_color, delete_color
  • whoami, get_inbox_email
  • Teams: create_team, invite_to_team, accept_invitation, assign_task, convert_project_to_shared, etc.
  • search and fetch (ChatGPT Connectors built-in tools, mapped to Taskpile)

Conventions

A few project-wide conventions worth knowing if you're writing a prompt:

  • Tags use @tag_name. Projects use #project_name. Do NOT use # for tags: #foo is silently treated as a project name.
  • create_task parses #project and @tag shorthand from the title. Only the FIRST # token becomes the project; the rest are stripped.
  • #name resolution covers projects shared with you, not just your own. If the name is unique it's used; if it's ambiguous (e.g. a private AND a shared project with the same name) the call fails with a candidate list: ask the user which, then retry with an explicit projectId. If nothing matches, a new project you own is created.
  • To set tags at creation, pass tags: string[] and/or put @tag in the title. Both forms work and are de-duplicated.
  • update_task does not parse #/@ shorthand from the title. Use tags / addTags / removeTags and projectId to change those.
  • Prefer dedicated verbs over update_task when they exist: complete_task, assign_horizon, delegate_task.
  • Bulk endpoints accept up to 200 ids per call.

Auth flow

If you're building a client and want to know what to expect:

  1. Client sends an unauthenticated request to https://taskpile.app/api/mcp and receives 401 with WWW-Authenticate: Bearer realm="taskpile", resource_metadata="https://taskpile.app/.well-known/oauth-protected-resource".
  2. Client fetches https://taskpile.app/.well-known/oauth-protected-resource and …/oauth-authorization-server to discover endpoints.
  3. Client POSTs to https://taskpile.app/oauth/register for Dynamic Client Registration (RFC 7591).
  4. Client kicks off the standard authorization-code + PKCE flow, opens a browser at /oauth/authorize, exchanges the code at /oauth/token, and receives an access_token.
  5. Subsequent requests carry Authorization: Bearer. Access tokens are valid for 30 days. A client that registers the refresh_token grant also gets a refresh token, valid for 90 days and rotated on every use; other clients re-run the authorize/token flow on expiry. Tokens can be revoked at /oauth/revoke (RFC 7009).

HEAD /api/mcp returns 200 without auth and is intended for liveness probes only.

Privacy + data handling

  • Taskpile is GDPR-compliant. Tasks, projects, and tags created via MCP are user-owned and visible only to the authenticated user (and their team members for shared projects).
  • The MCP integration sends task content to Taskpile's servers (EU-hosted). It does NOT route through Anthropic, OpenAI, or any other LLM provider: those are clients of the MCP server, not the server itself.
  • Personal access tokens can be created in Taskpile → Settings → Integrations and revoked at any time.

Issues and feedback

This repo is for documentation. Bug reports about the MCP server, feature requests for new tools, or questions about the API: please open an issue here and we'll triage.

For Taskpile app issues (unrelated to MCP), please contact us through the app at .

License

Documentation in this repository is MIT-licensed (see LICENSE). The Taskpile app itself is a hosted commercial product and is not licensed for redistribution.

常见问题

7 问
答案由本站依据条目字段整理,不引用上游原文
Taskpile.app 怎么安装?

资料没有给出安装命令,请到官方仓库或文档按说明接入;这类条目多数是生态应用,或尚未发布可安装包。

Taskpile.app 怎么在 Claude Desktop、Claude、Cursor 里配置?

它的传输方式未标注,在客户端的 MCP 配置里填好启动命令和参数,保存后完全退出客户端再打开,配置才会生效。

Taskpile.app 收费吗?

本站不代收费用,也没有标注具体价格。是否收费取决于服务本身和背后的接口额度,正式使用前按官方说明确认。

Taskpile.app 需要 API Key 吗?

资料标注需要OAuth 授权认证,使用前准备好对应凭据,并按最小权限配置。

Taskpile.app 支持哪些客户端?

资料标注支持 Claude Desktop、Claude、Cursor、VS Code、Cline、Gemini CLI;其他客户端只要能配置 MCP Server,也能用同样的命令或地址接入。

Taskpile.app 能提供哪些能力?

资料显示能力标签包括 tasks、task management、productivity、todo、personal、planner。具体工具清单以官方文档为准。

Taskpile.app 需要什么运行环境?

运行时为 Cross-platform。

热门专题

按标签挑服务器
全部专题 →

服务器信息以作者仓库与官方文档为准;分类、传输方式与鉴权方式的中文说明为中文整理,最近核验 未标注。