Knowledge is attached one project or one media file at a time, which keeps the wiring explicit — an agent knows what you handed it and nothing more. Because everything is addressed by id, a session usually opens with the workspace and folder listings before anything interesting happens, and the newer agent-chat and webhook tools sit beside older names for the same reads, so expect some duplication when you scan the list.
Taskade's own server over its API: 62 tools split between project and task work and the agent side — creating agents, giving them knowledge, prompting them and reading their conversations back.
- Projects created from content, from a custom template or by copying an existing one, completed and restored, and listed per folder, per workspace or for you alone
- Tasks created several at a time, moved within a project, completed and reopened, carrying notes, start and end dates, assignees by handle and per-project field values
- Agents created by hand or generated from a text prompt, updated, deleted and prompted directly from the client
- Agent knowledge assembled from projects and uploaded media, added and removed one source at a time
- Agent conversations listed and read back, so what an agent has been telling people stays reviewable
- Share links switched on and fetched for a project, and public access enabled for an agent with its public preferences updated
- Webhook subscriptions created against a trigger type and removed by hook id, so changes push outward instead of being polled for
A Personal Access Token from Taskade's API settings, in TASKADE_API_KEY, and the workspace, folder or project ids you mean to act on — nearly everything is addressed by id, and the workspace and folder listings are where those come from. Plan matters here: some endpoints, workspace listing among them, are gated on free accounts. Running it with --http instead of stdio serves the same tools on port 3000 for remote clients. Note that Taskade also publishes a separate hosted server for editing a deployed app's code; this package is the one that reads and writes workspace content. MIT.
One command plus a key — npx @taskade/mcp-server, then supply credentials