MCP tools
Kaloko's MCP server lets an agent read runs, feedback, designs, the changelog and docs, and answer reviewers. It is part of the Team plan and up. Capturing, evaluating and uploading stay in the CLI.
Connect
The server is https://kaloko.app/mcp (MCP over Streamable HTTP). Authenticate with an organization API token in the Authorization header; how to create one: Roles and tokens.
claude mcp add --transport http kaloko https://kaloko.app/mcp --header "Authorization: Bearer $KALOKO_TOKEN"
Other agents (Codex, Cursor) take the same URL and header as an HTTP MCP server. A read-only token is enough to read; tools that write need a token with that scope, as noted below. A read:health token (for a dashboard) sees get_health, get_health_aggregate, get_health_diff and list_findings only. Screenshots and files are not sent over MCP: the answers carry their URLs, which the same token can fetch.
list_runs, list_notifications and list_comments answer one page at a time. When more match than limit, the answer has next; call the tool again with cursor set to it. The REST API pages the same lists with ?cursor= and names the next page in the X-Next-Cursor and Link headers.
Runs and review
| Tool | What it does |
|---|---|
get_started | where the organization stands, its sample run and the next steps |
add_sample_run | adds the sample run, or returns the one there is |
list_projects | projects of the organization with their slugs |
upsert_project | creates a project with its name, or renames it (the project's admin), and adds it to a product; like kaloko projects create, rename and sync |
list_runs | shared runs, newest first, filtered by scenario, project, verdict, author, environment, branch, ref (a record the run serves, such as CC-2026-001) or purpose (dry_run, formal, smoke); cursor for the next page |
get_run_summary | one run: statuses per step and language, criteria that need attention with evidence and reasons, screenshot URLs, the canvas link, the flow's lanes and sessions (roles) and each step's lane and session |
get_stack_items | the pages of a stack step with their status and failing criteria |
get_step_assets | the newest capture of every step of a scenario at stable URLs (Business); state picks a step state |
get_step_recording | a step's video and trace; state picks a step state |
get_criteria_verdicts | reviewers' verdicts on manual or overridden criteria |
get_review_queue | what a person still has to decide in a run, and the review link to pass on |
decide_step | the agent's own approve or return on a step; marked as an agent's, never counted as a person's |
revoke_carried_approval | takes back an approval carried over to a step that should be looked at again |
get_signoff_record | the signed acceptance record of an accepted run (Business) |
get_evidence | the evidence of a run or a release for your own documents: acceptance and signing state, criteria as walked with requirement references, results, screenshot hashes, decisions, signatures, audit trail and the trace matrix (Business) |
get_health | the health of a run, the newest run of a scenario, or the trend of a project: findings by severity, pack and step, and what is new or fixed since the previous run; advisory, never a verdict |
get_health_aggregate | health of a run (or a scenario's newest run) counted for a dashboard: per locale, step, check or pack how many results pass, fail or are unsure, the most affected pages, and how many are new or fixed since the previous run; a read:health token may call it |
get_health_diff | per page, locale and check what is new, fixed or still open since the previous run, with the run that first saw it; a read:health token may call it |
list_findings | the open results of a scenario grouped into findings by check, site, locale and step: severity, pages affected, sample pages with their CMS edit link, first and last seen, status (open, acknowledged, ignored with the reason, fixed) and the tracker issue; read-only, a read:health token may call it |
adopt_health_check | turns a health check of a step (HC103) into the acceptance criterion AC103 of the scenario, as is or with new text (Developer / Tester); kaloko health pull writes it into the scenario file |
get_affected_steps | which steps of a scenario the changed files reach, and why |
list_notifications | the token owner's inbox |
Feedback and issues
| Tool | What it does |
|---|---|
get_feedback | the run's verdict, approved steps, open returns and comments |
list_comments | open threads across the organization, with replies, pins and drawn regions |
add_comment | a comment on a step, a run or a whole flow, or a reply |
resolve_comment | closes a thread with a note on what changed |
reopen_comment, edit_comment, delete_comment | reopen a thread; edit or delete your own comment |
get_findings | experimental triage findings of a run (the kind of problem on each screen) and the answers people gave |
answer_finding | marks a finding right, not a problem, or turned into a comment |
get_triage_report | how triage does in your organization: useful findings per kind, how well its probabilities hold, findings turned into comments, time to the first review with and without findings |
list_ignore_regions | regions people drew to leave out of pixel diffs |
add_ignore_region | suggests such a region |
create_issue | a Jira or Linear issue from a step, with the screenshot, criterion and notes |
list_issues | issues created from steps, with their state |
list_schedules, run_schedule | hosted runs and their page budget; start one now |
Design
| Tool | What it does |
|---|---|
get_draft | which revision each step of the shared draft shows, and who changed it |
get_step | the handoff of a step: live files, tokens, page structure, open comments; each capture names its step state and token mode |
get_step_spec | what to build for a step as approved: elements, styles mapped to tokens, states, contrast; state for an empty, error or other step state |
get_step_drift | how an implementation run differs from the design reference, in one step state (state) |
get_step_history | versions and revisions of a step with their authors |
list_step_changes | steps that changed between two references or since the previous accepted run |
get_references, get_tokens | the design reference and baseline; the project's token set |
get_draft_feedback | comments on the draft |
get_version_notes, set_version_notes | read or rewrite what changed in a version |
publish_version, set_reference, set_step_status, add_draft_comment | publish the draft as a version, set the reference, set a step's status, comment on the draft |
Screens, changelog, docs and products
| Tool | What it does |
|---|---|
search_screens | the screen library: the newest screenshot of every step, searched by words, project, product, language or status |
list_products | the products you read, with their newest release, docs and readers |
get_changelog | a product's visual changelog, optionally with the pictures resolved |
draft_changelog_entry | what accepted runs since the last release show differently, as a draft entry with before and after references |
resolve_step_image | one step reference (kaloko:<scenario>/<step>) as an image URL, with the step's recording when it plays |
get_docs | a product's published docs: versions, languages, the sidebar, or one page |
docs_check | what needs attention in the published docs: broken references, stale sections, missing translations |
Errors come back as tool results marked as errors (an unknown run, a missing argument). A token that is not valid gets HTTP 401; an organization below Team is told the MCP server is not in its plan.