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

ToolWhat it does
get_startedwhere the organization stands, its sample run and the next steps
add_sample_runadds the sample run, or returns the one there is
list_projectsprojects of the organization with their slugs
upsert_projectcreates 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_runsshared 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_summaryone 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_itemsthe pages of a stack step with their status and failing criteria
get_step_assetsthe newest capture of every step of a scenario at stable URLs (Business); state picks a step state
get_step_recordinga step's video and trace; state picks a step state
get_criteria_verdictsreviewers' verdicts on manual or overridden criteria
get_review_queuewhat a person still has to decide in a run, and the review link to pass on
decide_stepthe agent's own approve or return on a step; marked as an agent's, never counted as a person's
revoke_carried_approvaltakes back an approval carried over to a step that should be looked at again
get_signoff_recordthe signed acceptance record of an accepted run (Business)
get_evidencethe 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_healththe 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_aggregatehealth 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_diffper 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_findingsthe 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_checkturns 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_stepswhich steps of a scenario the changed files reach, and why
list_notificationsthe token owner's inbox

Feedback and issues

ToolWhat it does
get_feedbackthe run's verdict, approved steps, open returns and comments
list_commentsopen threads across the organization, with replies, pins and drawn regions
add_commenta comment on a step, a run or a whole flow, or a reply
resolve_commentcloses a thread with a note on what changed
reopen_comment, edit_comment, delete_commentreopen a thread; edit or delete your own comment
get_findingsexperimental triage findings of a run (the kind of problem on each screen) and the answers people gave
answer_findingmarks a finding right, not a problem, or turned into a comment
get_triage_reporthow 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_regionsregions people drew to leave out of pixel diffs
add_ignore_regionsuggests such a region
create_issuea Jira or Linear issue from a step, with the screenshot, criterion and notes
list_issuesissues created from steps, with their state
list_schedules, run_schedulehosted runs and their page budget; start one now

Design

ToolWhat it does
get_draftwhich revision each step of the shared draft shows, and who changed it
get_stepthe handoff of a step: live files, tokens, page structure, open comments; each capture names its step state and token mode
get_step_specwhat 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_drifthow an implementation run differs from the design reference, in one step state (state)
get_step_historyversions and revisions of a step with their authors
list_step_changessteps that changed between two references or since the previous accepted run
get_references, get_tokensthe design reference and baseline; the project's token set
get_draft_feedbackcomments on the draft
get_version_notes, set_version_notesread or rewrite what changed in a version
publish_version, set_reference, set_step_status, add_draft_commentpublish the draft as a version, set the reference, set a step's status, comment on the draft

Screens, changelog, docs and products

ToolWhat it does
search_screensthe screen library: the newest screenshot of every step, searched by words, project, product, language or status
list_productsthe products you read, with their newest release, docs and readers
get_changeloga product's visual changelog, optionally with the pictures resolved
draft_changelog_entrywhat accepted runs since the last release show differently, as a draft entry with before and after references
resolve_step_imageone step reference (kaloko:<scenario>/<step>) as an image URL, with the step's recording when it plays
get_docsa product's published docs: versions, languages, the sidebar, or one page
docs_checkwhat 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.

Kaloko · latest · 2026-11-21