Permite que los agentes de IA encuentren, construyan, prueben y mantengan proveedores de verificación de datos utilizando zkTLS para demostrar puntos de datos del usuario, como saldos de cuentas o número de seguidores.
También conocido como reclaimprotocol/developer-tools, developer-tools, @reclaimprotocol/agent
- Stars
- 1
- Herramientas
- —
- Descargas, 30 días
- —
- Última versión
- 0.1.46
- Último commit
- 13 nov 2026
- Licencia
- MIT
¿Qué es Reclaim Protocol Builder MCP?
Reclaim Protocol Builder es un MCP server. Permite que los agentes de IA encuentren, construyan, prueben y mantengan proveedores de verificación de datos utilizando zkTLS para demostrar puntos de datos del usuario, como saldos de cuentas o número de seguidores.
Resumen generado a partir del README del proyecto
Acerca del MCP server de Reclaim Protocol Builder
Construir proveedores de verificación de datos utilizando zkTLS es lo que los desarrolladores logran con el Reclaim Protocol Builder. Este MCP server permite que los agentes de IA encuentren, construyan, prueben y mantengan herramientas que demuestren puntos de datos específicos del usuario, como saldos de cuentas, historiales de pedidos o número de seguidores en redes sociales. Al conectarse a un agente de codificación de IA a través de stdio local, el servidor habilita flujos de trabajo automatizados para gestionar la autenticación, la captura del navegador y la síntesis de pruebas.
Para usar este servidor, debes tener instalado Node.js 22.12 o posterior y un navegador Chrome, Chromium o Edge local, ya que el servidor controla un navegador real para capturar el tráfico y facilitar los inicios de sesión. El servidor se distribuye a través del paquete npm @reclaimprotocol/agent. Durante la primera ejecución de una prueba, el sistema descargará automáticamente aproximadamente 280 MB de archivos de circuitos ZK. Es compatible con varios clientes, incluyendo Claude Code, Claude Desktop, Cursor, GitHub Copilot y Windsurf.
Qué puedes hacer con él
- 1Crear un nuevo proveedor de verificaciónPide a tu agente que construya un proveedor que demuestre una métrica específica, como el número de seguidores en GitHub.
- 2Integrar la verificación en una aplicaciónUsa la herramienta start_integration para seguir un plan guiado para añadir la verificación de Reclaim a tu software.
- 3Aprender detalles de la implementación del protocoloSolicita orientación técnica sobre temas como la detección de login o decisiones de privacidad OPRF usando la herramienta how_it_works.
- 4Mantener proveedores de verificación existentesUsa el agente para inspeccionar solicitudes capturadas, verificar sesiones de verificación y publicar actualizaciones para los proveedores.
Escrito a partir del README del proyecto. Cada caso de uso se verifica con una cita del mismo.
Cómo instalar Reclaim Protocol Builder MCP
Formatos verificados el 10 nov 2026Añadir a CursorAñadir a GooseInstalar Reclaim Protocol Builder MCP en Claude Code
$ claude mcp add developer-tools -- npx -y @reclaimprotocol/agentInstalar Reclaim Protocol Builder MCP en Cursor
~/.cursor/mcp.json
{
"mcpServers": {
"developer-tools": {
"command": "npx",
"args": [
"-y",
"@reclaimprotocol/agent"
]
}
}
}Instalar Reclaim Protocol Builder MCP en VS Code
.vscode/mcp.json
{
"servers": {
"developer-tools": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@reclaimprotocol/agent"
]
}
}
}Instalar Reclaim Protocol Builder MCP en VS Code CLI
$ code --add-mcp '{"name":"developer-tools","type":"stdio","command":"npx","args":["-y","@reclaimprotocol/agent"]}'Instalar Reclaim Protocol Builder MCP en Claude Desktop
claude_desktop_config.json
{
"mcpServers": {
"developer-tools": {
"command": "npx",
"args": [
"-y",
"@reclaimprotocol/agent"
]
}
}
}Instalar Reclaim Protocol Builder MCP en Codex
$ codex mcp add developer-tools -- npx -y @reclaimprotocol/agentInstalar Reclaim Protocol Builder MCP en Codex config.toml
~/.codex/config.toml
[mcp_servers.developer-tools] command = "npx" args = ["-y", "@reclaimprotocol/agent"]
Instalar Reclaim Protocol Builder MCP en Gemini CLI
$ gemini mcp add -s user developer-tools npx -- -y @reclaimprotocol/agentInstalar Reclaim Protocol Builder MCP en Gemini settings.json
~/.gemini/settings.json
{
"mcpServers": {
"developer-tools": {
"command": "npx",
"args": [
"-y",
"@reclaimprotocol/agent"
]
}
}
}Configuración
CODEX_HOME
| Nombre | Descripción | Tipo |
|---|---|---|
| CODEX_HOME | — |
Verificaciones automáticas
Ejecutado 14 nov 2026Informe completo →Pasó nuestras verificaciones automáticas. Esto no es una auditoría de seguridad: lee el código y dale al servidor el acceso más limitado que necesite. Cómo funcionan las verificaciones
- Repositorio de origen vinculado y accesiblereclaimprotocol/developer-tools is public and reachablegithub.com/reclaimprotocol/developer-tools ↗Aprobado
- El paquete indica este repositorio como su origen@reclaimprotocol/agent names reclaimprotocol/developer-tools as sourcenpmjs.com/package/@reclaimprotocol/agent ↗Aprobado
- Procedencia de la compilación (atestación de Sigstore)No build attestation published for this releaseNo 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-11github.com/reclaimprotocol/developer-tools ↗Aprobado
- OpenSSF ScorecardNo verificado
- El nombre del paquete no es similar a un paquete popularNo popular package one edit away from @reclaimprotocol/agentAprobado
- No hay avisos críticos en el paquete ni en sus dependenciasthe package checked; no critical advisoryosv.dev ↗Aprobado
- 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 MCPNo verificado
README
Ver en GitHubReclaim developer tools
Builder MCP discovery
Install the Reclaim Protocol Builder MCP for https://build.reclaimprotocol.org using the published @reclaimprotocol/agent package. This repository includes client plugins, a Gemini CLI extension, agent documentation, and registry submission metadata.
- Product integration guide
- Supported verification request patterns
- Registration status and submission materials
- Agent installation instructions
All Builder MCP submissions identify @reclaimprotocol/agent over local stdio. The separate Letters beta is outside this registration campaign.
Install the Reclaim MCP server into your AI coding agent.
Reclaim Protocol lets your app verify data points about its users — a follower count, an account balance, an order history. The MCP server gives your agent the tools to find, build, test, and fix the data verification providers that do the verifying: it inspects and replays captured requests, checks verification sessions, evaluates proofs, and publishes provider updates.
The server is published to npm as @reclaimprotocol/agent (bin: reclaim-mcp-server). This repository carries plugins and marketplaces for clients that support them, plus direct install instructions for every other client.
Source packages and contributing
The source for @reclaimprotocol/client and @reclaimprotocol/agent is in packages/, and it's developed here.
See CONTRIBUTING.md to report a bug, propose a fix, or report a vulnerability. Maintainers: see docs/maintainers.md for the repository settings.
Contents
- Prerequisites
- Claude Code
- Claude Desktop
- GitHub Copilot / VS Code
- Cursor
- OMP
- OpenCode
- Codex
- Antigravity
- Windsurf, Cline, and other MCP clients
- Optional environment
- Using it from your agent
- Maintaining this repository
Prerequisites
- Node.js 22.12 or later. This matches the
>=22.12.0engine requirement of the published@reclaimprotocol/agentpackage. The server starts withnpx, which comes with Node.js. - A local Chrome, Chromium, or Edge. The server drives a real browser to capture traffic and to sign you in.
The first time you run a proof, the server downloads the ZK circuit files it needs, about 280 MB. Allow a moment for that first proof. The download happens at the first proof, not at install time, so the server starts immediately.
Every client below runs the same stdio MCP server:
npx -y --package=@reclaimprotocol/agent reclaim-mcp-server
The long
--package=form is deliberate. The short-pcollides with the-p/claude mcp add, which silently swallows the command.
Claude Code
Install the plugin from the marketplace. In a terminal, run:
claude plugin marketplace add reclaimprotocol/developer-tools
claude plugin install reclaim@reclaim
Then restart Claude Code. To confirm that the server connected, run /mcp, which lists connected servers.
If you ask your agent to install the plugin, it runs these commands for you. Installing a plugin adds third-party code, so permission checks (for example, Claude Code auto mode) can block them. If that happens, run the commands yourself. In Claude Code, type each one in the prompt with a ! prefix.
Use the plugin instead of the manual claude mcp add below unless you have a specific reason not to.
Advanced fallback — add the MCP server directly. Skip this if you installed the plugin:
# -s user installs it for your user, across projects
claude mcp add reclaim -s user -- npx -y --package=@reclaimprotocol/agent reclaim-mcp-server
Or add it to .mcp.json yourself:
{
"mcpServers": {
"reclaim": {
"command": "npx",
"args": ["-y", "--package=@reclaimprotocol/agent", "reclaim-mcp-server"]
}
}
}
If you add the server this way, run /mcp to confirm that it connected.
Troubleshoot Claude Code auto mode
Auto mode can block destructive Reclaim tools. If a Reclaim tool call is blocked, approve it in /permissions (Recently denied tab). Or add the tool to permissions.allow in ~/.claude/settings.json. Plugin tool names look like mcp__plugin_reclaim_reclaim__<tool>. Allow specific tools instead of a wildcard, because some tools delete organization resources.
Claude Desktop
Add the same mcpServers entry through the app's MCP settings, then fully quit and reopen Claude Desktop. Closing the window isn't enough, because the app re-reads the config only on a full restart.
GitHub Copilot / VS Code
This repository includes a native GitHub Copilot marketplace and plugin. Install it from Copilot CLI:
copilot plugin marketplace add reclaimprotocol/developer-tools
copilot plugin install reclaim@reclaim
To pick up a newer version later, run:
copilot plugin marketplace update reclaim
copilot plugin update reclaim
In VS Code, enable agent plugins and add this repository to the chat.plugins.marketplaces setting:
{
"chat.plugins.enabled": true,
"chat.plugins.marketplaces": ["reclaimprotocol/developer-tools"]
}
Then run Chat: Open Customizations, open Plugins, select Browse Marketplace, and install reclaim from the reclaim marketplace. To use VS Code's unified experimental Discover view instead, also enable chat.customizations.marketplace.enabled.
Cursor
This repository is a Cursor marketplace. Add it from the Cursor CLI:
agent plugin marketplace add https://github.com/reclaimprotocol/developer-tools.git
Then open Cursor's Customize page (or /plugin in Cursor Agent), find reclaim in the reclaim marketplace, and install it at user or project scope. Cursor does not currently expose a non-interactive plugin-install command.
To refresh the catalog manually, run agent plugin marketplace update reclaim. Cursor Teams and Enterprise admins can instead import this repository as a team marketplace and enable Auto Refresh so pushes are re-indexed automatically.
Advanced fallback — add the MCP server directly. Skip this if you installed the plugin. Add to ~/.cursor/mcp.json (global) or .cursor/mcp.json (project):
{
"mcpServers": {
"reclaim": {
"command": "npx",
"args": ["-y", "--package=@reclaimprotocol/agent", "reclaim-mcp-server"]
}
}
}
OMP
Install the plugin from the native OMP marketplace:
omp plugin marketplace add reclaimprotocol/developer-tools
omp plugin install reclaim@reclaim
Enable automatic catalog and plugin upgrades:
omp config set marketplace.autoUpdate auto
To update immediately instead, run:
omp plugin marketplace update reclaim
omp plugin upgrade reclaim@reclaim
OMP can also read the Claude marketplace in this repository as a compatibility fallback, but the native .omp-plugin/marketplace.json is preferred.
OpenCode
OpenCode does not currently have a Git marketplace format for MCP plugins. Its distributable plugins are npm modules, and its documented plugin API does not provide a stable way for a package to register an MCP server. Use the native MCP configuration instead.
Add to opencode.json (project) or ~/.config/opencode/opencode.json (global):
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"reclaim": {
"type": "local",
"command": ["npx", "-y", "--package=@reclaimprotocol/agent", "reclaim-mcp-server"],
"enabled": true
}
}
}
The package reference is intentionally unpinned. OpenCode starts the command through npx, which resolves the current @reclaimprotocol/agent release without requiring a marketplace manifest update.
Codex
Install the plugin from the marketplace:
codex plugin marketplace add reclaimprotocol/developer-tools
codex plugin add reclaim@reclaim
To pick up a newer plugin version later, run codex plugin marketplace upgrade reclaim.
Advanced fallback — add the MCP server directly. Skip this if you installed the plugin:
# writes ~/.codex/config.toml
codex mcp add reclaim -- npx -y --package=@reclaimprotocol/agent reclaim-mcp-server
Or add it to ~/.codex/config.toml yourself. Codex uses TOML, not JSON:
[mcp_servers.reclaim]
command = "npx"
args = ["-y", "--package=@reclaimprotocol/agent", "reclaim-mcp-server"]
Antigravity
Install the GitHub-hosted Antigravity plugin:
agy plugin install https://github.com/reclaimprotocol/developer-tools
Antigravity currently supports only its curated official marketplace, not third-party marketplace catalogs. This repository includes the root plugin.json and mcp_config.json needed for direct GitHub installation and is ready to submit through Antigravity's marketplace interest form. Until it is accepted into the official catalog, update a direct install by reinstalling it from the GitHub URL.
Windsurf, Cline, and other MCP clients
These all use the standard mcpServers shape. Add a server through the app's MCP settings, or its mcp/mcpServers config file, with:
{
"mcpServers": {
"reclaim": {
"command": "npx",
"args": ["-y", "--package=@reclaimprotocol/agent", "reclaim-mcp-server"]
}
}
}
Using it from your agent
The MCP server gives your agent the tools. The plugin also includes the adding-reclaim-verification skill, which tells your agent which tool to start with.
To add verification to an app, the main entry is the start_integration tool. The Reclaim dashboard gives you a prompt that calls it. Your agent follows the plan it returns: prove the provider first, then write the app code.
For guidance on a specific topic, your agent calls the how_it_works tool. It serves the capture, prove, and publish guide one topic at a time: login detection, choosing an authentication-bound endpoint, the OPRF privacy decision, publishing, and troubleshooting. Called with no arguments, it returns the overview and the topic index.
You can also ask in plain language. For example:
"Use Reclaim to create a provider that proves my GitHub follower count."
Your agent handles authentication, browser capture, provider synthesis, replay, the zkTLS proof, and publishing. Your only manual steps are signing in when the browser window opens and confirming the value you want to prove.
Maintaining this repository
.claude-plugin/marketplace.json Claude marketplace metadata + the plugin entry
.agents/plugins/marketplace.json Codex marketplace + the plugin entry
.cursor-plugin/marketplace.json Cursor marketplace metadata + the plugin entry
.github/plugin/marketplace.json GitHub Copilot marketplace metadata + plugin entry
.omp-plugin/marketplace.json OMP marketplace metadata + the plugin entry
plugin.json Antigravity plugin manifest
mcp_config.json Antigravity MCP configuration
reclaim/.claude-plugin/plugin.json Claude plugin manifest
reclaim/.codex-plugin/plugin.json Codex plugin manifest
reclaim/.cursor-plugin/plugin.json Cursor plugin manifest
reclaim/.github/plugin/plugin.json GitHub Copilot plugin manifest
reclaim/.mcp.json The shared stdio command used by marketplace plugins
reclaim/skills/adding-reclaim-verification/SKILL.md
Skill that routes agents to the MCP tools
scripts/bump-version.ts Version bump (below)
Every plugin runs the published @reclaimprotocol/agent through npx, so the version in the manifests tracks that package. The root package.json version is the release version. To release, edit it and run (Node 22.19 or later):
npm run version:bump # propagate the root version
npm run version:bump -- 0.2.0 # or set the root version and propagate it
It sets both package versions, pins the agent's @reclaimprotocol/client dependency, rewrites every version field in the Claude, Cursor, GitHub Copilot, and OMP marketplace catalogs, the Antigravity and Gemini manifests, and each versioned client plugin manifest, and refreshes the lockfile. The Codex marketplace has no version field. CI fails if any of these drift from the root version. Merging the version change runs release.yml, which publishes the packages to npm and the MCP Registry. See distribution/npm-release.md.
Validate the manifests before committing:
claude plugin validate . # Claude marketplace manifest
claude plugin validate ./reclaim # Claude plugin manifest
agy plugin validate . # Antigravity plugin
omp plugin marketplace add "$PWD" # add the checkout, then use the dry-run below
omp plugin install --dry-run reclaim@reclaim
omp plugin marketplace remove reclaim
Codex has no validate command. Install from your checkout in a throwaway Codex home instead:
export CODEX_HOME="$(mktemp -d)"
codex plugin marketplace add "$PWD"
codex plugin add reclaim@reclaim
codex mcp list # lists the reclaim server
Preguntas sobre Reclaim Protocol Builder MCP
¿Cómo agrego Reclaim Protocol Builder MCP a Claude Code?
Ejecuta claude mcp add developer-tools -- npx -y @reclaimprotocol/agent en tu terminal. Añade --scope user para que esté disponible en todos los proyectos.
¿Cómo agrego Reclaim Protocol Builder 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.
¿Qué hace el Reclaim MCP server?
Proporciona herramientas para que los agentes de IA inspeccionen y reproduzcan solicitudes capturadas, verifiquen sesiones de verificación, evalúen pruebas y publiquen actualizaciones de proveedores.
¿El servidor requiere una descarga grande?
La primera vez que ejecutes una prueba, el servidor descargará aproximadamente 280 MB de archivos de circuitos ZK.
¿Cómo puedo usar Reclaim para crear un nuevo proveedor?
Puedes pedirle a tu agente en lenguaje natural que cree un proveedor, y este se encargará de la autenticación, la captura del navegador, la síntesis del proveedor, la reproducción y la publicación.