octopilot-mcp
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| OP_IMAGE | No | Pin to a specific op release for reproducibility | ghcr.io/octopilot/op:latest |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| logging | {} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| extensions | {
"io.modelcontextprotocol/ui": {}
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| tool_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. |
| tool_generate_skaffold_yamlB | Generate a skaffold.yaml for the given build artifacts. |
| tool_generate_ci_workflowB | Generate a complete .github/workflows/ci.yml for the repository. |
| 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. |
| tool_run_op_buildA | Run 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. |
| 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. |
| 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. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| resource_actions | Full Octopilot actions registry as JSON. |
| resource_pipeline_context_schema | JSON Schema describing the pipeline-context object. |
| resource_getting_started | Plain-text getting started guide for wiring a new repo to Octopilot. |
| resource_skaffold_patterns | Common skaffold.yaml patterns for Octopilot projects. |
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/octopilot/octopilot-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server