Basecamp MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_projectsB | Get all Basecamp projects |
| get_projectC | Get details for a specific project |
| search_basecampC | Search across Basecamp projects, todos, and messages |
| global_searchC | Search projects, todos and campfire messages across all projects |
| get_todolistsC | Get todo lists for a project |
| get_todosC | Get todos from a todo list |
| get_card_tableC | Get the card table details for a project |
| get_columnsC | Get all columns in a card table |
| get_cardsC | Get all cards in a column |
| create_cardC | Create a new card in a column |
| create_columnC | Create a new column in a card table |
| update_columnC | Update a column title |
| move_columnC | Move a column to a new position |
| update_column_colorC | Update a column color |
| get_cardC | Get details for a specific card |
| update_cardC | Update a card |
| move_cardC | Move a card to a new column |
| complete_cardC | Mark a card as complete |
| get_card_stepsC | Get all steps (sub-tasks) for a card |
| create_card_stepC | Create a new step (sub-task) for a card |
| complete_card_stepC | Mark a card step as complete |
| get_campfire_linesB | Get recent messages from a Basecamp campfire (chat room) |
| get_commentsC | Get comments for a Basecamp item |
| get_documentsC | List documents in a vault |
| create_documentC | Create a document in a vault |
| update_documentC | Update a document |
| trash_documentC | Move a document to trash |
| get_uploadsC | List uploads in a project or vault |
| get_webhooksC | List webhooks for a project |
| create_webhookC | Create a webhook |
| delete_webhookC | Delete a webhook |
| get_daily_check_insC | Get project's daily checking questionnaire |
| get_question_answersC | Get answers on daily check-in question |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 33 tools
Most tools have distinct purposes targeting specific Basecamp resources (e.g., cards, columns, documents, webhooks), but there is some overlap between 'global_search' and 'search_basecamp' which could cause confusion as both appear to handle search functionality across projects. Otherwise, the tool set is well-differentiated.
Tool names follow a highly consistent verb_noun pattern throughout (e.g., create_card, get_cards, update_column). All tools use snake_case with clear, descriptive verbs, making the naming predictable and easy to understand.
With 33 tools, the count is borderline high for a project management server, potentially overwhelming for agents. While Basecamp has many features, this many tools might indicate over-fragmentation (e.g., separate tools for similar operations like get_card and get_cards).
The tool set provides comprehensive coverage for Basecamp's domain, including CRUD operations for cards, columns, documents, webhooks, and search, along with specific features like campfire messages and daily check-ins. No obvious gaps are present; agents can perform full lifecycle management.