Basecamp MCP Server exposes the Complete Basecamp 4 API through the MCP interface, enabling AI agents and automation tools to interact with projects, todos, messages, files, and more in a programmatic and consistent way. It includes auto-lookup to resolve resource IDs, OAuth 2.0 authentication flows, and multiple authentication methods (access tokens passed in arguments, Authorization: Bearer headers, or environment variables). To get started, configure your OAuth integration with Basecamp, set the required environment variables, and deploy the server to your preferred hosting environment (Cloudflare Workers is recommended per the project). Once running, you can call a suite of 59+ tools across project management, todo handling, communication, documents/files, team management, and more. Claude.ai compatibility is highlighted, so you can connect Claude to your MCP server and discover the full toolset directly in the chat interface. Typical usage involves authenticating to obtain an access token, then issuing tool requests such as listing projects, fetching todo lists, creating tasks, posting messages, or parsing Basecamp URLs to auto-discover resource IDs. You can also leverage auto-lookup and URL parsing to minimize manual ID management when automating workflows.

Prerequisites:

• Node.js (recommended LTS) and npm installed on your development machine
• Git for cloning the repository
• Wrangler (for Cloudflare Workers deployment) if you choose Cloudflare hosting

Steps:

1. Clone the repository git clone https://github.com/QusaiiSaleem/basecamp-mcp-server.git cd basecamp-mcp-server

2. Install dependencies npm install

3. Configure Cloudflare Workers deployment (recommended):

   • Copy example Wrangler config and configure account details cp wrangler.toml.example wrangler.toml

     Edit wrangler.toml with your Cloudflare account credentials

   • If you don’t have wrangler installed, install it: npm install -g wrangler

4. Set up OAuth environment variables (Basecamp integration):

   • Create and configure the Basecamp OAuth credentials via the Basecamp developer portal
   • Store secrets for your deployment: wrangler secret put BASECAMP_CLIENT_ID wrangler secret put BASECAMP_CLIENT_SECRET wrangler secret put BASECAMP_ACCOUNT_ID

5. Run or deploy the MCP server:

   • Local development (if supported by the project): npm run start
   • Deploy to Cloudflare Workers: npm run deploy

6. Retrieve an access token: visit the setup URL provided by your deployment (e.g., https://your-worker.workers.dev/setup) and complete the OAuth flow to obtain an access token. Use this token for subsequent requests, or configure BASECAMP_ACCESS_TOKEN accordingly.

7. (Optional) Configure Claude.ai or other clients:

   • In Claude.ai, add a remote MCP server with the endpoint URL and Bearer token authentication as described in the integration guide.

Tips and common considerations:

• This MCP server supports OAuth 2.0 with a simplified deployment flow (no KV storage required in v7.5+).
• Ensure BASECAMP_ACCOUNT_ID and client credentials are kept secure; use environment variables or Cloudflare Secrets in production.
• If you rely on auto-lookup, ensure resource scraping permissions are aligned with your Basecamp account to avoid 404s.
• When deploying to Cloudflare Workers, keep an eye on cold starts and latency; edge deployment helps with sub-100ms responses globally.
• The server exposes 59+ tools across Basecamp capabilities; review the tool reference section to identify the exact tool names you can call (e.g., get_todo_lists, create_todo, add_comment_to_recording, parse_basecamp_url).
• For Claude.ai integration, you’ll typically configure a Bearer token in Claude’s remote MCP settings and point to your worker URL; verify tools appear and test with sample phrases.
• If you update OAuth scopes or reconfigure Basecamp app settings, re-authenticate to refresh access tokens.