Skip to content
Codemind logo

Codemind MCP server

Which servers in the official MCP registry are Codemind's own, whether they answer, and what they offer. A program checked each of these, nobody copied them from a product page.

read 2026-10-12

← Back to Codemind

Whose server it is
  • Registry namedev.codemindhq/codemindverified in the MCP registry

The registry name sits under codemindhq.dev. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.

When we asked itchecked 2026-10-12
  • Stateanswerschecked 2026-10-12
  • Tools26
  • Server calls itselfcodemind-v2
  • Server version1.0.0
  • Protocol version2024-11-05

On 2026-10-12 the server answered initialize and tools/list without a sign-in. First answer in 455 ms.

Tools it offers26 tools · read 2026-10-12
  • create_free_account

    Instantly provision a new anonymous Codemind account on the free plan — no credential, no human step required. Call this when build_feature (or any other tool) fails with an auth error and no CODEMIND_API_KEY is configured. Returns a…

  • build_feature

    Generate a feature via Codemind: takes a story title + acceptance criteria, generates the implementation and its tests, runs automated checks against the acceptance criteria before returning, and returns a buildId immediately. Call…

  • stream_build

    Follow a build submitted by build_feature in real time. Emits a progress notification on every phase change and resolves with the final result when the build completes or fails. Use immediately after build_feature returns a buildId.

  • retry_build

    Retry a failed build using the same spec (story, acceptance criteria, stack, existing files).

  • cancel_build

    Cancel a running build. Has no effect on builds that already reached a terminal state.

  • continue_build

    Send corrected acceptance criteria to a running build. Applies to components that have not started generating yet; the currently-generating component finishes as originally scoped.

  • get_build

    Get the current state of a build by ID (status and error details).

  • list_builds

    List recent builds for this tenant.

  • get_build_spec

    Get a build's original submitted spec (storyTitle, acceptanceCriteria, stackType, existingFiles, skipTestsFor) without retrying it — useful for inspecting or reusing a prior build's spec as a template.

  • get_build_files

    Retrieve the generated files from a completed build. Returns each file path and full content.

  • notify_files_written

    Index files into the CIL codebase context for a project — for files Codemind itself did not generate (a manual edit, another tool's output). Not needed after a normal build_feature call: a completed build's own output is indexed…

  • test_component

    Run standalone cloud verification on code you already have: give it a component (filePath/exportName/signature) plus acceptance criteria, and it generates a black-box verification test, validates that test against a mechanical stub, then…

  • stream_test

    Follow a test submitted by test_component in real time. Resolves with the pass/fail verdict and the generated verification test content.

  • get_test

    Get the current state of a test by ID (status, pass/fail verdict, generated verification test content) without streaming — useful for polling or inspecting a test after the fact. Use stream_test to follow a test in real time instead.

  • review_code

    Submit code for review: bugs, security issues, silent failures, and style concerns. Give it files (path+content) and/or a unified diff. At least one of files or diff is required — submitting neither is rejected. TWO independent LLM-judge…

  • stream_review

    Follow a review submitted by review_code in real time. Resolves with the findings and the approve/request-changes verdict.

  • get_review

    Get the current state of a review by ID (status, verdict, findings) without streaming — useful for polling or inspecting a review after the fact. Use stream_review to follow a review in real time instead.

  • get_usage_guide

    Get detailed usage guidance for Codemind's tools — how to write effective acceptanceCriteria, when to use patch mode, how webhooks work, what to do when a build declines, common failure patterns unrelated to acceptanceCriteria quality…

  • get_billing_status

    Read-only: your plan, how many verified builds you have used, how many are included and left in the current allowance window, and the paid-balance draw (cents) if you have topped up. Call this to check headroom before a large batch, or to…

  • list_repos

    Lists GitHub repos currently attached to the caller's tenant via Cloud Repo Mode (the GitHub App that automatically triages filed issues into fix PRs), and that the returned `id` field is the repo attachment id to pass into…

  • get_triage_runs

    Lists the issue-triage run history for one attached repo — one row per GitHub issue that was auto-triaged — including terminal status (`pr_opened` means a fix PR was opened and passed the repo's own test suite; `needs_human` means the…

  • get_triage_diagnostics

    Returns the generated fix diff (as file paths and line counts, not full content) and before/after test-run output for one triage run, identified by the triage run id from get_triage_runs (NOT a build id and NOT an issue number)…

  • build_batch

    Submit several pre-decomposed stories in one call and get back one batchId to track, instead of dispatching build_feature N times yourself. Swarm is a Pro plan feature: the maximum batch size depends on the account plan (up to 50; not…

  • get_batch

    Get the aggregate status of a batch submitted via build_batch.

  • stream_batch

    Stream live progress for a batch submitted via build_batch. Polls the batch's aggregate status periodically and emits a progress notification each tick; closes once the batch reaches a terminal status (completed or…

  • build_from_spec

    Submit raw PRD/plan/spec text plus a list of target repos; Codemind LLM-decomposes it into stories (each assigned to one of your declared repos, never an invented one) and dispatches them via the same path build_batch uses. Pass dryRun…

How to connect

Add the server to your MCP client config. Claude Desktop, Cursor and most other clients read this shape:

{
  "mcpServers": {
    "codemind": {
      "type": "http",
      "url": "https://api.codemindhq.dev/mcp?utm_source=mcp-registry&utm_medium=directory&utm_campaign=registry-2026-10-10"
    }
  }
}

Each line is something a program found when it went looking: the registry entry, the server's own answer, a spec that parses. A missing line means we did not find it, not that it does not exist.