odu-mcp

Launch and manage an MCP server over stdio for agent-driven CI runs.

27|1|Updated May 27, 2026
One-click install
npx skills add https://github.com/srid/drishti --skill odu-mcp
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: odu-mcp
Source: https://github.com/srid/drishti/tree/main/.claude/skills/odu-mcp
Command: npx skills add https://github.com/srid/drishti --skill odu-mcp

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires nix.

What problem does it solve?

Automates starting and coordinating MCP CI server runs from a coding agent. bin/serve resolves odu via Nix and runs odu mcp in the current working directory. See the repo README for the tools/resources and override knobs.

Core Features & Use Cases

  • Launch the MCP server from the repository root using the provided launcher.
  • Resolve odu via Nix flakes and run odu mcp within the repo context.
  • Operate via agent-facing commands to manage CI runs (start, cancel, linger).
  • Override the odu source with ODU_FLAKE to pin a specific ref; IPC is handled through the repo's .ci/odu.sock.

Quick Start

Run bin/serve from the repository root to start the MCP server for your coding agent.

Frequently Asked Questions about odu-mcp

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I launch an MCP server for CI runs from a coding agent?

To launch an MCP server for CI runs, execute bin/serve from your repository root. This resolves the odu package via Nix flakes and starts the odu mcp process in the current working directory for your coding agent to control.

Do I need Nix to run an MCP CI server with odu?

Yes, Nix is required to run the odu MCP CI server. You must have Nix installed with flakes enabled, and your repository must contain the odu configuration to properly resolve and execute the automation commands.

How does an agent manage CI runs over standard IO?

Agent-facing commands manage CI runs over standard IO by starting, reusing, lingering, or canceling runs. The MCP server facilitates this communication, using a .ci/odu.sock file in the repository for local IPC.

Can I pin a specific odu source version for my MCP CI automation?

Yes, you can pin a specific odu source version for MCP CI automation. Set the ODU_FLAKE environment variable to override the default source resolution and pin a specific git ref for your runs.

What is the best way to automate CI loops using an agent and Nix flakes?

The best way to automate CI loops using an agent and Nix flakes is exposing the CI server via stdio. This allows the coding agent to directly initiate, manage, and cancel continuous integration runs within the repository context.