Can I use Basecamp 3 as a CLI?

Yes. KosmoKrator exposes a Basecamp 3 CLI through kosmo integrations:call and the provider shortcut command. Commands can return JSON for scripts, CI, and coding agents.

Can I expose Basecamp 3 through MCP?

Yes. The KosmoKrator MCP gateway can expose selected Basecamp 3 tools to clients such as Claude Code, Cursor, Codex, and other MCP-compatible tools.

Where are Basecamp 3 credentials stored?

Basecamp 3 credentials are configured in KosmoKrator's local integration settings and reused by CLI, Lua, and MCP gateway surfaces.

Can I deny write access for Basecamp 3 MCP tools?

Yes. Start the gateway with --write=deny for read-only clients, or use ask/allow only for trusted workspaces.

productivity

Basecamp 3 CLI for Cron Jobs

Use the Basecamp 3 CLI for cron jobs with headless JSON commands, schema discovery, credentials, and permission controls.

7 functions 6 read 1 write Manual OAuth token auth

Submit Basecamp 3 feedback View package source

Basecamp 3 CLI for Cron Jobs

Schedule repeatable integration workflows from cron while keeping credentials in KosmoKrator config.

Use the headless CLI from cron when an operation should run without an interactive agent session. The Basecamp 3 CLI uses the same integration registry as the TUI, Lua runtime, and MCP gateway, but returns predictable command output for automation.

Command Shape

# Basecamp 3 CLI for Cron Jobs
kosmokrator integrations:configure basecamp --set access_token="$BASECAMP_ACCESS_TOKEN" --set account_id="$BASECAMP_ACCOUNT_ID" --enable --read allow --write ask --json
kosmo integrations:call basecamp.basecamp_list_projects '{}' --json

Discovery Before Execution

Agents and scripts can inspect Basecamp 3 docs and schemas before choosing a function.

kosmo integrations:docs basecamp --json
kosmo integrations:docs basecamp.basecamp_list_projects --json
kosmo integrations:schema basecamp.basecamp_list_projects --json
kosmo integrations:search "Basecamp 3" --json
kosmo integrations:list --json

Useful Basecamp 3 CLI Functions

Function	Type	Parameters	Description
`basecamp.basecamp_list_projects`	Read	none	List all Basecamp projects visible to the authenticated user. Returns project names, IDs, descriptions, and creation dates.
`basecamp.basecamp_get_project`	Read	project_id	Get details for a single Basecamp project by ID. Returns the project name, description, members, and metadata.
`basecamp.basecamp_list_todos`	Read	project_id, todoset_id, todolist_id	List to-dos in a Basecamp to-do list. Requires the project ID, to-do set ID, and to-do list ID. Returns to-do items with their content, completion status, assignees, and due dates.
`basecamp.basecamp_create_todo`	Write	project_id, todoset_id, todolist_id, content, description, due_on, assignee_ids	Create a new to-do in a Basecamp to-do list. Specify the project, to-do set, to-do list, and to-do text. Optionally include a description, due date, and assignee IDs.
`basecamp.basecamp_list_messages`	Read	project_id	List messages (message board posts) for a Basecamp project. Returns message subjects, content excerpts, authors, and timestamps.
`basecamp.basecamp_get_message`	Read	project_id, message_id	Get a single message from a Basecamp project by ID. Returns the full message subject, content, author, and metadata.
`basecamp.basecamp_get_current_user`	Read	none	Get the profile of the currently authenticated Basecamp user. Returns name, email, avatar, and account details.

Automation Notes

Use --json for machine-readable output.
Keep credentials out of argv by using environment variables or stored KosmoKrator configuration.
Configure read/write policy before unattended runs; use --force only for trusted automation.
Use the MCP gateway instead when the agent needs dynamic tool discovery inside a conversation.

Related Basecamp 3 CLI Pages

CI Basecamp 3 CLI for CI. Shell Scripts Basecamp 3 CLI for shell scripts. Headless Automation Basecamp 3 CLI for headless automation. Coding Agents Basecamp 3 CLI for coding agents.