Skip to main content

MCP API v2 migration

Short answer

TestChimp Programmatic API 2.0.0 is a major MCP surface change. Prefer the consolidated tools below. Deprecated /api/mcp/* paths still accept the old JSON bodies so @testchimp/cli and the skill can migrate independently.

OpenAPI info.version is now 2.0.0. Auth is still the TestChimp-Api-Key header (and optional bot-id). Do not put projectApiKey or botId on request bodies — those belong on the connection, not each tool schema.

report-agent-action now advertises only nested traceability plus the action fields. Flat copies of the same tracking fields are still accepted server-side for one release. Advertise proto enum names (LOCAL_AGENT, CREATED) only.

Migration table​

Old tool (kebab)New toolParameter mapping
get-eaas-configunchangedadvertised permanently — skill connectivity check. ephemeral-environment action=CONFIG also returns the same public fields
provision-ephemeral-environmentephemeral-environmentaction=PROVISION, wait=false
provision-ephemeral-environment-and-waitephemeral-environmentaction=PROVISION (wait defaults true; maxWaitMinutes)
get-ephemeral-environment-statusephemeral-environmentaction=STATUS, bnsEnvironmentId
destroy-ephemeral-environmentunchangedstill a separate tool so destroy stays annotated
report-dast-findingsreport-scan-findingsscanner=DAST (MCP_SCAN_FINDER_DAST)
report-sast-findingsreport-scan-findingsscanner=SAST
report-deps-findingsreport-scan-findingsscanner=DEPS
report-secrets-findingsreport-scan-findingsscanner=SECRETS
list-workflow-executionsget-workflow-executionssame list filters
get-workflow-executionget-workflow-executionsworkflowExecutionId
get-last-run-workflow-detailget-workflow-executionsworkflowId + latestOnly=true (+ branchName / userId)
get-policyget-policiespolicyFileName
list-policiesget-policiesomit policyFileName (optional workflowId)
list-api-operation-servicesget-api-operationsno identity args
list-api-operationsget-api-operationsrootFilePath / serviceKey
get-api-operation-detailget-api-operationsid, or oasOperationId, or httpMethod+pathTemplate
list-meeting-filter-optionslist-meetingsincludeFilterOptions=true
get-meeting-setlist-meetingsmeetingSetId (expired sets still return 410)
mark-entity-distinctset-entity-distinctsame identities; distinct defaults true
unmark-entity-distinctset-entity-distinctdistinct=false
mark-semantic-tests-distinctset-entity-distinctentityType=TEST + the two TestLocators
get-batch-view-urlfetch-execution-reportbatchInvocationId only is allowed; response always includes batchViewUrl
get-suite-execution-statsget-execution-history (list_execution_history)same filters + aggregate=true
get-perf-runlist-perf-runsrunId (+ optional includeRaw)
get-release-detailsget-releaseversion + detail=GATE
create-issueupsert-issueomit issueId; title required
update-issue-statusupsert-issueissueId + status (and any other patch fields)

New tools with no v1 equivalent: list-issues (status / severity / assignee / label / release / text) and upsert-issue for create-or-update.

Intentionally unchanged​

Plans (stories / scenarios / lifecycle), TrueCoverage, credentials / bot bootstrap / project setup, and anything auth or login related. upload-attachment stays (it already accepts inline base64). BunnyShell diagnostics stay as three troubleshooting tools. get-eaas-config stays a standalone advertised tool because skills use it as the MCP connectivity check (ephemeral-environment action=CONFIG remains available too).

Develop-only tools shipped in 1.0.18–1.0.24 stay as-is. ask-about-testchimp (POST /api/mcp/ask_about_testchimp, CLI/skill alias ask-testchimp-question) is a distinct docs-KB Q&A tool — not folded into another family.

Client / skill follow-up​

Update @testchimp/cli MCP tool descriptors and the TestChimp skill to the new names. Hide or delete the old kebab names after one skill release. Shorten any remaining projectApiKey / botId boilerplate on the client — the server never required those as JSON fields.

Frequently asked questions

Is MCP API 2.0.0 backward compatible?

Old HTTP paths still work as hidden aliases. The advertised OpenAPI and MCP tool list is the consolidated v2 surface.

What replaces get-release-details?

get-release with version and detail=GATE. Catalog list/get is unchanged when detail is omitted.

FAQ

Is MCP API 2.0.0 backward compatible?

Old HTTP paths still work as hidden aliases. The advertised OpenAPI and MCP tool list is the consolidated v2 surface.

What replaces get-release-details?

get-release with version and detail=GATE. Catalog list/get is unchanged when detail is omitted.

How do agents list and update issues now?

Use list-issues for search and upsert-issue to create (omit issueId) or patch (set issueId). get-issue-details is unchanged.