What is a Basecamp MCP server?
It’s an MCP server that exposes data and functionality from an instance of Basecamp via tools. Your agents can call these tools to perform a wide range of tasks, from create a to-do task to updating a project’s name.
How can I use the Basecamp MCP server?
Here are just a few use cases (these also apply to other project management MCP servers):
- Project status reporting: Pull projects, to-dos, and milestones to generate a daily or weekly status update for a team
- Auto-create project plans: Create a new Basecamp project from a short prompt (project name, owners, key deliverables), then set up the initial to-do lists
- Meeting-to-workflow: Turn meeting notes into Basecamp to-dos, assign owners, and set due dates
- Task triage and assignment: Scan unassigned or overdue to-dos and propose (or apply) assignments and updated due dates
- Executive summaries: Summarize what changed since the last check-in across projects (new to-dos, completed work, risks)
- Cross-tool coordination: When work changes elsewhere (for example, an issue is marked “Ready” in Jira), create or update the corresponding Basecamp to-do
What are popular tools for Basecamp’s MCP server?
Here are a few tools across data types:
Comments
- <code class="blog_inline-code">list_comments</code>
- <code class="blog_inline-code">get_comment</code>
- <code class="blog_inline-code">create_comment</code>
- <code class="blog_inline-code">update_comment</code>
Projects
- <code class="blog_inline-code">list_projects</code>
- <code class="blog_inline-code">get_project</code>
- <code class="blog_inline-code">update_project</code>
To-dos
- <code class="blog_inline-code">update_todo</code>
- <code class="blog_inline-code">complete_todo</code>
- <code class="blog_inline-code">create_todo</code>
- <code class="blog_inline-code">uncomplete_todo</code>
What makes Merge Agent Handler’s Basecamp MCP server better than alternative Basecamp MCP servers?
Merge Agent Handler’s Basecamp MCP server offers more robust, enterprise-grade platform capabilities:
- Managed authentication and credential handling: Merge guides users through authorization and securely manages credentials for connected tools
- Enterprise-grade security and DLP: Tool inputs and outputs are scanned for sensitive data, with configurable rules to block, redact, or mask data
- Real-time observability and auditability: Merge provides activity logging for every tool call with fully searchable logs to support debugging and audits
- Evaluation before production: Tools can be validated against expected outcomes prior to deployment using the Evaluation Suite
Can I set custom security rules for Basecamp tool calls in Merge Agent Handler?
Yes. Merge Agent Handler includes a security gateway with Data Loss Protection (DLP) that allows default and custom rules to scan tool inputs and outputs and take actions such as blocking or redacting sensitive data.
Here are some examples:
- Block Social Security numbers from being posted into Basecamp (in messages, comments, or to-do descriptions)
- Block credit card numbers from being posted into Basecamp (in any text fields an agent can write)
- Redact email addresses and phone numbers before writing anything into Basecamp, so the action can proceed but contact info is removed from what gets sent
- Block any attempt to paste secrets into Basecamp (API keys, bearer tokens, passwords, or anything that looks like credentials)
- Block uploading sensitive files into Basecamp based on filename patterns (for example, “passport,” “w2,” “bank_statement,” “ssn”)
How can I start using Merge Agent Handler’s Basecamp MCP server?
You can take these steps:
1. Sign up for Merge Agent Handler (create a free account).
2. Create a Tool Pack (this is where you bundle the tools you want your agent to have).
3. Add the Basecamp connector to that Tool Pack.
4. Create a Registered User (this represents the identity that will authenticate and perform Basecamp actions through your agent).
5. Authenticate Basecamp for that Registered User (so tool calls have the right permissions).
6. Save the Tool Pack, then copy the MCP server URL from the Tool Pack setup for that Registered User.
7. Paste that MCP server URL into your agent client or IDE MCP configuration (for example, Cursor, Windsurf, or Claude Desktop), then refresh/restart the client.
8. Run a simple test prompt to confirm the Basecamp tools are available and generating logs (check the Logs page to verify tool calls are being captured).
Can employees use Merge Agent Handler to connect their AI tools to Basecamp?
Yes, Agent Handler for Employees lets your employees connect Claude, ChatGPT, Microsoft Copilot, Cursor, and other MCP-compatible AI tools to Basecamp without bypassing IT governance.
Instead of setting up direct connections with personal credentials that IT can't monitor or revoke, each employee authenticates through Agent Handler and gets individual credentials tied to their identity.
IT also provisions access by role or group via SCIM. A project manager, for example, gets Basecamp access to track milestones and to-dos, Slack to coordinate with the team, and Google Drive to manage project assets; while a software engineer gets Basecamp access to monitor task assignments, GitHub to link code changes to project discussions, and Jira to track bugs alongside Basecamp deliverables.
Every tool call an employee's AI makes to Basecamp is also inspected against your DLP rules and logged to a searchable audit trail, giving security teams full visibility into what data was accessed and by whom.