Set up MCP in four steps
Give Claude, Codex, Cursor or any other MCP client 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.
It opens a browser to approve; no key to copy. The installer then opens your browser to approve and registers Taskwich in the AI tools it finds. If it finishes, you can skip to Verify.
Re-running the same command upgrades in place
Manual route: create an API key
Only needed if the installer can't reach your client. 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.
Manual route: wire it into your client
Pick your AI tool and replace tsk_... with your key. Creating a key in Settings → API keys shows these same snippets with the key already filled in.
$ claude mcp add --scope user --env TASKWICH_API_KEY=tsk_... --transport stdio taskwich -- taskwich-mcp
- The key ends up in your shell history. On a shared machine, clear it afterwards.
Verify
Start a new session and run /mcp — you should see 108 tools across 13 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.