list_wikis
List all wikis you have access to
LABSCO SUMMARY
list_learnings is the tool that tells you whether the reviewer is actually adapting to your codebase.
Every AI review tool claims to learn your conventions. Exposing those learnings as readable objects makes the claim checkable — you can see what it thinks your team's rules are and whether they are right. Combined with update_issue_status taking feedback, the loop is visible rather than implied. resolve_github_user_contacts is the practical one: turning a username into a Slack mention is exactly the small friction that stops a finding reaching the person who can fix it.
What it is
Cubic's endpoint over their AI code review. Eleven tools spanning scans and their issues, the repository wiki, and the reviewer's accumulated learnings.
What you get
- list_scans and get_scan — repository scan summaries, then aggregated issues with filters and paging
- get_issue and get_pr_issues — one issue with its full code context, or everything published for a pull request
- update_issue_status — triage an issue, with optional feedback
- list_learnings and get_learning — what the AI reviewer has learned about this repository
- list_wikis, list_wiki_pages, get_wiki_page — the repository wiki
- resolve_github_user_contacts — GitHub usernames to email and Slack mentions
Requirements
A cubic account with access to at least one repository — membership of that repo's installation. OAuth with dynamic client registration; a legacy API key still works during migration. TLS 1.2+ in transit, AES-256 at rest, and least-privilege GitHub App scopes documented per scope.
Setup effort
Paste a URL, then authorize — add the endpoint to your client, then approve the OAuth consent screen
USE CASES
01
Working through review findings
Pull the issues for the pull request with their code context, then triage each with feedback.
02
Checking what the reviewer believes
Read its learnings for the repository and correct the ones that are wrong.
03
Getting a finding to the right person
Resolve the GitHub username to a Slack mention rather than guessing at handles.
04
Reading the project's own docs
The repository wiki is reachable through the same connection.
11 tools
Listed in project docs. Your client may show a different list.
list_wiki_pages
List all available wiki pages for a repository
get_wiki_page
Retrieve the content of a specific wiki page
list_scans
List repository scan summaries
get_scan
List aggregated scan issues with filters and pagination
resolve_github_user_contacts
Resolve GitHub usernames to email and Slack mentions
get_issue
Get full issue details including code context
update_issue_status
Update a scan issue triage status with optional feedback
list_learnings
List AI review learnings for a repository
get_learning
Get full details of a specific learning
get_pr_issues
Get all published issues for a pull request
BEFORE YOU INSTALL
What to know first
Tools you get
11 tools named in the project's documentation.
Requires
- an MCP client that can reach a remote endpoint
- OAuth (dynamic client registration; auth server = Supabase); legacy API key during migration
INSTALLATION
Connect your client
Add the endpoint to your client, then approve the OAuth consent screen.
Server setup
ENDPOINT URL
https://www.cubic.dev/api/mcpRequirements
- OAuth (dynamic client registration; auth server = Supabase); legacy API key during migration
