Set up MCP in four steps
Give Claude or Cursor read-and-write access to your Taskwich projects. Takes about six minutes.
Install the connector
One command puts a single taskwich-mcp executable on your path and nothing else. The connector runs on Node.js 20 or newer — the script checks and tells you if it's missing.
curl -fsSL https://taskwich.app/install/mcp.sh | sh
Installs to ~/.local/bin. If that folder isn't on your PATH — common on macOS — the script prints the exact line to add to your shell profile.
Re-running the same command upgrades in place
Create an API key
Open Settings → API keys and create one. Name it after the machine you're on — that name is what you'll look for when revoking it later. The secret is shown once; copy it into your client config straight away.
Treat the key like a password. Anyone holding it acts as you in this workspace. Keep it out of chats, screenshots, and version control.
Wire it into your client
Claude Code, once per machine:
claude mcp add taskwich --env TASKWICH_API_KEY=tsk_... -- taskwich-mcp
Claude Desktop and Cursor take the same JSON, on every platform. Claude Desktop keeps it under Settings → Developer → Edit config; Cursor reads ~/.cursor/mcp.json. Quit Claude Desktop fully and reopen it — closing the window isn't enough.
- macOS — Claude Desktop doesn't read your shell profile. If it can't find the bare command, put the absolute path — /Users/<you>/.local/bin/taskwich-mcp — in the command field instead.
- Windows — if the command isn't found right after installing, restart the app; it inherits the PATH it was launched with.
Verify
Start a new session and run /mcp — you should see 71 tools across 12 domains. Permissions follow your user: the agent can never reach further than you can. The full list lives in the MCP tools reference.
Settings
| Field | Expected value | Required | Flag |
|---|---|---|---|
| TASKWICH_API_KEY | Personal key — starts with tsk_ | Required | --api-key= |
| TASKWICH_API_URL | URL — defaults to https://taskwich.app | Optional | --api-url= |
Prefer environment variables — flags show up in process listings. The connector refuses plaintext HTTP for any host that isn't localhost, requests time out after 30 seconds, and the key is never echoed back in an error message.
Revoking access
Delete the key in Settings → API keys. The client loses access on its next request — there is no cache to wait out and no session to expire.