docs: canonicalize hosted MCP endpoint to taskade.com/mcp (closes #6)#37
Conversation
|
fba349a to
6ad207f
Compare
The hosted endpoint is live at https://www.taskade.com/mcp — an OAuth-protected remote MCP server (verified: WWW-Authenticate: Bearer realm="mcp" + OAuth discovery at /.well-known/oauth-authorization-server). Any remote-capable MCP client can authorize via browser — true zero-install, no API key to copy. Uses www (the non-redirecting canonical): bare taskade.com/mcp issues a 301 to www, and a 301 can downgrade POST->GET and break MCP's handshake. The server's own OAuth resource metadata also references www. - Add a zero-install hosted-endpoint callout to Quick Start - Remove the planned 'mcp.taskade.com' roadmap item (superseded) Closes #6
OAuth dynamic client registration currently admits claude.ai and loopback redirect URIs only, so the hosted endpoint works with Claude (web/Desktop/ mobile) and Claude Code today. Say that instead of 'any MCP client'.
6ad207f to
41c3120
Compare
✅ Validated → fixed → merging
Also rebased onto current QA: markdown-only; note sits above Quick Start without disturbing the 7-step numbering. Confidence: high · zero regression. Merging. Follow-up that makes "any client" true: widen |
Decision: use the live hosted endpoint at
https://taskade.com/mcprather than standing up a separatemcp.taskade.comsubdomain (no new infra, no redirect/rewrite fragility).Verified
https://taskade.com/mcpis an OAuth-protected remote MCP server:WWW-Authenticate: Bearer realm="mcp"on unauthenticated requests/.well-known/oauth-authorization-server(200) + resource metadata under/mcp/.well-known/oauth-protected-resourceSo remote-capable MCP clients authorize via browser — true zero-install, no API key to copy.
Changes
https://taskade.com/mcp.mcp.taskade.comroadmap item — superseded by the live endpoint.Closes #6. cc @deanzaka @lxcid