MCP tool reference
Connection, repository setup, proposal status, traveler memory, reflection, and watch controls.
For client-specific connection instructions and the server address, use Connect your assistant. Sign in to Alcove through the browser when prompted. MCP tools use the signed-in account's organization and permissions.
Connection and setup
| Tool | Purpose |
|---|---|
connect_github_app | Return a GitHub authorization link for the user to open and select repositories. |
get_github_connection | Discover the connected installation and accessible repositories, with the next setup step. |
get_repository_setup | Inspect a connected repository's privacy, required file presence, review setting, and observed protection requirements. |
set_review_enabled | Enable or disable future reviews for one connected repository. Requires an organization owner or admin. |
get_proposal_status | Inspect a pull request's current revision, expected checks, and acceptance state. |
After GitHub authorization, discover the connection again. Pass the connected repository ID returned by Alcove into setup and proposal tools; do not substitute a GitHub numeric repository ID.
Required file presence is not schema validation. Read the repository's checks for that. Protection inspection can report unknown or unavailable results, including GitHub plan restrictions. Observed check requirements do not establish independent human approval or the absence of bypass permissions.
Review enablement applies to future eligible events and does not queue a review immediately. Existing billing and usage limits still apply. Enabling requires an active installation; disabling is allowed when disconnected.
Proposal status
Check the current proposal before presenting its status or requesting acceptance. Missing, pending, unreadable, skipped, or stale checks are not passing checks. If the proposal changes during inspection, refresh the result.
A proposal merged into another proposal is not accepted into the main plan. A historical merge also does not prove that its contents remain the current plan. Check status does not certify that review conversations are resolved or that the traveler has approved the change.
These tools inspect GitHub; they do not create repositories, edit itinerary files, open proposals, approve them, or merge them. Those actions require the client's GitHub tools and the traveler's authorization.
Traveler profiles and reflection
Use the subject tools to list, create, and update the traveler profiles the user chooses to store. Trip repositories reference their opaque IDs.
Reflection proposes lessons from a post-trip conversation. Ask the user to approve or reject each lesson; only approved lessons enter traveler memory. See Traveler memory for the workflow.
Watch
Hosted watch controls operate on a linked repository and require an eligible plan:
get_watch_status— enablement, cadence, last run and issue.enable_watch/pause_watch— enable or pause the schedule.run_watch_now— queue one pass that opens or updates a watch issue.
Watch targets live in the repository's optional watch.yaml. Watch does not silently edit the accepted trip.