Can AI agents automate Basecamp?

Basecamp is automatable today through its HTTP API. This record is the current Basecamp product from 37signals. The homepage calls the 2026 release Basecamp 5. HEY and Fizzy are separate products. API URLs start at https://3.basecampapi.com/{accountId}/ and end in .json. Requests send Authorization: Bearer and a User-Agent that names the application. Missing User-Agent returns 400. The authorization guide says every Basecamp 5 request uses an OAuth 2 token. Access tokens expire after two weeks. The same guide says Basecamp also accepts a personal access token and a legacy Launchpad token, and that a DPoP-bound token must use Authorization: DPoP rather than Bearer. The official SDK README says there is no API key and no personal access token, and that a static token is one the caller already holds. Account selection uses the product code bc3. The API reference lists projects, todos, messages, card tables, campfires, people, and many other resources, paginates with Link and X-Total-Count, and describes a first common limit of 50 requests per 10 seconds per IP. Official SDKs exist for Go, Ruby, TypeScript, Swift, Kotlin, Python, and Rust. The basecamp CLI is the official command-line interface, prints JSON with --json, and can log in with the OAuth device flow when the server advertises it. basecamp mcp serves that signed-in account over stdio, with a read-only flag. The pricing page still says official full MCP support for ChatGPT, Claude, and AI agents is coming soon. Webhooks POST JSON to an HTTPS URL. Connector catalogs were not opened. https://basecamp.com/llms.txt returned 404 on this pass, so an llms.txt guide is not established. Computer-use viability is unassessed. The API and CLI both score 8. The API is the best path because it does not depend on the local basecamp binary. The MCP command scores 7.

Best path today: api · Overall automatability: 8/10