Set up GetItDone in Claude Code

Let Claude Code do it: paste this sentence and it follows the setup prompt itself. The steps below are the same ones, by hand.

Fetch and execute the appropriate instructions to set me up for GetItDone from https://nowgetitdone.com/agent-setup/prompt.md

Add to Claude

Fastest: Add to Claude

Using claude.ai or Claude Desktop as well? Add GetItDone to Claude opens GetItDone in Claude's connector directory; choose Connect, then sign in.

Manual: add as a custom connector (Claude's Add custom connector dialog with the name and URL filled in).

1. Get an API key

Create a key at Profile → API Keys and store it in your project's .env as GETITDONE_API_KEY=gid_…. Keep .env in .gitignore.

2. Connect the MCP server

Config: ~/.claude.json (local scope: private to this user and this project)

Run the commands below from the project root. The default local scope keeps the key out of .mcp.json and out of the repository.
Tell the user to restart Claude Code (or open /mcp) so the getitdone server loads.

set -a; . ./.env; set +a
claude mcp add --transport http getitdone https://app.nowgetitdone.com/api/mcp --header "Authorization: Bearer $GETITDONE_API_KEY"

No key? Run claude mcp add --transport http getitdone https://app.nowgetitdone.com/api/mcp without the header, then open /mcp, pick getitdone and sign in to GetItDone in the browser.

3. Tell Claude Code about GetItDone

Append this block to CLAUDE.md.

Add .env to .gitignore if it is not already there, so the key never lands in a commit.
Tell the user they can ask for GetItDone work in plain language now, e.g. "what can I actually start today?".

markdown

## GetItDone

GetItDone is the task manager this project talks to.

- MCP server: `getitdone` at https://app.nowgetitdone.com/api/mcp. Prefer it for tasks, projects and workspaces: call `search_tools` first, then run one `execute_typescript` program that calls the tools it found. When the connection reaches more than one workspace, pass the `workspaceId` from `list_workspaces`.
- REST API for everything else: base URL https://app.nowgetitdone.com/v1
- Auth: send the key from the GETITDONE_API_KEY environment variable as `Authorization: Bearer <key>`
- OpenAPI spec (source of truth for paths and payloads): https://nowgetitdone.com/docs/api/openapi.json
- Human reference: https://nowgetitdone.com/docs/api
- Errors are RFC 9457 problem+json: switch on `code`, back off on 429 honouring `Retry-After`, and send an `Idempotency-Key` on POSTs that create something.

Never print the key. Prefer reading the spec over guessing an endpoint.

4. Verify

set -a; . ./.env; set +a
curl -s -H "Authorization: Bearer $GETITDONE_API_KEY" https://app.nowgetitdone.com/v1/organizations
curl -s -X POST https://app.nowgetitdone.com/api/mcp -H "Authorization: Bearer $GETITDONE_API_KEY" -H "Content-Type: application/json" -H "Accept: application/json, text/event-stream" -d '{"jsonrpc":"2.0","id":1,"method":"tools/list"}'

The first command lists the workspace the key belongs to; the second lists the MCP tools, including search_tools and execute_typescript. A 401 means the key is missing, revoked or mistyped.

Every client and the full tool list: MCP server guide.