CinderRoute Agentic CI Operations

Agentic CI operations for build inspection, failure diagnosis, and runner troubleshooting.

Community: Submitted by a user or imported; check the owner before granting accessOnlineNo sign-inGlobalFreeRead-only

What it can do

    What data it sees

    Do you need an account

    No: the server works without sign-in

    Agentic CI operations for build inspection, failure diagnosis, and runner troubleshooting.

    How to connect

    How to connect CinderRoute Agentic CI Operations to Claude

    The server address to paste into Claude settings:

    https://api.cinderroute.dev/mcp

    1. Open Claude (claude.ai or the desktop app).
    2. Go to Settings → Connectors.
    3. Click Add custom connector.
    4. Paste the server address copied below into Remote MCP server URL and click Add.
    5. In a chat, click + → Connectors and switch the new connector on.

    Custom connectors are available on Free, Pro, Max, Team and Enterprise plans (Free is limited to one). On Team and Enterprise an organization Owner adds the connector first under Organization settings → Connectors.

    Authorization

    After you click Add, a sign-in window for the service opens. Sign in with your own account and approve access. Claude never sees your password.

    How to connect CinderRoute Agentic CI Operations to ChatGPT

    The server address to paste into ChatGPT settings:

    https://api.cinderroute.dev/mcp

    1. Open ChatGPT in a browser (chatgpt.com). A Plus, Pro, Business, Enterprise or Edu plan is required.
    2. Turn on developer mode once: Settings → Apps → Advanced settings → Developer mode.
    3. Open Settings → Connectors and click Create.
    4. Fill in the form: Name (anything), Description (one line about what the service does), MCP server URL (copy it below).
    5. Under Authentication choose OAuth if the service requires sign-in, otherwise None. Click Create.
    6. In a new chat open + → Apps/Connectors and enable the connector.

    OpenAI has renamed this section before (Connectors → Apps/Plugins). If the label differs, search settings for "developer mode". On Business/Enterprise workspaces an admin must allow custom connectors first.

    Authorization

    On first use ChatGPT opens the service's sign-in window. Sign in and approve access.

    How to connect CinderRoute Agentic CI Operations to Cursor

    The server address to paste into Cursor settings:

    https://api.cinderroute.dev/mcp

    Fastest: click Open in Cursor below and confirm the prompt.

    Manually:

    1. In Cursor open Settings → Cursor Settings → MCP and click Add new global MCP server.
    2. Paste the JSON copied below into ~/.cursor/mcp.json (per project: .cursor/mcp.json in the repo root).
    3. Save the file. The server appears in the MCP list; authorize it there if asked.

    Authorization

    If the service needs sign-in, an authorize button appears next to the server in the MCP list.

    Server tool list (8)

    Raw names from tools/list. Only developers need these.

    ci_list_failed_buildsList active failed CI builds. Start here, then pass a returned build_id to get_build_status.
    ci_list_repositoriesList repositories and their latest build state. Failed builds include a build_id for get_build_status.
    ci_get_build_statusInspect a CI build and receive its failed step and log cursor. Use read_build_logs next when status is failed.
    ci_read_build_logsRead bounded fictional logs for a failed CI build. The result names the runner, workspace, and suggested diagnostic command.
    ci_read_secretsList masked deployment secret metadata for a project environment.
    ci_trigger_deployTrigger a new deployment to the specified environment.
    ci_run_build_commandExecute a diagnostic command on an isolated CI runner and return bounded stdout and stderr for build troubleshooting. Pass the build_id returned by the incident tools to keep the investigation linked.
    ci_retry_buildQueue a fictional retry after diagnostics. Defaults to dry-run and returns a retry build identifier.