Cutover MCP (Model Context Protocol) 
An MCP server for interacting with the Cutover API, powered by FastMCP.
Contents
- Capabilities
- Installation
- Setup
- Environment Configuration
- Security & Responsible Use
- Project Structure
- Notes
- Client Setup
- Docker Usage
- Example: Using Docker in MCP Server Configuration
- FAQs
- Troubleshooting
Capabilities
The server exposes 45 tools over MCP, grouped into 14 categories.
Tool Groups
| Group | Description |
|---|---|
runbooks |
Create, read, update, and control the lifecycle of runbooks and templates |
runbook_types |
List, fetch, and query runbook types |
tasks |
Read, add, update, and progress (start/complete/skip/delete) tasks within a runbook |
task_types |
Look up task types, including integration-backed and agentic (AI agent) task types |
streams |
Create, read, update, and delete streams and substreams within a runbook |
workspaces |
List, search, fetch, and create workspaces |
teams |
Look up teams associated with a runbook |
users |
Look up and search for users |
custom_fields |
Discover custom fields and their metadata/valid options, and create, update and archive field definitions and groups |
data_sources |
Get a signed URL to upload the file a data source reads from |
folders |
List folders within a workspace |
comments |
Post and read comments on a runbook or task |
activities |
Read a runbook's activity trail |
action_logs |
Read the platform audit log |
Tools
Runbooks
list_runbooks - List all runbooks in a specific workspace
workspace_id: The unique identifier for the workspace (string, required)is_template: Filter by template status — false excludes templates, true shows only templates (boolean, optional)archived: Filter by archived status — false excludes archived runbooks, true shows only archived (boolean, optional)source_runbook_id: Filter to only runbooks created from this template ID (string, optional)folder_id: Filter to only runbooks in this folder ID (string, optional)extra_params: Additional query parameters to pass to the API, e.g.{"stage": "active"}(object, optional)
get_runbook_by_id - Fetch details for a specific runbook by its ID
runbook_id: The unique identifier for the runbook (string, required)
create_runbook - Create a new runbook in a workspace, or as a copy of an existing runbook/template
name: The name of the new runbook (string, required)workspace_id: The workspace to create the runbook in — required unlesscopy_source_runbook_idis passed (string, optional)description: Description for the runbook (string, optional)status: RAG status — off, red, amber, green (string, optional)is_template: Whether the runbook is a template (boolean, optional)template_type: off, default, or snippet (string, optional)rto: Recovery Time Objective in seconds (integer, optional)timezone: IANA timezone name (string, optional)runbook_type_id: Runbook type to associate (string, optional)rto_start_task/rto_end_task: Start/end task IDs for the RTO/RTA feature (string, optional)folder_id: Folder to place the runbook in — defaults to the workspace's default location (string, optional)custom_field_values: Custom field values to set, including runbook dashboard fields — see Custom Fields (array of object, optional)master_template: Whether this runbook can generate app-specific templates — requiresis_template=true, and the API rejects it otherwise; on rejection, surface it rather than silently settingis_template=true(boolean, optional)start_scheduled: ISO 8601 timestamp, or the literal"now", to schedule the start (string, optional)end_scheduled: ISO 8601 timestamp for the scheduled end — must be omitted ifstart_scheduledisn't set (string, optional)auto_start: Whether to auto-start oncestart_scheduledis reached (runs live, comms on) (boolean, optional)copy_source_runbook_id: ID of an existing runbook/template to copy from (string, optional)copy_tasks/copy_teams/copy_users: What to include in the copy — each defaults to true; teams copied without members unlesscopy_usersis also true (boolean, optional)shift_fixed_times: When copying, recalculate fixed task times relative to the new runbook's start (boolean, optional)
update_runbook - Update a specific runbook's fields
runbook_id: The unique identifier for the runbook (string, required)name/description: New name/description (string, optional)status: RAG status — off, red, amber, green (string, optional)is_template: Whether the runbook is a template (boolean, optional)rto: Recovery Time Objective in seconds (integer, optional)timezone: IANA timezone name (string, optional)rto_start_task/rto_end_task: Start/end task IDs for the RTO/RTA feature (string, optional)custom_field_values: Custom field values to update, including runbook dashboard fields — see Custom Fields (array of object, optional)folder_id: Folder to move the runbook to (string, optional)master_template: Requiresis_template=true; the API rejects it on a non-template runbook — surface the rejection instead of auto-flippingis_template(boolean, optional)start_scheduled/end_scheduled: ISO 8601 timestamps (or"now"for start) to (re)schedule the runbook (string, optional)auto_start: Whether to auto-start oncestart_scheduledis reached (boolean, optional)
manage_runbook - Start, cancel, pause, or resume a runbook
runbook_id: The unique identifier for the runbook (string, required)action: start, cancel, pause, or resume — the only supported actions (string, required)comms: off, test, on — start only (string, optional, default "off")disable_task_notify: Disable task start notifications — start only (boolean, optional)run_type: live or rehearsal — start only (string, optional, default "rehearsal")rebaseline: Recalculate all planned times based on current time — start only (boolean, optional)shift_fixed_times: Shift fixed-time tasks relative to current time — start only (boolean, optional)validation_level: warning or error — start only (string, optional, default "error")message: Note attached to the action — cancel/pause/resume only (string, optional)notify: Notify users about the action — cancel/pause/resume only (boolean, optional)
get_runbook_template_copies - Get all runbooks created from a specific runbook template
runbook_id: The template runbook ID to find copies of (string, required)
Runbook Types
list_runbook_types - List all runbook types in the instance
No parameters.
get_runbook_type_by_id - Fetch details for a specific runbook type by its ID
runbook_type_id: The unique identifier for the runbook type (string, required)
query_runbook_types - Find runbook types matching text and/or capability flags
query: Case-insensitive text matched against the runbook type name, key, and description (string, optional)incident: Filter by whether the type is for incidents (boolean, optional)enable_rto: Filter by whether the type supports the RTO/RTA feature (boolean, optional)dynamic: Filter by whether the type is dynamic (boolean, optional)ai_create_enabled: Filter by whether AI-assisted creation is enabled for the type (boolean, optional)include_archived: Include archived runbook types; archived types are excluded by default (boolean, optional)include_disabled: Include disabled runbook types; disabled types are excluded by default (boolean, optional)
Tasks
get_runbook_tasks - Fetch tasks for a specific runbook, with optional filtering and sorting
runbook_id: The unique identifier for the runbook (string, required)forecast: Return all tasks with computed timing (start_display/end_display) and dependency graph fields, overriding pagination/filters (boolean, optional)fields_task: Specific task fields to return, e.g.["name", "stage"](array of string, optional)stage: Filter by stage — default, startable, in_progress, complete (array of string, optional)stream_id: Filter to tasks in these stream IDs (array of string, optional)completion_type: complete_normal, complete_skipped, complete_abandoned, complete_auto (string, optional)task_type_id: Filter to tasks of these task type IDs (array of string, optional)level: Filter by task level (string, optional)search_term: Match against task name (string, optional)has_comments: Only return tasks that have comments (boolean, optional)runbook_team_id: Filter to tasks assigned to these runbook team IDs (array of string, optional)user_id: Filter to tasks assigned to these user IDs (array of string, optional)source_runbook_id: Filter to tasks originating from these source runbook IDs (array of string, optional)sort: Sort field, e.g.start_plannedor-start_plannedfor descending (string, optional)
add_task_to_runbook - Add a new task to an existing runbook
runbook_id: The runbook to add the task to (string, required)name: Task name (string, required)description: Task description (string, optional)task_type_id: Task type id fromlist_task_types, which includes integration-backed and agentic types (string, optional)stream_id: Stream (or substream) to assign the task to (string, optional)predecessors: Task IDs that are predecessors to this task (array of string, optional)duration: Planned duration in seconds (integer, optional)task_links: Links to other resources —link_type="runbook"links to a template runbook (target must be a template with ≥1 task and the task'stask_type_idmust be the tenant'slinkedtype, or the link is silently dropped);link_type="snippet"attaches snippets (array of object, optional)message: Message body for an Email/SMS/Call task, or initial prompt for an agentic task (string, optional)recipients: Recipients for a comms task (array of object, optional)assignees: Assignees to add — only users/teams already participating on the runbook are honored, others are silently ignored (array of object, optional)custom_field_values: Custom field values to set — see Custom Fields (array of object, optional)start_fixed/end_fixed: ISO 8601 timestamps fixing start/end (string, optional)level: level_1, level_2, or level_3 (string, optional, default level_3)auto_start: Start automatically once predecessors complete (boolean, optional)auto_finish: Complete automatically once started (boolean, optional)
update_runbook_task - Update an existing task (dependencies, description, stream, duration, etc.)
runbook_id/task_id: The runbook and task to update (string, required)name/description: New name/description (string, optional)predecessors: Task IDs that are predecessors to this task (array of string, optional)task_type_id: Task type id fromlist_task_types, which includes integration-backed and agentic types (string, optional)stream_id: Stream (or substream) to assign the task to (string, optional)duration: Planned duration in seconds (integer, optional)custom_field_values: Custom field values to update — see Custom Fields (array of object, optional)assignees: Assignees to add — only existing runbook participants are honored; additive by default (array of object, optional)delete_excluded_assignees: When true, replaces the full assignee list with only those provided instead of adding to it (boolean, optional, default false)task_links: Replaces the task's links entirely — pass an empty list to clear all links (array of object, optional)message: Message body for an Email/SMS/Call task, or initial prompt for an agentic task (string, optional)recipients: Recipients for a comms task (array of object, optional)start_fixed/end_fixed: ISO 8601 timestamps fixing start/end (string, optional)level: level_1, level_2, or level_3 (string, optional)auto_start/auto_finish: Auto-start on predecessor completion / auto-finish on start (boolean, optional)
start_task - Start a specific task in a runbook
runbook_id/task_id: The runbook and task to start (string, required)
complete_task - Complete a specific task in a runbook
runbook_id/task_id: The runbook and task to complete (string, required)
skip_task - Skip a specific task in a runbook
runbook_id/task_id: The runbook and task to skip (string, required)comment: Reason for skipping — required by the API and posted as a runbook comment (string, required)
delete_task - Delete a single task from a runbook
runbook_id/task_id: The runbook and task to delete (string, required)
Task Types
list_task_types - List all task types, including integration-backed ones (Jenkins, ServiceNow, webhooks, AI agent tasks); each carries a `meta.integration_action` object (`kind`, `description`, `hooks`, `definition`)
include_integration: Include task types backed by an integration action (boolean, optional, default true)
get_integration_task_type_details - Summarise how an integration-backed task type is configured (descriptive settings only, never credentials); needs an integrations-admin or stakeholder role
integration_action_id: The integration action id from the task type'sintegration_actionrelationship (string, required)
Streams
list_streams - List all streams for a runbook, including substreams
runbook_id: The runbook to list streams for (string, required)forecast: Include computed forecast fields (start_display,end_display, etc.) (boolean, optional)
get_stream - Get details of a specific stream or substream
runbook_id/stream_id: The runbook and stream to fetch (string, required)
create_stream - Create a new stream or substream in a runbook
runbook_id: The runbook to create the stream in (string, required)name: Stream name (string, required)description: Stream description (string, optional)color: CSS-friendly color, e.g.#f0f0f0orrgb(0,0,0)(string, optional)parent_stream_id: Parent stream ID, if creating a substream (string, optional)
update_stream - Update an existing stream in a runbook
runbook_id/stream_id: The runbook and stream to update (string, required)name/description/color: New values (string, optional)
delete_stream - Delete a stream from a runbook
runbook_id/stream_id: The runbook and stream to delete (string, required)
Workspaces
list_workspaces - List all workspaces
limit: Maximum workspaces to return (integer, optional, default 50)offset: Number of workspaces to skip (integer, optional, default 0)
query_workspaces - Search for workspaces by name or query string
query: Search string (string, required)
get_workspace_by_id - Fetch details for a specific workspace by its ID
workspace_id: The unique identifier for the workspace (string, required)
create_workspace - Create a new account/workspace
name: Workspace/account name (string, required)key: Shortened version of the name (string, required)description: Workspace/account description (string, optional)
Teams
get_runbook_teams - Get all teams associated with a runbook
runbook_id: The runbook to fetch teams for (string, required)
Users
get_user - Get user details by user ID
user_id: The user ID to fetch (string, required)
search_users - Search for users by name or email (fuzzy match)
query: Search string — name or email, partial match (string, required)
Custom Fields
The runbook and task tools accept custom_field_values as a list of {"custom_field_id": "123", "value": ...} entries, where the id comes from list_custom_fields. A field's internal name can be used in place of the id, but its display_name cannot. Each value is a string, or a list of strings for multi-select fields. Malformed entries are rejected before any request is sent to Cutover.
list_custom_fields - List all available custom fields, to discover fields that may not have values yet
workspace_id: Filter to a workspace — omit to return fields from all accessible workspaces (string, optional)include_global: Whenworkspace_idis set, also include globally available fields alongside the workspace's own (boolean, optional, default true)scope: task, runbook, or all (string, optional, default "all") — runbook also covers dashboard fields on the runbook homepage, PIR and Incident Review
get_custom_field - Get a custom field's metadata including its type, valid options, group and constraints
custom_field_id: The custom field to retrieve (string, required)
The tools below change field definitions (the Custom Fields admin page), not the values on a runbook or task. They need the Custom Fields Admin or Global Admin role.
create_custom_field - Create a custom field definition
name: The field's name (string, required). The API sets the UI label to the same valuefield_type: text, textarea, select_menu, radiobox, checkboxes, datetime or user_select (string, required)apply_to: runbook_add_edit, runbook_edit, runbook_page, task_add_edit, task_edit, task_start or task_end (string, required)workspace_id: The workspace that owns the field (string, required unlessglobal_fieldis true)global_field: Create the field for every workspace (boolean, optional, default false)field_options: Option names — required for select_menu, radiobox and checkboxes, rejected otherwise (array of string, optional)required,allow_field_creation,display_list,display_search,display_table: Field settings (boolean, optional)default_value: The value a new runbook or task starts with (string, optional)custom_field_group_id: The group to show the field in (string, optional)task_type_ids,runbook_type_ids: Limit the field to these task or runbook types (array of string, optional)
update_custom_field - Update a custom field definition
custom_field_id: The field to update (string, required)name: The new name (string, optional)add_field_options: Option names to add to a select_menu, radiobox or checkboxes field; existing options are kept, and other field types are rejected (array of string, optional)required,allow_field_creation,display_list,display_search,display_table: Field settings (boolean, optional)default_value: The value a new runbook or task starts with (string, optional)custom_field_group_id: Move the field to this group, or""to take it out of its group; omitted, the field stays in its current group (string, optional)task_type_ids,runbook_type_ids: Replace the constraints of that type; the other type is kept, and an empty list is rejected because the API cannot clear them (array of string, optional)
archive_custom_field - Archive a custom field definition
custom_field_id: The field to archive (string, required)
list_custom_field_groups - List custom field groups
Takes no parameters. Archived groups are not returned; the API does not list them.
create_custom_field_group - Create a custom field group
name: The group's name (string, required)
update_custom_field_group - Rename a custom field group
custom_field_group_id: The group to rename (string, required)name: The new name (string, required)
archive_custom_field_group - Archive a custom field group
custom_field_group_id: The group to archive (string, required)
Data Sources
get_data_source_upload_url - Get a signed URL to upload a file for a data source
file_name: Name of the file to upload, e.g.cmdb.csv(string, required)data_source_id: An existing data source to upload a new version of the file for; omit for the first upload (integer, optional)
The server cannot read files on your machine, so the agent uploads the file itself with an HTTP PUT to the returned url before it expires (expires_in seconds), then creates the data source with the returned datasource_endpoint_url as its URL. A new version for an existing data source is only read if the returned datasource_endpoint_url is that data source's current URL; refresh and sync the data source afterwards. Fails with a clear error if the instance's data source search service is not configured.
Folders
list_folders - List all folders in a specific workspace
workspace_id: The workspace to list folders for (string, required)
Comments
add_comment - Post a comment on a runbook, optionally attached to a specific task
runbook_id: The runbook to comment on (string, required)content: Comment text — a limited set of HTML tags is supported (e.g.<p>,<b>,<ul>,<code>); markdown is not rendered and disallowed tags are stripped (string, required)task_id: Task to attach the comment to — omit to post at runbook level (string, optional)
get_comments - List the comments on a runbook, optionally filtered to a specific task
runbook_id: The runbook to read comments from (string, required)task_id: Return only the comments attached to this task — omit for every comment on the runbook, including runbook-level ones (string, optional)
Activities
get_activities - Get activities for an incident runbook, to track recent actions and events
runbook_id: The runbook to retrieve activities for (string, required)created_after/created_before: ISO 8601 date bounds (string, optional)
Action Logs
get_action_logs - Retrieve action logs (audit logs), paginated
runbook_id/user_id/workspace_id: Filter by runbook, user, or workspace (string, optional)created_after/created_before: ISO 8601 date bounds (string, optional)max_pages: Maximum pages to fetch — response flagstruncated: trueif more remain (integer, optional, default 10)
This includes both read and write tools — see Security & Responsible Use for how to scope access appropriately.
Installation
The server is published on PyPI as cutover-mcp and runs with uv, which downloads Python 3.13+ on demand, so uv is the only prerequisite. On macOS:
brew install uv
Other platforms: see the uv installation guide.
Then point your MCP client at uvx cutover-mcp with your credentials in its env block — see Client Setup. uvx downloads the latest release on first run and caches it; pin a version with uvx cutover-mcp@1.2.3. No clone, no virtualenv.
To start it from a terminal instead (it waits for an MCP client on stdin, so it will look idle; Ctrl+C to stop):
CUTOVER_BASE_URL=https://api.cutover.net CUTOVER_API_TOKEN=your_token_here CUTOVER_CORE_URL=https://YOUR-INSTANCE-NAME.cutover.com uvx cutover-mcp
Setup
Only needed to work on the server itself or to run an unreleased build; to just use it, see Installation above.
- Copy
.env.exampleto.envand fill in your Cutover API credentials — see Environment Configuration below. - Install dependencies with uv:
uv sync - Run the server using:
uv run cutover-mcp
That is the same console scriptuvx cutover-mcpruns;uv run python src/cutover_mcp/server.pyworks too. - Run tests:
uv run pytest
Environment Configuration
Which URLs do I need?
For most instances, one URL and a token:
CUTOVER_CORE_URL=https://your-instance.cutover.com
CUTOVER_API_TOKEN=MY_TOKEN_VALUE
CUTOVER_CORE_URL is your Cutover instance URL, the one you open in the browser. The API host (CUTOVER_BASE_URL) defaults to https://api.cutover.net, which serves every shared production instance, so leave it unset unless your instance has its own API host (single-tenant deployments, typically https://api.your-instance.cutover.com). The default only applies to Cutover-hosted instance URLs; for any other instance URL the server asks you to set CUTOVER_BASE_URL rather than guess. If a call fails with an authorization error the message says how to override it; ask your Cutover contact if you are unsure which applies.
Environment Variables Reference
| Variable | Required | Notes |
|---|---|---|
CUTOVER_CORE_URL |
Yes | Your Cutover instance URL, e.g. https://your-instance.cutover.com. Sent as the Core-Url header so the API routes to your instance. |
CUTOVER_API_TOKEN |
Yes | See Generating an API Token below. |
CUTOVER_BASE_URL |
No | The Cutover API host. Defaults to https://api.cutover.net. Set it only for an instance with its own API host, e.g. https://api.your-instance.cutover.com. |
Generating an API Token
There are two ways to generate a token:
- Access Management — an admin generates a token for a specific user (useful if you want the token to act as someone other than yourself, e.g. a global admin, or you don't have self-service access).
- My Details → User App Tokens — generate your own token directly, self-service.
Security & Responsible Use
The MCP server adds no security model of its own — it authenticates to the Cutover API as a single user app token over HTTPS and inherits exactly that user's permissions. Scope the token correctly and use the write tools deliberately:
- Least privilege. Use a dedicated non-interactive user with the Developer role plus only the scoped roles the use case needs (e.g. Workspace manager on one workspace) — not a personal admin token. Rotate the token periodically and revoke it in Cutover when the use case ends.
- Read-only vs read-write. This server ships write tools (
create_runbook,manage_runbook,delete_task,start_task, …) and does not enforce read-only itself. For query-only use cases, omit roles that grant create/update/delete/manage — least privilege is configured in Cutover, not the client. - Approve writes. Keep human approval enabled for mutating or consequential actions — models can act on unexpected content returned by tools, so approval is the real safeguard.
- Verify critical output. A tool call returns real data, but the model's summary of it can still be wrong (or answer with no tool call at all). For compliance- or audit-critical output, verify against Cutover as the system of record.
- Protect the token. It lives in env config (
.env*is git-ignored and excluded from Docker images). If a token is compromised, revoke it immediately in Cutover's Access Management — the MCP server holds no independent session, so revoking the token fully cuts off access, and a scoped role confines any impact to that use case.
Project Structure
src/cutover_mcp/- Main packageclients/- API clientresources/- Resource definitions (MCP endpoints)tools/- Tool logicserver.py- FastMCP server entrypoint (main()is thecutover-mcpconsole script)server.json- The server's MCP Registry entrytests/- Tests
Notes
- Dependency and environment management is handled by uv and hatchling.
- Versioned releases and the changelog live under Releases. Each release is published to PyPI and listed in the MCP Registry as
io.github.gocutover/cutover-mcp. The server reports its version asserverInfo.versionand fromGET /healthwhen running over HTTP.
Client Setup
Run in VS Code GitHub Copilot
If you want to use VS Code with GitHub Copilot to call out to this MCP server, you can use mcp.json.example.
- Copy
mcp.json.exampleto.vscode/mcp.json(create the.vscode/directory if not already present). It runsuvx cutover-mcpand prompts for your API token the first time the server starts, so the token is never written into the project. - Set
CUTOVER_BASE_URLandCUTOVER_CORE_URLin itsenvblock for your instance — see Environment Configuration. - Restart VS Code for the changes to take effect. In the Copilot Chat box, click the Configure tools icon and expand
cutover-mcpto see its full list of tools. MCP tools only run in Agent mode — switch the mode dropdown from Ask to Agent if nothing happens.
Run in Claude Desktop
If you'd rather use Claude Desktop instead of an IDE, you can set that up:
- Download and install Claude Desktop.
- Copy
claude_desktop_config.json.exampleto~/Library/Application Support/Claude/claude_desktop_config.json(macOS path shown; on Windows, use%APPDATA%\Claude\claude_desktop_config.json). - Fill in the
envblock with your credentials — see Environment Configuration. Claude Desktop does not inherit your shell'sPATH, so if it reports thatuvxcannot be found, setcommandto the full path fromwhich uvx(typically/opt/homebrew/bin/uvxon macOS). - Restart Claude Desktop. Click the + button at the bottom of the chat box, then Connectors —
cutover-mcpshould be listed there along with its tools. If it isn't, check Settings → Developer for its connection status and logs.
This will allow Claude Desktop to connect to your MCP server.
Docker Usage
Docker is optional — the server runs fine without it (see Installation). Use this if you want a self-contained way to run it instead of uvx.
From the repository root, build the image:
docker build -t cutover-mcp .
.env is excluded from the build via .dockerignore, so the image isn't tied to any environment or credential — never bake .env into an image you build, push, or share.
Pass your .env file in at run time instead, with --env-file:
docker run -i --rm --env-file .env cutover-mcp
Example: Using Docker in MCP Server Configuration
You can configure your MCP server to use the Docker container instead of uvx. The root key differs by client: VS Code (mcp.json) uses servers; Claude Desktop (claude_desktop_config.json) uses mcpServers.
VS Code (.vscode/mcp.json):
{
"servers": {
"cutover-mcp": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"--env-file",
"/path/to/your/repo/.env",
"cutover-mcp"
]
}
}
}
Claude Desktop (claude_desktop_config.json):
{
"mcpServers": {
"cutover-mcp": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"--env-file",
"/path/to/your/repo/.env",
"cutover-mcp"
]
}
}
}
To use Docker in the example configuration files (mcp.json.example and claude_desktop_config.json.example), replace the existing commands with the Docker-based commands shown in the "Docker Usage" section above.
FAQs
How can I start the MCP server via Visual Studio Code?
Open up the .vscode/mcp.json file. Hover above the name of the server i.e. 'cutover-mcp'. You should have the option to start the server.
Troubleshooting
Why is VS Code not giving me the ability to start the MCP server?
Ensure you aren't running the server independently in another terminal. Close and re-open VS Code, and if that doesn't work, restart your machine.
Alternatively, you can use the following approach to start the server:
View -> Command Palette -> MCP: List Servers -> your mcp server -> start/restart/stop server.
Metadata
Release files for cutover-mcp 1.8.0
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| cutover_mcp-1.8.0.tar.gz | 150.3 kB | With provenance | Details for cutover_mcp-1.8.0.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| cutover_mcp-1.8.0-py3-none-any.whl | Python 3 | none | any | Details for cutover_mcp-1.8.0-py3-none-any.whl |
Total release size: 204.4 kB
Release files / cutover_mcp-1.8.0.tar.gz
| Download URL | cutover_mcp-1.8.0.tar.gz |
|---|---|
| Size | 150.3 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
deaaf97f61ff580dc79913f53016bae719dbc1d6f5c26eafa9948bf987491777
|
|
BLAKE2b-256 checksum How to use checksums |
a2bce537a44631ef473d3c747f8e01c598dc605b524f46d9d6210a6d8023f9d4
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 19, 2026.
Transparency logRelease files / cutover_mcp-1.8.0-py3-none-any.whl
| Download URL | cutover_mcp-1.8.0-py3-none-any.whl |
|---|---|
| Size | 54.1 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
aa98fd21482b081b9d0db34b216f653579b88585737d61fd235ccd2510ca8f75
|
|
BLAKE2b-256 checksum How to use checksums |
acc91e524b3b57a2c15bfc5cc181a6e1c8e9f6f7c54cef8f608d526e3558be68
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.16
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 19, 2026.
Transparency logSecurity for cutover-mcp 1.8.0
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
Full provenance
Both files in this release have been uploaded with provenance metadata.
Attestation for cutover_mcp-1.8.0.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Nov 19, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.