Pack local or remote codebases into AI-friendly files that LLMs and coding agents can read or search
Nothing to run from here
Codemind is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
26
tools declared
—
trust score
remote
at its publisher
—
calls last 7d
What it does
Hand routine JS/TS tasks to Codemind from your agent. $0.10 per verified build; failures are free.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http codemindhq-codemind-mcp 'https://api.codemindhq.dev/mcp?utm_source=mcp-registry&utm_medium=directory&utm_campaign=registry-2026-10-10'
# 2 — ask your agent for something these tools do
# create_free_account, build_feature, stream_build and 23 more
Codemind costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
COAll 1 server
codemindhq1 server
1 category
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
Claude Codedeclared by this listing
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http codemindhq-codemind-mcp 'https://api.codemindhq.dev/mcp?utm_source=mcp-registry&utm_medium=directory&utm_campaign=registry-2026-10-10'Reconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it answers at its publisher’s own address: this marketplace is not in the path, so there is no key of ours to hold and no card to add.
What it writes
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
What you approve
26 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
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 tenantId and a bearer token (apiKey) usable immediately for build_feature and every other tool. The account is anonymous (no identity attached) until a person opens t
| Parameter | Type | Required | Notes |
|---|---|---|---|
| utm_source | string | no | Optional marketing source tag, e.g. "producthunt". Lowercase letters, digits, "_", "." and "-", max 64 characters; anything else is ignored. |
| utm_medium | string | no | Optional marketing medium tag, e.g. "launch". Same format as utm_source. |
| utm_campaign | string | no | Optional campaign tag, e.g. "ph-2026-10-08". Same format as utm_source. |
| invite | string | no | Optional invite code from an invite link your human gave you. Case-sensitive; pass it exactly as given. An invalid or used-up code is ignored. |
| ph_did | string | no | Optional web visitor id from a setup link or command your human gave you (--ph-did). Pass it exactly as given; an invalid value is ignored. |
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 with the returned buildId to follow progress. Call get_usage_guide for detailed usage guidance. IMPORTANT: if this tool errors, surface the error to the us
| Parameter | Type | Required | Notes |
|---|---|---|---|
| storyTitle | string | yes | Short title used to organize this build. |
| acceptanceCriteria | string | yes | Detailed requirements — function signatures, file paths, edge cases. Used verbatim to generate the implementation. |
| stackType | string | yes | Runtime target stack (free text). JavaScript/TypeScript only at launch, e.g. "worker", "typescript", "node", "react". python, go, swift-ios, kotlin-android and rust are rejected with UNSUPPORTED_STACK |
| projectId | string | no | Opaque identifier grouping related builds for CIL codebase context — omit to skip CIL entirely. |
| examples | array | no | OPTIONAL call → result examples, turned directly into test cases (no LLM), so the build is verified against exactly these. Each: { target: repo-relative .ts/.tsx path of the file under test, call: a T |
| skipTestsFor | array | no | Repo-relative source paths (max 20) to opt OUT of test-file delivery for — e.g. the repo has no test framework and a scaffolded test file would be unwanted. Verification still ALWAYS runs against ever |
| existingFiles | array | no | PATCH MODE — pass current content of files being modified. Without this, codegen creates new files instead of editing existing ones. |
| webhookUrl | string | no | HTTPS URL to POST a signed payload to when the build reaches a terminal state (completed/failed). Must be supplied together with webhookSecret. |
| webhookSecret | string | no | Shared secret (16-256 chars) used to HMAC-SHA256-sign the webhook payload, sent in the x-codemind-v2-signature header. Must be supplied together with webhookUrl. Never echoed back. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| buildId | string | yes | The buildId returned by build_feature. |
Retry a failed build using the same spec (story, acceptance criteria, stack, existing files).
| Parameter | Type | Required | Notes |
|---|---|---|---|
| buildId | string | yes | ID of the failed build to retry. |
Cancel a running build. Has no effect on builds that already reached a terminal state.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| buildId | string | yes | ID of the build to cancel. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| buildId | string | yes | ID of the running build to steer. |
| correctedAcceptanceCriteria | string | yes | The new, complete acceptance criteria — replaces the original for all not-yet-started components. |
Get the current state of a build by ID (status and error details).
| Parameter | Type | Required | Notes |
|---|---|---|---|
| buildId | string | yes | The build ID. |
List recent builds for this tenant.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| limit | number | no | Max builds to return (default 20, max 50). |
| offset | number | no | Pagination offset (default 0). |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| buildId | string | yes | The build ID. |
Retrieve the generated files from a completed build. Returns each file path and full content.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| buildId | string | yes | The build ID. |
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 automatically when projectId was supplied.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| projectId | string | yes | Opaque project identifier — same value used in build_feature calls for this codebase. |
| files | array | yes | Files to index, ≤10 files / ≤700KB total. |
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 executes your REAL code against it in the cloud (isolate or container, per stack). No code generation happens here — use build_feature for that. Returns a testId
| Parameter | Type | Required | Notes |
|---|---|---|---|
| stackType | string | yes | Runtime target stack (JavaScript/TypeScript only at launch), e.g. "worker", "typescript", "node", "react". |
| component | object | yes | MUST match the real code exactly — the generated verification test imports/calls by these exact names. |
| code | string | yes | The REAL implementation to test. Never shown to the model that generates the verification test. |
| acceptanceCriteria | string | yes | What the code must do — the verification test is generated from this alone. |
| contextFiles | array | no | Optional ambient read-only files the code under test may import. |
Follow a test submitted by test_component in real time. Resolves with the pass/fail verdict and the generated verification test content.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| testId | string | yes | The testId returned by test_component. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| testId | string | yes | The testId returned by test_component. |
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 passes review it (a general correctness/security pass and a dedicated silent-failure pass) and their findings are merged into one verdict. For a genuinely useful
| Parameter | Type | Required | Notes |
|---|---|---|---|
| files | array | no | Full file contents to review. Provide when you want the reviewer to see complete files, not just a diff. |
| diff | string | no | A unified diff. The reviewer weights changed lines most heavily. Combined with files, must not exceed 150,000 characters. |
| context | string | no | Optional story/PR description to give the reviewer intent context. |
| conventions | string | no | This project's CLAUDE.md and/or RULES.md content (or the relevant excerpt). Strongly recommended when available — both review passes treat this as authoritative: a finding that violates a stated rule |
| relatedFiles | array | no | Existing files for cross-reference ONLY — never diffed, never themselves the subject of a finding. Supply an interface the change implements, a caller of a changed function, or a sibling file showing |
Follow a review submitted by review_code in real time. Resolves with the findings and the approve/request-changes verdict.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| reviewId | string | yes | The reviewId returned by review_code. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| reviewId | string | yes | The reviewId returned by review_code. |
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, and how to recover from an auth error without losing an identified account. Call this before build_feature/test_component/review_code if you are unfamiliar with thi
| Parameter | Type | Required | Notes |
|---|---|---|---|
| topic | string | no | Which part of Codemind usage to get guidance on. Defaults to overview. |
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 learn why a build was rejected for allowance.
No parameter schema on file.
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.
No parameter schema on file.
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 issue wasn't judged auto-fixable; failed means the triage/build/verify pipeline errored). The repoAttachmentId is the attachment id returned by list_repos, N
| Parameter | Type | Required | Notes |
|---|---|---|---|
| repoAttachmentId | string | yes | The repo attachment id, as returned by list_repos (not an owner/repo string). |
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). stdout/stderr are tail-truncated because test failure summaries appear at the end of output, not the install noise at the start. Full file contents are available separatel
| Parameter | Type | Required | Notes |
|---|---|---|---|
| triageRunId | string | yes | The triage run id, as returned by get_triage_runs (the first token of each line), not the build id or issue number. |
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 available on Free or the base pay-as-you-go account); a batch over the limit is refused with BATCH_SIZE_LIMIT_EXCEEDED and the limit. Each item has the same shape as
| Parameter | Type | Required | Notes |
|---|---|---|---|
| items | array | yes | 1 to 50 stories to dispatch. |
| idempotencyKey | string | no | A repeat call with the same key returns the original batchId instead of dispatching again. |
| webhookUrl | string | no | Fires once when every item in the batch reaches a terminal state. Must be supplied together with webhookSecret. |
| webhookSecret | string | no | HMAC-SHA256 signing secret (16-256 chars) for the aggregate completion webhook. Must be supplied together with webhookUrl. |
Get the aggregate status of a batch submitted via build_batch.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| batchId | string | yes | — |
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 completed_with_failures). Call get_batch instead for a single point-in-time snapshot.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| batchId | string | yes | — |
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: true to see the decomposed story list without dispatching anything, useful for reviewing before committing. Recommended for a first-time caller: review with dryRun
| Parameter | Type | Required | Notes |
|---|---|---|---|
| specText | string | yes | — |
| repos | array | yes | — |
| maxStories | number | no | Default 20, hard ceiling 50. |
| dryRun | boolean | no | — |
| webhookUrl | string | no | — |
| webhookSecret | string | no | — |
Free
$0 forever
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install Codemind or to call it, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: —
—Grade not published
No rule-by-rule report on file for this release
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
This listing is an address its publisher runs, and you connect to it directly — this marketplace is not in the path. The scanner reads packages and public source, and an address is neither. So there is no grade — not a withheld one, an unmeasured one.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 1.0.0.
1.0.0
undated
latestNo release note was published with this version.
—
no reviews yet
Who can review
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Sign in to write one
Any signed-in account that does not publish Codemind can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
No reviews yet
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.