Get the hosted Taskade MCP server into the Claude connectors directory

未关闭
#90 1 条评论 0 个 reaction 已指派 1 人 在 GitHub 查看

维护者通常 1 天内回复

@johnxie 已经在做这个了。

开始于 2026年10月9日。

评估

这个 Issue 还没有评估数据。

描述

cc @deanzaka

Goal

List the hosted Taskade MCP server (https://www.taskade.com/mcp) in the Claude connectors directory, and close the gaps in this repo for setup UX and visibility.

Parent: taskade/taskcade#31571. The server-side blocker (no tool annotations on the 48 hosted tools) is fixed in taskade/taskcade#31575.

Sources

Gap table: Claude connectors directory

# Requirement (source) Taskade today Gap Where to fix Effort
1 Remote server on an https:// URL, Streamable HTTP (policy 5F, submission checklist) https://www.taskade.com/mcp, Streamable HTTP, live None - -
2 401 with resource_metadata, PRM resource equals the URL, first authorization_servers entry is the issuer (auth doc) All three hold None - -
3 OAuth 2.0 for a service that acts on a user account (policy 5D) OAuth 2.0 + PKCE S256, public client, refresh rotation, invalid_grant None - -
4 Client registration: DCR, CIMD or Anthropic-held credentials (auth doc) DCR live, redirect allowlist covers claude.ai and loopback on any port CIMD not advertised. Claude prefers CIMD or Anthropic-held credentials for high-traffic servers, because DCR registers a client on each fresh connection. findOrCreatePublicPkceMcpApplication dedupes by {client_name, redirect_uris}, so the row growth is bounded. Not a blocker. taskcade routes/oauth2.ts, routes/well-known/oauth.ts M (follow-up)
5 OAuth endpoints answer in 10 s, refresh in 30 s (auth doc) Not measured Owner check during the custom-connector test - S
6 Every tool has title and readOnlyHint or destructiveHint (submission checklist, policy 5E) Hosted: 0 of 48 tools had any annotation Blocker. Fixed in taskade/taskcade#31575: one table, 48 titles, read-only / destructive / idempotent / open-world hints, test over tools/list taskcade src/backend/concerns/user-mcp/ S (done, in review)
7 Tool names 64 characters or fewer (policy 5C) Longest hosted name: create_project_from_template (28) None - -
8 Separate read and write tools, no catch-all api_request (review criteria) Every tool is one purpose-built operation None - -
9 Narrow, accurate descriptions, no prompt-injection patterns (policy 2A-2G) Descriptions name sibling tools ("Get ids from list_agents"), which is allowed. write_file says "IMPORTANT: Always read the file with inspect_space before editing." Low risk. Reviewer can read the IMPORTANT line as an instruction to Claude. Consider plain wording. taskcade tools/write-file.ts S (optional)
10 Helpful errors, no generic "Bad Request" (policy 5A) mcpClientError returns a message per case None found - -
11 Token frugality (policy 5B) Several tools return JSON with 2-space indent. read_project returns the full tree. Low. Compact JSON saves tokens. taskcade tools/*.ts S (optional)
12 Privacy policy URL (policy 3A, portal Listing step) https://www.taskade.com/privacy (200) README had no hosted privacy text taskade/mcp README (PR) S (done, in review)
13 Support contact (policy 3B) [email protected] in SECURITY.md, README said [email protected] README now lists help center, email and issues taskade/mcp README (PR) S (done, in review)
14 Documentation: setup, purpose, troubleshooting, 3+ working example prompts (policy 3C, 3E) README described the hosted server as browse-only ("task-level writes still live in this local package"), which is false since Phase A. Its Cursor and VS Code buttons used cursor:// and vscode: links, which GitHub strips. No hosted examples. Fixed in the README PR: hosted-first quick start for Claude, Claude Code, Cursor, VS Code, Windsurf, API token; 48-tool table; 5 example prompts; troubleshooting table taskade/mcp README (PR); optional mirror in taskade/docs and help.taskade.com S (done, in review)
15 Test account with sample data (policy 3D, portal Test & launch) None Owner: a paid workspace with projects, tasks, custom fields, agents, a Genesis app Owner M
16 Icon (portal Listing step) PNG at https://www.taskade.com/images/taskade-icon-512.png and -1024.png, SVG at /favicon.svg Owner uploads one in the portal Owner S
17 Listing copy: name (100), one-liner (200), description (2,000), 1-5 categories, permanent slug (portal) None Owner approves. Draft below. Owner S
18 Use cases, prerequisites, read/write (portal Use cases step) Paid plan needed; reads and writes Owner fills in. Prerequisite: a Taskade paid plan (Starter and up). Owner S
19 Data handling: first-party API, no health data, no sponsored content (portal Data handling step) First-party API on taskade.com Owner answers Owner S
20 Seven compliance acknowledgments (portal) - Owner answers. Check 4B (no AI image/video/audio generation): no hosted tool generates media. prompt_agent runs a user agent, which can carry its own tools. Owner S
21 Every tool run once as a custom connector or in MCP Inspector (portal Test & launch) Not done after #31575 Owner or eng runs all 48 tools from Claude after the deploy Owner + eng M
22 Production quality (policy 3G maintain) UserMcpServer description starts with [BETA] and says "tools and behavior may change" Not a written rule, but the description is visible to clients. Owner call: drop [BETA] before submission. taskcade src/backend/concerns/user-mcp/mcp-server.ts S (owner call)
23 Own the domain and API (policy 3F) taskade.com None - -
24 Submitter on a paid Claude plan (submission checklist) - Owner Owner S

Gap table: other directories

Directory Taskade today Gap Where to fix Effort
Claude connectors directory Not listed (https://claude.com/marketplace/connectors/taskade returns 404) Rows 6 and 12-24 above taskcade PR + owner portal submission M
Official MCP Registry Listed: io.github.taskade/mcp-server 0.1.0, 0.1.1, 0.1.2. 0.1.2 is latest and has remotes: [{type: streamable-http, url: https://www.taskade.com/mcp}] (#83). Publish runs from .github/workflows/publish-mcp-registry.yml on each @taskade/mcp-server@* tag (GitHub OIDC). No websiteUrl, no icons. Issue taskade/mcp#77 ("hosted server absent") is stale since #83 and 0.1.2. taskade/mcp packages/server/server.json (PR). Goes live with the next npm release. S (done, in review)
modelcontextprotocol/servers README The README has no third-party list now. It sends readers to the registry. None (the registry entry covers it) - -
VoltAgent/official-mcp-servers Listed in Productivity: taskade/mcp - Taskade projects, tasks and agents After a Claude listing, add ([Claude](https://claude.com/marketplace/connectors/<slug>)) like Asana and Linear PR to VoltAgent/official-mcp-servers (owner) S
wong2/awesome-mcp-servers Listed None - -
punkpeye/awesome-mcp-servers (96k stars) Not listed Optional PR Owner S
Cursor .cursor-plugin/ manifest with the hosted URL; logo was favicon.ico Logo now the 512 PNG (registry PR). README now has a working https://cursor.com/install-mcp button. taskade/mcp (PR) S (done, in review)
VS Code README button used vscode: (stripped by GitHub) Now https://vscode.dev/redirect/mcp/install taskade/mcp README (PR) S (done, in review)
Smithery smithery.yaml is stdio-only. https://smithery.ai/server/@taskade/mcp returns 404. Optional: list the hosted URL on Smithery Owner S
Glama, mcp.so Pages return 200 (content renders client-side, not verified) None known - -

Submission checklist (owner steps, nothing done yet)

  • Review and merge taskade/taskcade#31575, then deploy.
  • Run every hosted tool once from Claude: Customize > Connectors > Add custom connector, URL https://www.taskade.com/mcp. Confirm that the read tools run without a prompt and the delete tools ask.
  • Decide on the [BETA] text in the server description (row 22).
  • Create the reviewer test account: a paid workspace with sample projects, tasks with dates and custom fields, two agents with knowledge, and one Genesis app.
  • Review and merge the three taskade/mcp PRs. The npm patch release (changeset) publishes the new server.json to the MCP Registry.
  • Close taskade/mcp#77 (stale) and decide on taskade/mcp#87.
  • From a paid Claude account, open https://claude.ai/directory/manage > Submit new > MCP connector. Use the draft copy below, the 512 PNG icon, docs URL https://github.com/taskade/mcp#readme (or a help.taskade.com page), privacy URL https://www.taskade.com/privacy, support [email protected].
  • Authentication step: OAuth with dynamic client registration.
  • Track the status in the portal. Escalation: [email protected].
  • After the listing is live, add the Claude link to the VoltAgent/official-mcp-servers entry and the README badges.
主要语言
TypeScript
星标
170
派生
55
平均合并
1 天 5 小时
30 天内合并 PR
25

环境准备

  • 提供 Dockerfile 或 Docker Compose 文件
  • 没有 Pull Request 模板
  • 阅读贡献指南

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

taskade/mcp 的其他 Issue

查看 taskade/mcp 的全部 Issue

相似的 Issue

更多 TypeScript Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。