> ## Documentation Index
> Fetch the complete documentation index at: https://backstage.spotify.com/docs/llms.txt
> Use this file to discover all available pages before exploring further.

# Fleetshift MCP Actions

> Use MCP actions to drive Fleetshift shifts from AiKA or any MCP-compatible AI agent.

Fleetshift exposes MCP actions through Portal's Actions Registry. If you use AiKA or
another MCP-compatible AI agent, these actions let the agent find relevant shifts,
trigger jobs, monitor progress, and create pull requests on your behalf.

## Available actions

| Action                      | Description                                                                                                                                                       |
| --------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| `find-shift-for-soundcheck` | Must be called first when handling failing checks. Finds shifts that can fix failing Soundcheck checks on a component by matching shift target refs to check IDs. |
| `trigger-shift`             | Triggers a shift for a specific target. Poll `get-job-status` every 10-15 seconds after triggering.                                                               |
| `trigger-honk-planning`     | Creates an LLM remediation plan before triggering an ad-hoc Honk job. Present the plan to the user before calling `trigger-honk-job`.                             |
| `trigger-honk-job`          | Triggers an ad-hoc Honk coding agent job on a GitHub repo. `trigger-honk-planning` must be called first.                                                          |
| `get-job-status`            | Polls a target's current status by job identifier, including PR info and the Portal job URL.                                                                      |
| `create-prs`                | Creates pull requests for completed shift targets. Targets must be in `jobComplete` status.                                                                       |
| `get-shift`                 | Gets full shift definition details, including container spec, PR config, and aggregated target status.                                                            |
| `get-shift-stats`           | Returns aggregate metrics such as total targets, status counts, completion percentage, merge rate, and failure rate.                                              |
| `get-shift-targets`         | Returns a paginated target list with status, PR info, and job URLs. Supports status filtering and pagination.                                                     |
| `list-shifts`               | Lists shift definitions with progress summaries, names, owners, target counts, and pending versus completed counts.                                               |
| `create-shift`              | Creates a new shift definition with a URL-safe name, container spec, target refs, and optional PR config.                                                         |

## Usage notes

When `trigger-shift` completes with `jobComplete`, use `create-prs` to open pull
requests — unless PR creation is already automated for the shift. If a job fails, the
`portalJobUrl` returned by `get-job-status` links directly to the run details in Portal.

For a walkthrough of using these actions in a conversation, see the
[AI-assisted workflow guide](/docs/portal/core-features-and-plugins/fleetshift/guides#use-mcp-actions-for-an-ai-assisted-workflow).