3,400+ MCP servers ready to use
Vinkius

Basecamp MCP Server for Claude DesktopGive Claude Desktop instant access to 17 tools to Complete Todo, Create Comment, Create Project, and more

Built by Vinkius GDPR 17 Tools IDE

Claude Desktop is Anthropic's native application for interacting with Claude AI models on macOS and Windows. It was the first consumer application to ship with built-in MCP support, making it the reference implementation for the Model Context Protocol standard.

Ask AI about this App Connector for Claude Desktop

The Basecamp app connector for Claude Desktop is a standout in the Productivity category — giving your AI agent 17 tools to work with, ready to go from day one.

Vinkius delivers Streamable HTTP and SSE to any MCP client

RecommendedModern Approach — Zero Configuration

Vinkius Desktop App

The modern way to manage MCP Servers — no config files, no terminal commands. Install Basecamp and 3,400+ MCP Servers from a single visual interface.

Vinkius Desktop InterfaceVinkius Desktop InterfaceVinkius Desktop InterfaceVinkius Desktop Interface
Download Free Open SourceNo signup required
Classic Setup·json
{
  "mcpServers": {
    "basecamp-alternative": {
      // Your Vinkius token. get it at cloud.vinkius.com
      "url": "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
    }
  }
}
Basecamp
Fully ManagedVinkius Servers
60%Token savings
High SecurityEnterprise-grade
IAMAccess control
EU AI ActCompliant
DLPData protection
V8 IsolateSandboxed
Ed25519Audit chain
<40msKill switch
Stream every event to Splunk, Datadog, or your own webhook in real-time

* Every MCP server runs on Vinkius-managed infrastructure inside AWS - a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts optimized for native MCP execution. See our infrastructure

About Basecamp MCP Server

Connect your Basecamp account to any AI agent and take full control of your project management, team collaboration, and task tracking through natural conversation.

Claude Desktop is the definitive way to connect Basecamp to your AI workflow. Add Vinkius Edge URL to your config, restart the app, and Claude immediately exposes all 17 tools in the chat interface. ask a question, Claude calls the right tool, and you see the answer. Zero code, zero context switching.

What you can do

  • Project Management — Create, list, update, and inspect projects with full dock metadata (message boards, to-do sets, schedules).
  • To-Do CRUD — Create, update, complete, and uncomplete to-do items across any to-do list, with assignees and due dates.
  • Team Visibility — List all people in your account or within a specific project to find assignee IDs and check roles.
  • Message Boards — Read messages posted on project boards to stay aligned with team decisions and announcements.
  • Comments — Add comments to any recording (to-do, message, document) to provide feedback or status updates.
  • Profile Verification — Retrieve your authenticated profile to confirm connectivity and check access permissions.

The Basecamp MCP Server exposes 17 tools through the Vinkius. Connect it to Claude Desktop in under two minutes — no API keys to rotate, no infrastructure to provision, no vendor lock-in. Your configuration, your data, your control.

All 17 Basecamp tools available for Claude Desktop

When Claude Desktop connects to Basecamp through Vinkius, your AI agent gets direct access to every tool listed below — spanning task-tracking, team-communication, file-sharing, and more. Every call is secured with network, filesystem, subprocess, and code evaluation entitlements inside a sandboxed runtime. Beyond a simple connection, you get a full AI Gateway with real-time visibility into agent activity, enterprise governance, and optimized token usage.

complete_todo

This is separate from archiving or trashing — a completed to-do remains active but is marked as done. Use uncomplete_todo to reverse this action. Mark a to-do item as completed

create_comment

). The recording_id is the unique numeric ID of the item you want to comment on. The content must be provided as rich text (HTML). All subscribers to the recording will be notified of the new comment. Add a comment to any Basecamp recording

create_project

The project will be initialized with default tools (message board, to-do set, schedule, etc.) enabled via its dock. Returns the newly created project with its numeric ID and dock tool IDs. Create a new project in Basecamp

create_todo

Requires the todolist_id and the content (title) of the to-do. Optionally include a rich text description, assignee IDs (array of person IDs), and a due date in YYYY-MM-DD format. The to-do will be created as pending (not completed). Create a new to-do item in a to-do list

get_message

Get full details of a specific message

get_my_profile

Use this to verify connectivity or identify the current operator. Get the authenticated Basecamp user profile

get_person

Use this to look up details about a team member or assignee. Get full details of a specific person

get_project

). The dock contains the IDs you need to access tools like the to-do set or message board. Get full details of a specific project

get_todo

Get full details of a specific to-do item

list_messages

Each message includes title, content preview, author, category, and creation date. You need the message_board_id which can be found via the project dock. List all messages on a project message board

list_people

Useful for finding assignee IDs before creating or updating to-dos. List all people in the Basecamp account

list_project_people

Returns names, emails, and roles. Useful for checking team composition before assigning tasks. List all people assigned to a specific project

list_projects

Optionally filter by status: "active" (default), "archived", or "trashed". Each project includes its name, description, purpose, dock (enabled tools), and bookmark status. List all projects in Basecamp

list_todos

By default returns only pending (not completed) items. Set completed to true to see completed items instead. Each to-do includes its content, assignees, due date, completion status, and comments count. You need the todolist_id which can be found via the project dock. List all to-dos in a specific to-do list

uncomplete_todo

Use this when a previously completed task needs to be reopened or reworked. Mark a completed to-do item as pending again

update_project

At least one of name or description must be provided. Returns the updated project details including the full dock listing. Update an existing project in Basecamp

update_todo

At least one field must be provided. Does not affect completion status — use the complete_todo or uncomplete_todo tools for that. Update an existing to-do item in Basecamp

Connect Basecamp to Claude Desktop via MCP

Follow these steps to wire Basecamp into Claude Desktop. The entire setup takes under two minutes — your credentials stay safe behind the Vinkius.

01

Open Claude Desktop Settings

Go to Settings → Developer → Edit Config to open claude_desktop_config.json
02

Add the MCP Server

Paste the configuration above into the mcpServers section
03

Restart Claude Desktop

Close and reopen Claude Desktop to load the new server
04

Start using Basecamp

Look for the 🔌 icon in the chat. your 17 tools are now available

Why Use Claude Desktop with the Basecamp MCP Server

Claude Desktop by Anthropic provides unique advantages when paired with Basecamp through the Model Context Protocol.

01

Claude Desktop is the reference MCP client. it was designed alongside the protocol itself, ensuring the most complete and stable MCP implementation available

02

Zero-code configuration: add a server URL to a JSON file and Claude instantly discovers and exposes all available tools in the chat interface

03

Claude's extended thinking capability lets it reason through multi-step tool usage, chaining multiple API calls to answer complex questions

04

Enterprise-grade security with local config storage. your tokens never leave your machine, and connections go directly to Vinkius Edge network

Basecamp + Claude Desktop Use Cases

Practical scenarios where Claude Desktop combined with the Basecamp MCP Server delivers measurable value.

01

Interactive data exploration: ask Claude to query DNS records, look up WHOIS data, and cross-reference results in a single conversation

02

Ad-hoc security audits: type a domain name and let Claude enumerate subdomains, check DNS history, and flag configuration anomalies. all through natural language

03

Executive briefings: generate comprehensive domain intelligence reports by asking Claude to compile findings into a formatted summary

04

Learning and training: new team members can explore API capabilities conversationally without needing to read documentation

Example Prompts for Basecamp in Claude Desktop

Ready-to-use prompts you can give your Claude Desktop agent to start working with Basecamp immediately.

01

"List all my active projects in Basecamp."

02

"Create a new to-do 'Review design mockups' in list 592001 and assign it to person 10293 with a due date of 2026-05-15."

03

"Show me the latest messages on the message board of project 48291034."

Troubleshooting Basecamp MCP Server with Claude Desktop

Common issues when connecting Basecamp to Claude Desktop through the Vinkius, and how to resolve them.

01

Server not appearing after restart

Ensure the JSON is valid (no trailing commas). Check the file path: ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\\Claude\\ (Windows).
02

Authentication error

Verify your Vinkius token is correct. Go to cloud.vinkius.com to regenerate it if needed.
03

Tools not showing in chat

Click the 🔌 icon at the bottom of the chat input. If it shows 0 tools, the server may still be connecting. wait a few seconds.

Basecamp + Claude Desktop FAQ

Common questions about integrating Basecamp MCP Server with Claude Desktop.

01

How does Claude Desktop discover MCP tools?

When Claude Desktop starts, it reads the claude_desktop_config.json file and connects to each configured MCP server. It calls the tools/list endpoint to fetch the schema for every available tool, then surfaces them as clickable options in the chat interface via the 🔌 icon.
02

What happens if the MCP server is temporarily unavailable?

Claude Desktop handles disconnections gracefully. if the server is unreachable at startup, the tools simply won't appear. Once the server becomes available again, restarting Claude Desktop will re-establish the connection. There is no timeout penalty or error loop.
03

Can I connect multiple MCP servers simultaneously?

Yes. You can add as many servers as you need in the mcpServers section of the config file. Each server appears as a separate tool provider, and Claude can use tools from multiple servers in a single conversation turn.
04

Is there a limit on the number of tools per server?

Claude Desktop can handle hundreds of tools per server. However, for optimal LLM performance, Vinkius servers are designed to expose focused, well-documented tool sets rather than overwhelming the model with too many options.
05

Does Claude Desktop support Streamable HTTP transport?

Yes. Claude Desktop supports both SSE (Server-Sent Events) and the newer Streamable HTTP transport that Vinkius uses. Simply provide the server URL. Claude auto-negotiates the transport protocol.