cobuilt

dev.cobuiltPublished by cobuilt.devOfficial publisherv1.2.0Updated Nov 6, 2026

Publish honest build receipts to cobuilt.dev: your agent drafts, you approve every field.

VerifiedStreamable HTTPWeb executableKnowledge & MemoryDeveloper Tools

Overview

AI-generated overview

Publishes an approved "build receipt" describing how a project was built and how AI was involved to cobuilt.dev.

What you can do
  • List your cobuilt projects
  • Read the drafting guide and your current receipt for a project
  • Draft a build receipt from the repository and the coding session, asking you for details only you can supply
  • Submit the receipt to cobuilt.dev once you have approved every field
When to use it
Use it when you want a public, honest record of how a project was built and how AI contributed, published from inside an AI coding agent such as Claude Code or Gemini CLI.
Requirements
Remote MCP endpoint at cobuilt.dev over streamable HTTP. A cobuilt.dev account and a personal agent token, sent as an Authorization bearer header. Client setup differs: a Claude Code plugin, a Gemini CLI extension, or a manual MCP configuration for other clients.
Before you install
Requires a personal agent token that grants access to your cobuilt account; it is stored in the client's keychain or credentials file, and uninstalling the Gemini extension does not remove it, so revoke the token in settings to switch access off. Submitting a receipt publishes data to cobuilt.dev, so review every field before approving. A manually added server at the same address can silently replace the plugin's.

Installation

In SourceWeft

  1. Open cobuilt in the dashboard and add it to a workspace.
  2. Connect Authorization token credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/dev.cobuilt%2Fcobuilt/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "cobuilt": {
      "type": "http",
      "url": "https://cobuilt.dev/mcp",
      "headers": {
        "Authorization": "Bearer <YOUR_TOKEN>"
      }
    }
  }
}

README

cobuilt plugin

Publish a build receipt for your project to cobuilt.dev from your AI coding agent. A build receipt is an honest record of how a project was built and how AI was involved. Your agent drafts it from the repository and the session, asks you what only you can answer, and sends nothing until you have approved every field.

Install (Claude Code)

  1. Sign in at cobuilt.dev and create an agent token: Settings → Agent tokens (it starts with cbt_).

  2. In a Claude Code session, run:

    text
    /plugin install cobuilt --marketplace cobuilt-dev/agent-plugins

    Paste your token when the dialog asks for it, then run /reload-plugins.

  3. Say "Publish this project to cobuilt", or run /cobuilt:publish.

If it doesn't work

  • Added cobuilt with claude mcp add before? Run claude mcp remove cobuilt --scope user first. A server you added by hand at the same address silently replaces the plugin's.
  • No cobuilt tools? Run /plugin configure cobuilt@cobuilt, paste your token, then /reload-plugins. Installing from the shell (claude plugin install) doesn't ask for the token.
  • Use Cursor too? Cursor imports the Claude Code plugins you installed (Cursor Settings → Agents → Third-Party Imports, on by default) and lists this one as "cobuilt · Plugin" with an error, because it can't read the token. Switch that entry off in Cursor's MCP list (it stays off after a restart) and set Cursor up with the ~/.cursor/mcp.json snippet from cobuilt.dev/connect.

Install (Gemini CLI)

  1. Create an agent token as above.

  2. In a terminal, run:

    text
    gemini extensions install https://github.com/cobuilt-dev/agent-plugins

    Paste your token when it asks for cobuilt agent token.

  3. Start Gemini CLI and say "Publish this project to cobuilt".

No cobuilt tools? Run gemini extensions config cobuilt, paste your token, then restart Gemini CLI. gemini mcp list should show cobuilt as connected.

Setup for other clients: cobuilt.dev/connect.

What it contains

  • The cobuilt MCP server (https://cobuilt.dev/mcp), sent your token as Authorization: Bearer …. Its tools: list your projects, get the drafting guide, read your current receipt, submit a build receipt.
  • One skill, publish, shared by Claude Code and Gemini CLI. In Claude Code the drafting guide, the project list and your current receipt load without a permission prompt; submitting a receipt always asks you first.

Your token

Claude Code stores the token as a secret: in the macOS Keychain, elsewhere in ~/.claude/.credentials.json. Uninstalling the plugin removes it.

Gemini CLI stores it in your system keychain (on Windows, Credential Manager under "Gemini CLI Extensions cobuilt …"; without a keychain, ~/.gemini/gemini-credentials.json). Uninstalling the extension does not remove it: delete that entry yourself (on Windows: Control Panel → Credential Manager → Windows Credentials → Generic Credentials).

Revoking the token in Settings → Agent tokens on cobuilt.dev is the real off switch.

Privacy

Only the receipt fields you approved are sent. The plugin never sends source code, diffs, file contents, prompts, chat transcripts, secrets, environment variables or local file paths. See the privacy policy and terms.

Releases

Each change bumps the version in every manifest and gets a GitHub Release tagged vX.Y.Z. Changes to the drafting guide and the tools ship on cobuilt.dev and need no plugin update. Changes to this README alone don't bump the version.

server.json lists the server in the official MCP Registry as dev.cobuilt/cobuilt. It carries the same version as the plugin, and a published version can't be republished, so a change to it needs a release and then a new publish.

License

MIT

Source: README.md at commit 1aa6852

Tools

0
This server asks for a credential such as an API key, so SourceWeft could not read its tools without one and has not indexed them.

Version history

1
  1. v1.2.0LatestNov 6, 2026

Score

85% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts