MCP server de cobuilt
Commit 10 nov 2026Publica recibos de construcción honestos en cobuilt.dev para documentar cómo participó la IA en el desarrollo de tu proyecto.
También conocido como cobuilt-dev/agent-plugins, agent-plugins
- Stars
- 0
- Herramientas
- —
- Descargas, 30 días
- —
- Última versión
- 1.2.0
- Último commit
- 10 nov 2026
- Licencia
- MIT
¿Qué es cobuilt MCP?
cobuilt es un MCP server. Publica recibos de construcción honestos en cobuilt.dev para documentar cómo participó la IA en el desarrollo de tu proyecto.
Resumen generado a partir del README del proyecto
Acerca del MCP server de cobuilt
Documentar el papel de la inteligencia artificial en tu desarrollo de software es lo que cobuilt permite a los desarrolladores que usan Claude Code o Gemini CLI. Al generar recibos de construcción, creas un registro honesto de cómo las herramientas de IA contribuyeron a tu proyecto, incluyendo los modelos específicos utilizados y la división de trabajo entre tú y el agente. Este proceso garantiza la transparencia al redactar detalles de tu repositorio y de la sesión antes de requerir tu aprobación manual para cada campo.
Para usar este servidor, debes crear un token de agente que comience con cbt_ desde la configuración de tu cuenta y proporcionarlo durante el proceso de instalación del plugin. El servidor se conecta a un endpoint remoto para gestionar tus proyectos y recibos. Incluye herramientas específicas para listar tus proyectos, acceder a una guía de redacción, leer recibos existentes y enviar nuevos. Debido a que el sistema prioriza la privacidad, se le instruye al agente que nunca envíe código fuente, secretos o transcripciones de chat, y solo transmite los datos finales del recibo después de que hayas revisado y aprobado el contenido.
Qué puedes hacer con él
- 1Revisar documentación de proyectos existentesRecupera el recibo de construcción actual asociado a tu proyecto para ver qué se ha registrado.
Escrito a partir del README del proyecto. Cada caso de uso se verifica con una cita del mismo.
Cómo instalar cobuilt MCP
Formatos verificados el 10 nov 2026Añadir a CursorAñadir a GooseInstalar cobuilt MCP en Claude Code
$ claude mcp add --transport http agent-plugins https://cobuilt.dev/mcpInstalar cobuilt MCP en Cursor
~/.cursor/mcp.json
{
"mcpServers": {
"agent-plugins": {
"url": "https://cobuilt.dev/mcp"
}
}
}Instalar cobuilt MCP en VS Code
.vscode/mcp.json
{
"servers": {
"agent-plugins": {
"type": "http",
"url": "https://cobuilt.dev/mcp"
}
}
}Instalar cobuilt MCP en VS Code CLI
$ code --add-mcp '{"name":"agent-plugins","type":"http","url":"https://cobuilt.dev/mcp"}'Instalar cobuilt MCP en Codex
$ codex mcp add agent-plugins --url https://cobuilt.dev/mcpInstalar cobuilt MCP en Codex config.toml
~/.codex/config.toml
[mcp_servers.agent-plugins] url = "https://cobuilt.dev/mcp"
Instalar cobuilt MCP en Gemini CLI
$ gemini mcp add -s user --transport http agent-plugins https://cobuilt.dev/mcpInstalar cobuilt MCP en Gemini settings.json
~/.gemini/settings.json
{
"mcpServers": {
"agent-plugins": {
"url": "https://cobuilt.dev/mcp",
"type": "http"
}
}
}Verificaciones automáticas
Ejecutado 15 nov 2026Informe completo →Aún no verificado. Un servidor necesita una puntuación de 80, ningún hallazgo grave y suficientes datos para que podamos revisarlo. Cómo funcionan las verificaciones · Qué corregir para obtener más puntos
- Repositorio de origen vinculado y accesiblecobuilt-dev/agent-plugins is public and reachablegithub.com/cobuilt-dev/agent-plugins ↗Aprobado
- El paquete indica este repositorio como su origenNo verificado
- Procedencia de la compilación (atestación de Sigstore)No verificado
- Licencia de código abierto (OSI)MITspdx.org/licenses/MIT.html ↗Aprobado
- Commit o lanzamiento en el último añoLast commit or release 2026-11-10github.com/cobuilt-dev/agent-plugins ↗Aprobado
- OpenSSF ScorecardNo verificado
- El nombre del paquete no es similar a un paquete popularNo verificado
- No hay avisos críticos en el paquete ni en sus dependenciasNo verificado
- Sin instrucciones ocultas para el modelo0 tool descriptions and the README read; no override phrases, credential paths or hidden charactersAprobado
- Las herramientas destructivas están etiquetadasNo verificado
- El endpoint remoto responde al handshake de MCPHTTPS endpoint answered 401 (sign-in required)Aprobado
README
Ver en GitHubcobuilt 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.
Where it works
Publishing works in Claude Code and Gemini CLI, which can send your agent token. In claude.ai chat and Cowork the skill loads but the cobuilt tools don't work, because those apps connect servers through an OAuth sign-in, which cobuilt doesn't offer yet. Open your project in Claude Code to publish.
Try it
Say any of these in your project:
- "Publish this project to cobuilt." Your agent drafts the receipt, asks what it can't know, and shows you the final fields to approve.
- "Show me the build receipt this project has on cobuilt." It finds the project among yours and reads the current receipt. Nothing is changed.
- "Update this project's build receipt on cobuilt." It starts from the published receipt, shows you the old and new text side by side, and warns you before replacing anything.
Install (Claude Code)
-
Sign in at cobuilt.dev and create an agent token: Settings → Agent tokens (it starts with
cbt_). -
In a Claude Code session, run:
/plugin install cobuilt --marketplace cobuilt-dev/agent-pluginsPaste your token when the dialog asks for it, then run
/reload-plugins. -
Say "Publish this project to cobuilt", or run
/cobuilt:publish.
If it doesn't work
- Added cobuilt with
claude mcp addbefore? Runclaude mcp remove cobuilt --scope userfirst. 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. - Added the plugin on claude.ai? It reaches Claude Code as
cobuilt@synced, so run/plugin configure cobuilt@syncedinstead. - 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.jsonsnippet from cobuilt.dev/connect.
Install (Gemini CLI)
-
Create an agent token as above.
-
In a terminal, run:
gemini extensions install https://github.com/cobuilt-dev/agent-pluginsPaste your token when it asks for cobuilt agent token.
-
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 asAuthorization: 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. Your client asks before each cobuilt tool call unless you allow it, and submitting a receipt always asks you first.
Your token
Claude Code stores the token as a secret: in the macOS Keychain, elsewhere in Claude Code's own credentials file in your user folder. 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, in a file in Gemini CLI's own settings folder). 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.
What it sends and where
The plugin runs nothing on your machine: no hooks, scripts or local commands. It talks to one server,
https://cobuilt.dev/mcp, and every request carries your agent token.
- Reading: your agent asks for the drafting guide, your list of projects and a project's current receipt.
- Publishing: after you approve, it sends the receipt: project title, description, links, type and tech stack (for a new project), how AI was involved, the AI tools used, what the AI did, what you did, what went wrong, the agent and model names, and optional summary numbers such as commit counts.
A submitted receipt is public once its project is approved, and a new project is reviewed first. Sending a receipt for an existing project replaces its current one. cobuilt keeps the receipt until you replace it or delete the project.
The plugin's instructions tell your agent never to send source code, diffs, file contents, prompts, chat transcripts, secrets, environment variables or local file paths. Your agent shows you every field first, so check them before you approve. 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
Preguntas sobre cobuilt MCP
¿Cómo agrego cobuilt MCP a Claude Code?
Ejecuta claude mcp add --transport http agent-plugins https://cobuilt.dev/mcp en tu terminal. Añade --scope user para que esté disponible en todos los proyectos.
¿Cómo agrego cobuilt MCP a Cursor?
Abre ~/.cursor/mcp.json y añade el servidor en mcpServers, usando la configuración de Cursor que se muestra en la sección de instalación de arriba.
¿Dónde funciona esto?
Funciona en Claude Code y Gemini CLI. Actualmente no funciona en el chat de claude.ai ni en Cowork porque requieren OAuth.
¿El plugin ejecuta código local?
No, el plugin no ejecuta ningún hook, script o comando local en tu máquina.
¿Qué información se envía al publicar un recibo?
Envía detalles del proyecto como el título, la descripción y el stack tecnológico, junto con detalles sobre la participación de la IA, las herramientas utilizadas y las tareas realizadas por la IA y por el humano.
¿Cómo lo instalo en Claude Code?
Ejecuta /plugin install cobuilt --marketplace cobuilt-dev/agent-plugins en una sesión de Claude Code y pega tu token de agente.