Tod

What theonedev/tod MCP server does

The theonedev/tod MCP server is the agent-facing workflow layer of TOD, a command-line tool for OneDev 15.1 and newer. It provides commands for querying and editing issues, pull requests, and builds, while also supporting local repository operations.

The tool can start CI/CD jobs using uncommitted local changes, a branch, or a tag. It streams job logs while the run is in progress. Developers can also retrieve build logs, recent changes, and code problem reports when diagnosing a build.

For repository work, TOD checks out OneDev issues and pull requests into the current working directory. Its checkout behavior includes moving already retrieved submodules to the commits recorded by the selected revision. Missing submodule commits can be fetched from the submodule remote.

How it works

TOD communicates with a configured OneDev instance and uses the local Git repository for checkout and local-build operations. A local run can collect snapshots from initialized submodules before sending the parent repository. When invoked from inside a submodule, the outermost superproject is used by default unless a working directory is supplied explicitly.

The project includes eight tool-agnostic SKILL.md files. These describe workflows such as general OneDev operations, build-spec editing, failed-build repair, issue work, pull-request work, and commit-message generation. The skills are intended for Claude Code, Cursor, Codex, and other agents that load SKILL.md files; the supplied material does not document a separate MCP client configuration format.

Setup and configuration

Installers are provided for macOS, Linux, FreeBSD, and Windows. The project can also be built from source with Go 1.22.1 or newer. The installation scripts download a platform-specific binary and place it on the system PATH.

Run tod config set interactively, or set individual properties non-interactively. Supported properties are server-url, access-token, and trust-certs-file. Configuration is read from $XDG_CONFIG_HOME/tod/config first, then ~/.config/tod/config; the file uses INI syntax and is written with mode 0600.

The equivalent environment variables are ONEDEV_SERVER_URL, ONEDEV_ACCESS_TOKEN, and ONEDEV_TRUST_CERTS_FILE. They override values from the configuration file. Use the trust-certificate setting when the OneDev server uses a self-signed certificate or an otherwise untrusted CA.

Tools and capabilities

Typical operations include:

• Run a CI job against local changes, a branch, or a tag.
• List and inspect issues using OneDev query syntax.
• Check out an issue or pull request locally.
• List builds and retrieve build details or logs.
• Inspect build diagnostics, including changes and code problems.
• Validate and migrate .onedev-buildspec.yml files.
• Use the shipped skills to guide issue, pull-request, and build workflows.

The theonedev/tod MCP server is suitable for teams that already use OneDev and want local automation around CI, issue handling, pull-request review, and repository changes.

Limitations and notes

Local CI log streaming may require HTTP buffering to be disabled for the /~api/streaming route when OneDev is behind Nginx. Jobs that need secrets require suitable authorization settings, and local changes are pushed to a temporary reference. Submodule snapshots require the configured token to have permission to push to the related OneDev project.

The provided material does not state a formal software license name, nor does it list native support for specific MCP desktop clients. It does document compatibility with agents that consume SKILL.md files, including Cursor and Claude Code.