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 |
|---|---|
| list_projectsB | Returns id, name, status, timestamps, purpose, clients_enabled, bookmarked, and enabled dock tools. Supports pagination and JSON output. |
| get_todosetC | Resolves the project's to-do set by reading the dock; can include lists. |
| list_todolistsC | Resolves the project's to-do set from dock, then lists its to-do lists. |
| create_todoC | Create a new to-do in the given list. |
| list_messagesC | Resolves the project's message board from the dock, then lists messages with pagination. Optionally include full content. |
| get_messageB | Fetch a single message by ID; render body as markdown/html/text, or return raw JSON. |
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 6 tools
The tools are mostly distinct, with clear separation between to-do, message, and project operations. However, 'get_todoset' and 'list_todolists' could be slightly confusing as both relate to to-do lists, though 'get_todoset' focuses on resolving the set while 'list_todolists' lists the lists within it, which helps mitigate overlap.
All tool names follow a consistent verb_noun pattern (e.g., create_todo, get_message, list_projects), using snake_case throughout. This predictability makes it easy for agents to understand and navigate the tool set without confusion.
With 6 tools, the count is reasonable for a Basecamp server, covering core operations like creating to-dos and listing projects. It's slightly lean but well-scoped, though it could benefit from additional tools for updates or deletions to enhance completeness.
The tools cover basic read and create operations for to-dos, messages, and projects, but there are notable gaps. For example, there are no update or delete tools for to-dos or messages, and operations like creating messages or projects are missing, which could limit agent workflows in a CRUD context.