generated: '2026-09-05'
method: derived
source: >-
  mcp/continuous-delivery-foundation-mcp.yml,
  openapi/continuous-delivery-foundation-jenkins-pipeline-graph-view-openapi.yaml,
  openapi/continuous-delivery-foundation-screwdriver-openapi.json,
  openapi/continuous-delivery-foundation-spinnaker-openapi.json
note: >-
  This crosswalk records a real and unusual divergence rather than a tidy binding. The one MCP
  server in the CDF estate is Jenkins'. Its 18 tools are backed by the Jenkins CORE remote-access
  API, which Jenkins documents in prose and exposes as XML/JSON/Python trees at ?api/ — it
  publishes no OpenAPI, so there is no operationId to bind to. The only Jenkins OpenAPI in this
  repo belongs to a DIFFERENT component, the Pipeline Graph View plugin, which happens to cover a
  few of the same actions on the same host. Those overlaps are recorded at low/medium confidence
  and explicitly marked as different components, not as the tools' backing operations. The
  Screwdriver and Spinnaker contracts have no MCP surface at all and are listed whole under
  rest_only.
surfaces:
  openapi:
    - file: openapi/continuous-delivery-foundation-jenkins-pipeline-graph-view-openapi.yaml
      project: Jenkins (Pipeline Graph View plugin)
      operations: 10
      gated: false
      note: templated servers ({build_url}) — runs on the operator's own Jenkins
    - file: openapi/continuous-delivery-foundation-screwdriver-openapi.json
      project: Screwdriver
      operations: 152
      gated: false
      note: live at https://api.screwdriver.cd/v4/openapi.json
    - file: openapi/continuous-delivery-foundation-spinnaker-openapi.json
      project: Spinnaker
      operations: 288
      gated: false
      note: static document served from spinnaker.io; servers[] is the generated http://localhost
  graphql: null
  mcp:
    endpoint: https://<your-jenkins-host>/mcp-server/mcp
    gated: true
    gate: >-
      self-hosted — no public instance exists, so tools/list could not be called anonymously and
      no inputSchema was captured
crosswalk:
  - tool: getBuildLog
    category: build-information
    rest: [getConsoleText, getBuildConsoleOutput]
    binding: rest
    confidence: low
    note: >-
      Same capability (read a build's console output on the same Jenkins host) but a different
      component — these operationIds belong to the Pipeline Graph View plugin, not to the core
      remote-access API the MCP tool actually calls. Recorded as an overlap, not as the backing
      operation.
  - tool: rebuildBuild
    category: build-information
    rest: [rerunPipeline]
    binding: rest
    confidence: low
    note: >-
      Both re-run a build; the plugin operation is scoped to a Pipeline run in its own UI context
      while the MCP tool schedules through the core queue and returns a queue item.
  - tool: getBuild
    category: build-information
    rest: [getPipelineRuns]
    binding: rest
    confidence: low
    note: overlapping read of build/run metadata, different component and different shape
mcp_only:
  - tool: getJob
    reason: Jenkins core remote-access API; no published OpenAPI operation
  - tool: getJobs
    reason: Jenkins core remote-access API; no published OpenAPI operation
  - tool: triggerBuild
    reason: Jenkins core build queue; no published OpenAPI operation
  - tool: getQueueItem
    reason: Jenkins core queue API; no published OpenAPI operation
  - tool: updateBuild
    reason: Jenkins core build API; no published OpenAPI operation
  - tool: searchBuildLog
    reason: server-side composite over the console log; no REST equivalent published
  - tool: getReplayScripts
    reason: Pipeline replay surface; no published OpenAPI operation
  - tool: replayBuild
    reason: Pipeline replay surface; no published OpenAPI operation
  - tool: getTestResults
    reason: JUnit plugin surface; no published OpenAPI operation
  - tool: getJobScm
    reason: SCM API surface; no published OpenAPI operation
  - tool: getBuildScm
    reason: SCM API surface; no published OpenAPI operation
  - tool: getBuildChangeSets
    reason: SCM changelog surface; no published OpenAPI operation
  - tool: findJobsWithScmUrl
    reason: server-side search across jobs; no REST equivalent published
  - tool: whoAmI
    reason: Jenkins core whoAmI; no published OpenAPI operation
  - tool: getStatus
    reason: MCP-specific health/readiness roll-up; no published OpenAPI operation
rest_only:
  - capability: Jenkins pipeline graph and step inspection
    file: openapi/continuous-delivery-foundation-jenkins-pipeline-graph-view-openapi.yaml
    operations: [getPipelineTree, getAllSteps, getStepsByNode, getExceptionText, hasNextBuild, cancelPipeline]
  - capability: Screwdriver — the entire v4 API
    file: openapi/continuous-delivery-foundation-screwdriver-openapi.json
    operations_count: 152
    note: >-
      pipelines, events, builds, jobs, templates, commands, collections, secrets, tokens, banners,
      build clusters, webhooks. No MCP tool exists for any of it.
  - capability: Spinnaker — the entire Gate API
    file: openapi/continuous-delivery-foundation-spinnaker-openapi.json
    operations_count: 288
    note: >-
      applications, pipelines, tasks, executions, artifacts, managed delivery, credentials,
      clusters, load balancers, security groups. No first-party MCP tool exists for any of it.
coverage:
  tools_named: 18
  tools_bound: 3
  tools_bound_confidence: low
  mcp_only: 15
  rest_operations_total: 450
  rest_operations_with_a_tool: 5