MCP server that wraps the basecamp CLI.
Project description
basecamp-cli-mcp
A Model Context Protocol (MCP) server that wraps the basecamp
CLI. Every non-shortcut CLI action (projects list, todos create, cards update, etc.) is
exposed as an MCP tool, so MCP-compatible clients (Claude Code, Claude Desktop, etc.) can
drive Basecamp directly.
Requirements
- Python ≥ 3.11
- The
basecampCLI onPATH, already authenticated (basecamp setup) — see First-time setup below to do both in one command uvfor the recommended install
First-time setup
If you don't have the basecamp CLI installed yet:
uvx basecamp-cli-mcp setup
This checks for the basecamp binary, runs the official installer (curl -fsSL https://basecamp.com/install-cli | bash) after a y/N prompt if it's missing, then runs basecamp setup to walk you through OAuth.
On macOS, after auth completes it offers to:
- Add
basecampto yourclaude_desktop_config.json(with a timestamped backup of any existing file). - Restart Claude Desktop.
Both steps prompt y/N. macOS and Linux only for the install/auth — on Windows the command prints the PowerShell installer and exits. The Claude Desktop step is macOS-only.
Run
The fastest way — no install step at all:
uvx basecamp-cli-mcp
uvx resolves the package, runs it in an ephemeral isolated env, and exec's it on stdin/stdout.
To install permanently:
uv tool install basecamp-cli-mcp
basecamp-cli-mcp
Add to Claude Code
claude mcp add basecamp -- uvx basecamp-cli-mcp
Add to Claude Desktop (claude_desktop_config.json)
{
"mcpServers": {
"basecamp": {
"command": "uvx",
"args": ["basecamp-cli-mcp"]
}
}
}
If uvx isn't on Desktop's PATH (it strips most of your shell PATH), use the absolute path — which uvx from your shell.
Filtering tools
By default the server exposes all 250+ tools. Most agents only need a handful, and a smaller
catalog speeds up tool selection. Filter with --include / --exclude (fnmatch globs against
tool names; both flags repeatable):
basecamp-cli-mcp --include 'cards_*' --include 'todos_*'
basecamp-cli-mcp --include '*' --exclude 'webhooks_*' --exclude 'templates_*'
Register multiple profiles in claude_desktop_config.json and turn them on per task:
{
"mcpServers": {
"basecamp-cards": {
"command": "uvx",
"args": ["basecamp-cli-mcp", "--include", "cards_*", "--include", "projects_list"]
},
"basecamp-todos": {
"command": "uvx",
"args": ["basecamp-cli-mcp", "--include", "todos_*", "--include", "projects_list"]
},
"basecamp-full": {
"command": "uvx",
"args": ["basecamp-cli-mcp"]
}
}
}
BASECAMP_BIN
If the basecamp CLI isn't on the spawned process's PATH (a real risk under Claude Desktop), set:
"env": { "BASECAMP_BIN": "/absolute/path/to/basecamp" }
How it works
Tool schemas are pre-generated and committed to src/basecamp_cli_mcp/data/tools.json (shipped
inside the wheel as package data). At runtime the server loads that file and registers one MCP
tool per entry. Each tool:
- Builds
argvfrom positional arguments and flags defined in the schema. - Shells out:
basecamp <group> <action> <args...> --json. - Returns the parsed
datafield from the CLI's{ok, data}envelope to the MCP client.
Shortcut commands (todo, done, card, comment, etc.) are intentionally excluded — their
underlying actions (todos_create, cards_create, …) are already exposed.
Regenerating tool schemas
After upgrading the basecamp CLI:
uv run basecamp-cli-mcp generate
Review the diff in src/basecamp_cli_mcp/data/tools.json and commit. The generator reads
basecamp commands --json and parses basecamp <group> <action> --help for each action.
Development
uv sync
uv run pytest
uv build # wheel + sdist into dist/
Layout:
src/basecamp_cli_mcp/server.py— wires up the MCP server fromdata/tools.jsonsrc/basecamp_cli_mcp/runner.py— builds argv and shells outsrc/basecamp_cli_mcp/generator.py— regeneratesdata/tools.jsonsrc/basecamp_cli_mcp/help_parser.py— parses--helptext into a schemasrc/basecamp_cli_mcp/cli.py— entrypoint (basecamp-cli-mcp)src/basecamp_cli_mcp/data/tools.json— generated tool schemas (committed)
Project details
Download files
Download the file for your platform. If you're not sure which to choose, learn more about installing packages.
Source Distribution
Built Distribution
Filter files by name, interpreter, ABI, and platform.
If you're not sure about the file name format, learn more about wheel file names.
Copy a direct link to the current filters
File details
Details for the file basecamp_cli_mcp-0.6.0.tar.gz.
File metadata
- Download URL: basecamp_cli_mcp-0.6.0.tar.gz
- Upload date:
- Size: 35.3 kB
- Tags: Source
- Uploaded using Trusted Publishing? No
- Uploaded via: uv/0.10.12 {"installer":{"name":"uv","version":"0.10.12","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"macOS","version":null,"id":null,"libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":null}
File hashes
| Algorithm | Hash digest | |
|---|---|---|
| SHA256 |
c8dbb521fbd3215413764c0ad890870d50b5339919ca99344267255e9fd23efb
|
|
| MD5 |
2a727049749fa6ec4857a448289422c0
|
|
| BLAKE2b-256 |
e8ff8596f24b69e8a8cae26007868a2f315b867951542b04a30f5cb32c1c3044
|
File details
Details for the file basecamp_cli_mcp-0.6.0-py3-none-any.whl.
File metadata
- Download URL: basecamp_cli_mcp-0.6.0-py3-none-any.whl
- Upload date:
- Size: 35.8 kB
- Tags: Python 3
- Uploaded using Trusted Publishing? No
- Uploaded via: uv/0.10.12 {"installer":{"name":"uv","version":"0.10.12","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"macOS","version":null,"id":null,"libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":null}
File hashes
| Algorithm | Hash digest | |
|---|---|---|
| SHA256 |
0f9231bde9f85a11069c3105aad558a403f77ccdb52b465888da2ee34e710072
|
|
| MD5 |
f8b89b2e0638ee9bca659a4e35818a2e
|
|
| BLAKE2b-256 |
3608b1abca47f05d7a2ddf8643d144e27475fa28b52295066a008520f229c0e0
|