dyve / dyve/basecamp-cli-mcp

Backlog: CLI commands with no dedicated tool

Open
#8 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
JavaScript
Stars
0
Forks
0
Avg merge
4m
Merged PRs (30d)
5

Description

Standing list of Basecamp CLI capabilities reachable today only through basecamp_run. Kept as an issue so it survives outside CHANGELOG.md, where it has drifted once already (it still listed files versions / files replace as unwired after #4 landed them).

Not a commitment to build any of these. AGENTS.md's scope policy means each is an explicit decision.

  • files uploads create — creating an upload; see #7
  • cards wormholes list/create/update/delete — needed to discover valid to_wormhole targets for move_card, which already accepts one
  • cards list --all-projects — account-wide Kanban listing, with its own assignee / due / unassigned filters
  • todos list --all-projects, --due <with|without|overdue>, --unassigned, --no-due-date — account-wide server-side filters, currently approximated client-side
  • reports schedule --start / --end — custom date window; get_schedule is fixed to "upcoming"
  • comments list --all-projects, comments thread
  • files list --all-projects --kind --person
  • notifications bubbleupslist_notifications returns only bubble_ups_count, never the items
  • top-level assign / unassign shortcuts (alias-shaped; see #6 before using them)
Also intentionally absent

delete_project is excluded by design — a destructive action deliberately kept out of the tool surface. Not a gap; do not add it.

Current as of CLI v0.9.1.

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reading AGENTS.md for the scope policy, then review the listed capabilities and referenced issues (#4, #6, and #7). The issue is a backlog rather than one defined change, so each command needs an explicit decision and its own scope; completion cannot be established for the list as a whole.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript
Domain
cli
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Quiet
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.