Basecamp

This connector uses the Basecamp 4 API (37signals.com — github.com/basecamp/bc3-api).

Setup:

1. Register an integration at https://launchpad.37signals.com/integrations.
2. Implement OAuth2 authorization-code flow with https://launchpad.37signals.com/authorization (response includes user's account_id).
3. Set BASECAMP_ACCESS_TOKEN to the obtained access token.
4. Set BASECAMP_ACCOUNT_ID to your Basecamp account ID (a 6-9 digit number — visible in any Basecamp URL or returned by the OAuth identity endpoint).

Authentication: Authorization: Bearer ${BASECAMP_ACCESS_TOKEN}.

Account-scoped base URL: every Basecamp account has its own subdomain. The API URL is https://3.basecampapi.com/${BASECAMP_ACCOUNT_ID}/.... The adapter substitutes the account ID via env var template.

User-Agent header: Basecamp REQUIRES a meaningful User-Agent header on every request (their support staff need it to identify integrations). The adapter sets User-Agent: AnythingMCP (https://anythingmcp.com) automatically.

Resource model:

• Project (called 'Basecamp' in the UI) — the top-level container.
• Dock — array of tools enabled on the project (todoset, message_board, schedule, vault, chat, etc.) each with its own URL.
• Todoset → multiple Todolists → multiple Todos.
• Message Board → multiple Messages.
• Comments can be attached to most recordings (todos, messages, etc.).

Recordings: Basecamp's underlying primitive. A todo, message, comment, etc. is all a 'recording' with an id and a type. Many endpoints accept any recording_id and dispatch by type.

Person picker: assignees are people IDs. List them via basecamp_get_people (account-wide) or per-project.

Status of completed todos: completed=true sends a Boolean — not a separate endpoint. To 'reopen' a todo, send completed=false on the same todo.

Pagination: 50 per page typical, Link header gives next URL. Some endpoints return all in one shot.

Rate limits: 50 req per 10 sec per account. On 429 honor Retry-After.

Out of scope here: Hill Charts, automatic check-ins, schedule entries, vault (file upload), Pings (DMs), Chat (Campfire) — all addressable via the API but each have idiosyncratic URLs returned by the Project dock; out of scope for this MVP connector.