octopilot-mcp
OfficialGenerate CI workflows and browse the Octopilot GitHub Actions registry, enabling automated CI/CD pipeline creation.
Suggest and generate .pre-commit-config.yaml as part of repository onboarding to enforce code quality checks.
Generate skaffold.yaml configuration files for artifacts, facilitating container image building and deployment.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@octopilot-mcp Onboard the Rust API project in ./rust-api for Octopilot CI"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
octopilot-mcp
Model Context Protocol (MCP) server for Octopilot — enables AI agents to detect, generate, build, and wire up new repositories end-to-end using the Octopilot CI/CD toolchain.
What it does
Tool | Description |
| Parse |
| Generate a |
| Full |
| One-call onboarding: detect → generate files → return next steps |
| Run |
| All Octopilot GitHub Actions from the bundled registry |
| Full spec, inputs, examples, gotchas for one action |
op promote-imageis intentionally not exposed. Image promotion between environments is operationally sensitive and must only run through a GitHub Actions workflow (with audit trail, OIDC credentials, and environment protection rules). Usegenerate_ci_workflowto produce the workflow that handles promotion safely.
Related MCP server: @lex-tools/codebase-context-dumper
Option A — Hosted (zero install)
Connect directly to the public server at https://mcp.octopilot.app — no cloning, no Python, no pip required.
# Cursor
fastmcp install cursor https://mcp.octopilot.app --name octopilot
# Claude Desktop
fastmcp install claude https://mcp.octopilot.app --name octopilotAvailable hosted tools (stateless, no local dependencies):
Tool | Description |
| Browse the Octopilot GitHub Actions registry |
| Full spec, inputs, examples, gotchas for one action |
| Generate a |
| Full |
Need
detect_project_contexts,onboard_repository, orrun_op_build? Those tools need Docker and local filesystem access — use Option B below.
Option B — Local install (full suite)
# Clone and install
git clone https://github.com/octopilot/octopilot-mcp
cd octopilot-mcp
uv syncUsage
Register with your IDE (one command, FastMCP 3 CLI)
Docker or Colima is the only external dependency. Most tools are pure Python;
run_op_build pulls ghcr.io/octopilot/op:latest automatically with
--pull always, so you always run the latest release.
# Cursor
uv run fastmcp install cursor src/octopilot_mcp/server.py --name octopilot
# Claude Desktop
uv run fastmcp install claude src/octopilot_mcp/server.py --name octopilotDevelopment (hot-reload)
uv run fastmcp dev src/octopilot_mcp/server.py --reloadInspect tools from the terminal
# List all available tools
uv run fastmcp list src/octopilot_mcp/server.py
# Call a tool directly
uv run fastmcp call src/octopilot_mcp/server.py tool_list_actionsRun as a server directly
uv run octopilot-mcpManual JSON config (alternative to fastmcp install)
{
"mcpServers": {
"octopilot": {
"command": "uv",
"args": ["run", "--directory", "/path/to/octopilot-mcp", "octopilot-mcp"]
}
}
}Pin to a specific op release (optional):
{
"mcpServers": {
"octopilot": {
"command": "uv",
"args": ["run", "--directory", "/path/to/octopilot-mcp", "octopilot-mcp"],
"env": { "OP_IMAGE": "ghcr.io/octopilot/op:v1.0.0" }
}
}
}Environment variables
Variable | Default | Description |
|
| Pin to a specific op release for reproducibility |
Example agent interaction
User: Onboard this Rust API project to use Octopilot CI.
Agent: [calls onboard_repository("/path/to/my-api", "ghcr.io/my-org")]
→ Detected: rust (stable) in api/
→ Generated: skaffold.yaml, .github/workflows/ci.yml
→ Next steps: add .pre-commit-config.yaml, push changesDevelopment
uv sync --all-extras
# Run tests
uv run pytest tests/ -v
# Run with coverage
uv run pytest tests/ --cov=src/octopilot_mcp --cov-report=term-missingTool module coverage target: ≥95% (actions, detect, generate, op_runner).
See CONTRIBUTING.md for details.
Resources
The server also exposes MCP resources for agent context:
octopilot://actions— Full actions registry JSONoctopilot://pipeline-context-schema— JSON Schema for pipeline-contextoctopilot://docs/getting-started— Plain-text onboarding guideoctopilot://docs/skaffold-patterns— Commonskaffold.yamlpatterns
Available Tools
7 toolstool_detect_project_contextsA
Parse skaffold.yaml in the workspace and return a pipeline-context JSON object.
The pipeline-context is consumed by lint, test, janitor, and ci workflow generation. It contains the detected languages, versions, and build matrix.
Inputs: workspace (required). Returns: object
tool_generate_ci_workflowB
Generate a complete .github/workflows/ci.yml for the repository.
Inputs: registry (required), pipeline_context (required), platforms, golangci_lint_timeout. Returns: result
tool_generate_skaffold_yamlB
Generate a skaffold.yaml for the given build artifacts.
Inputs: artifacts (required), builder. Returns: result
tool_get_action_detailsA
Return the full spec for a single Octopilot GitHub Action.
Includes: description, all inputs/outputs, example workflow YAML, and known gotchas with symptoms and fixes.
Inputs: action_id (required). Returns: result
tool_list_actionsA
Return all Octopilot GitHub Actions from the bundled registry.
Each entry includes: id, title, path, description, features, inputs, outputs. Use get_action_details for examples and gotchas.
Inputs: no named parameters. Returns: result
tool_onboard_repositoryA
Onboard a repository end-to-end in a single call.
Detects the project languages, generates skaffold.yaml (if missing) and .github/workflows/ci.yml, and returns a ready-to-commit file set plus a checklist of remaining manual steps.
Inputs: registry (required), workspace (required), builder, platforms. Returns: object
tool_run_op_buildA
Run op build in the workspace using the official op container.
Docker or Colima must be running. The container image is always pulled before each run so the latest op release is used automatically. Set OP_IMAGE in the MCP server env to pin to a specific version.
Inputs: registry (required), workspace (required), push, platforms. Returns: object
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 7 tools
Each tool targets a distinct operation: project detection, CI workflow generation, skaffold generation, action details, action listing, full onboarding, and running builds. There is no functional overlap.
All tools follow a consistent verb_noun pattern in snake_case (e.g., detect_project_contexts, generate_ci_workflow, list_actions). The naming is predictable and clear.
With 7 tools, the set is well-scoped for the domain of CI/CD pipeline management and onboarding. Each tool has a clear purpose and contributes to the overall workflow.
The tool surface covers core workflows: detection, generation, action interaction, onboarding, and building. Minor gaps exist (e.g., no tool for updating existing configurations or tear-down), but the main use cases are addressed.
Maintenance
Related MCP Connectors
A comprehensive Model Context Protocol (MCP) server that enables AI assistants to interact with yo…
Model Context Protocol server for the Apideck Unified API. Connect any MCP-compatible agent framework to 100+ accounting systems, HRIS platforms, file storage providers, and more through one integration. More information https://www.apideck.com/mcp-server
MCP server for AI agents to plan, verify, and deploy Cloudflare-native apps.
MCP server for building and testing AI agents with multi-model experimentation and insights.
Related MCP Servers
- AlicenseAqualityCmaintenanceA Model Context Protocol (MCP) server that helps large language models index, search, and analyze code repositories with minimal setup22142,325 PyPI1,004MIT
- AlicenseAqualityDmaintenanceA Model Context Protocol (MCP) server designed to easily dump your codebase context into Large Language Models (LLMs).18 npm3Apache 2.0
- FlicenseNot gradedqualityDmaintenanceA Model Context Protocol (MCP) server that bridges BMAD agents with GitHub Copilot, enabling AI-assisted development workflows through specialized agent tools and prompts.1-
- AlicenseNot gradedqualityDmaintenanceA Model Context Protocol (MCP) server that provides VSCode context and filesystem operations for AI assistants.9MIT