# Your Basecamp projects. The check-in, drafted. Source: https://corespeed.io/integrations/basecamp Connect Basecamp to Claude Code, Codex, Cursor or any MCP agent through CoreSpeed. Your agent lists your projects and their people, reads each list's open to-dos with assignees and due dates, and drafts a check-in of the open work and who holds it. It uses your own Basecamp account, and adding a to-do is a separate call. ## Set up an agent Give your agent this line: `set up https://corespeed.io/SKILL.md (read it raw, e.g. with curl)` It fetches the skill at https://corespeed.io/SKILL.md, adds the CoreSpeed MCP server, signs you in (or up), and keeps the skill for next time. Connect Basecamp after setup. Access follows the connected account and its permissions. Create an account: https://app.corespeed.io/sign-up ## Read the to-dos. Write the check-in Ask your agent to read the open to-dos in a Basecamp project, then draft a check-in with what is due and who holds each item. You ask your agent: "Read the Office move project in Basecamp. Draft a check-in of the open to-dos, what is due first and who holds each one. Do not add any to-dos." It calls CoreSpeed: - `basecamp__get_project`: ok, 322 ms - `basecamp__list_todolists`: ok, 284 ms - `basecamp__list_todos`: ok, 409 ms It reads from: Basecamp. ### Check-in: Office move, on one page. Twelve to-dos are open. The movers are due Friday, and labeling has no one assigned. **Due first** - Book the movers by Friday. - Return the old keys by Monday. **Unassigned** - Label the boxes. _Illustrative example · Fictional data · No to-dos added_ All connectors: https://corespeed.io/docs/connectors ## From to-do lists to a clear check-in Requests you can make once Basecamp is connected. The data is fictional. ### See the open to-dos Office move · Logistics · To-do list - Open: Book the movers - No one assigned: Label the boxes - From the projects you can access ### Draft the check-in Office move, this week · Draft in your agent - Include: Open work, due dates, owners - Keep separate: Suggested new to-dos - No to-do added ### Hold a new to-do for review Add a to-do · Example approval policy - Policy: Ask before adding to a project - Outcome: The to-do waits for a person - Approval required Full example: https://corespeed.io/solutions/agent-approvals (Markdown: https://corespeed.io/solutions/agent-approvals.md) ## Keep your agent. Bring your work One CoreSpeed account, across compatible agents. 1. **Set up CoreSpeed**: Give your agent the setup line. It adds CoreSpeed and signs you in. 2. **Connect Basecamp**: Authorize the account and the content you need. 3. **Start with one task**: Ask for a summary, a brief, or a draft. Review the answer. Setup guides: Claude Code https://corespeed.io/docs/mcp#claude-code · Codex https://corespeed.io/docs/mcp#codex · Cursor https://corespeed.io/docs/mcp#cursor ## Questions ### Which parts of Basecamp does it read? Projects, the people on them, to-do lists and their open to-dos. Completed to-dos, message boards, schedules and chat are not part of this connection. ### Can I limit access to some projects? Not in Basecamp itself: its authorization covers the whole account. Your agent sees the projects your Basecamp account can see. ### Does it add to-dos on its own? No. Adding a to-do is a separate tool call, which approvals can hold for a person. ### Do I have to switch agents? No. CoreSpeed adds tools to the agent you already use: Claude Code, Codex, Cursor, or another MCP client. Each one signs in once. ### Can my agent access every account in our organization? No. Access follows your CoreSpeed identity, each connection's visibility, and the app's own permissions. Personal connections stay private. ### Does this work without connecting an account? No. Connect the app's account first; your CoreSpeed workspace shows what each app needs. The examples on this page use fictional data. All connectors: https://corespeed.io/docs/connectors Every tool and price: https://corespeed.io/catalog/basecamp ## Related pages - [Approval gates for AI agent tool actions](https://corespeed.io/solutions/agent-approvals): Set approval policies for writes through CoreSpeed. Review held tool actions while your team keeps using its preferred agents. - [Linear for Claude Code, Codex, and Cursor](https://corespeed.io/integrations/linear): Bring Linear issues and project context into your agent. See what is moving and what needs attention. - [Todoist for Claude Code, Codex, and Cursor](https://corespeed.io/integrations/todoist): Bring Todoist tasks and projects into your agent. Plan the day from today and overdue, and draft tasks before adding them. - [Wrike for Claude Code, Codex, and Cursor](https://corespeed.io/integrations/wrike): Bring Wrike tasks and their comments into your agent. Draft a review of what is deferred or waiting, and why. ## Sources - Connectors: https://corespeed.io/docs/connectors - Basecamp API: https://github.com/basecamp/bc3-api - Basecamp API: To-dos: https://github.com/basecamp/bc3-api/blob/master/sections/todos.md Reviewed 2026-11-10. ## Links - Product overview: https://corespeed.io/ (Markdown: https://corespeed.io/index.md) - All integrations: https://corespeed.io/integrations (Markdown: https://corespeed.io/integrations.md) - Documentation: https://corespeed.io/docs - Pricing: https://corespeed.io/pricing (Markdown: https://corespeed.io/pricing.md)