SCM Integration
Caboose auto-detects your source control platform from the git remote URL when a session starts. If a GitHub or GitLab remote is found, platform-specific tools are registered automatically — no configuration required.
What gets registered
Section titled “What gets registered”GitHub
Section titled “GitHub”| Tool | Description |
|---|---|
list_issues | List open issues, optionally filtered by label or assignee |
get_issue | Fetch a single issue with comments |
list_pull_requests | List open PRs with status and review info |
get_pull_request | Fetch a PR with diff and review comments |
get_file_contents | Read any file from the repo at any ref |
search_code | Search across the repository codebase |
GitLab
Section titled “GitLab”Same set of tools scoped to GitLab’s API: issues, merge requests, file contents, and repository search.
Authentication
Section titled “Authentication”SCM tools require an API token:
- GitHub: set
GITHUB_TOKENenvironment variable, or configure it via/connect github - GitLab: set
GITLAB_TOKENenvironment variable, or configure it via/connect gitlab
Tokens are stored in your system keychain and never written to config files.
MCP presets
Section titled “MCP presets”The GitHub and GitLab integrations are backed by MCP servers. You can toggle them on or off from /settings without affecting the auto-detected tools — the MCP presets add additional capabilities on top of the built-in integration.
Example usage
Section titled “Example usage”Once connected, you can ask Caboose to work with your repo directly:
What open issues are labeled "bug"?Summarize the changes in PR #142.Find all files that reference the UserAuth class.Caboose will call the appropriate SCM tools and incorporate the results into its response.