MCP server de Peer
Commit 12 nov 2026Permite que un cliente de IA interactúe con el protocolo Peer, el mercado, el checkout y los flujos de trabajo de Peer Cash a través de varios perfiles MCP.
También conocido como zkp2p/peer-cli, peer-cli
- Stars
- 0
- Herramientas
- —
- Descargas, 30 días
- —
- Última versión
- 0.4.1
- Último commit
- 12 nov 2026
- Licencia
- MIT
¿Qué es Peer MCP?
Peer es un MCP server. Permite que un cliente de IA interactúe con el protocolo Peer, el mercado, el checkout y los flujos de trabajo de Peer Cash a través de varios perfiles MCP.
Resumen generado a partir del README del proyecto
Acerca del MCP server de Peer
Este servidor permite a los desarrolladores que utilizan clientes de IA interactuar con el protocolo Peer, el mercado y los flujos de trabajo de Peer Cash. Proporciona una interfaz estructurada para gestionar operaciones financieras complejas como cotizaciones, registro de beneficiarios y ciclos de vida de depósitos. Los usuarios pueden elegir entre tres perfiles MCP distintos según sus necesidades de seguridad: read-only para datos del protocolo y de Peer Cash, cash para flujos de trabajo con custodia separada que preparan transacciones sin firmar, y full para capacidades completas de operador, incluyendo herramientas de escritura genéricas.
Para usar el servidor, puedes ejecutarlo localmente vía stdio mediante el paquete npm peer-protocol-cli o conectarte a la versión alojada a través de HTTP. Las instalaciones locales permiten comandos que mutan el estado al proporcionar una clave privada mediante la variable de entorno PEER_PRIVATE_KEY o una ruta de wallet. El servidor admite varios entornos, incluyendo producción, preproducción y staging, y requiere Node.js 22 o superior para configuraciones locales. Gestiona diversas tareas que van desde depósitos y retiros en StakeVault hasta la exploración del mercado en Peerlytics y transferencias de USDC.
Qué puedes hacer con él
- 1Solicitud de cotizaciones de pagos cross-chainUn agente de IA puede obtener una cotización y rastrear una ruta cross-chain hacia Base USDC.
- 2Gestión de transacciones de Peer CashLos desarrolladores pueden usar el perfil cash para preparar transacciones de depósito y aprobaciones sin firmar.
- 3Inspección de datos del mercado y del protocoloUn agente puede usar el perfil read-only para visualizar el historial del mercado en Peerlytics e información del protocolo.
- 4Ejecución de operaciones completas del protocoloUn proceso local con una clave privada puede realizar tareas completas de operador, incluyendo la gestión de StakeVault.
Escrito a partir del README del proyecto. Cada caso de uso se verifica con una cita del mismo.
Cómo instalar Peer MCP
Formatos verificados el 10 nov 2026Añadir a CursorAñadir a GooseInstalar Peer MCP en Claude Code
$ claude mcp add --transport http peer-cli https://mcp.peer.xyz/mcpInstalar Peer MCP en Cursor
~/.cursor/mcp.json
{
"mcpServers": {
"peer-cli": {
"url": "https://mcp.peer.xyz/mcp"
}
}
}Instalar Peer MCP en VS Code
.vscode/mcp.json
{
"servers": {
"peer-cli": {
"type": "http",
"url": "https://mcp.peer.xyz/mcp"
}
}
}Instalar Peer MCP en VS Code CLI
$ code --add-mcp '{"name":"peer-cli","type":"http","url":"https://mcp.peer.xyz/mcp"}'Instalar Peer MCP en Codex
$ codex mcp add peer-cli --url https://mcp.peer.xyz/mcpInstalar Peer MCP en Codex config.toml
~/.codex/config.toml
[mcp_servers.peer-cli] url = "https://mcp.peer.xyz/mcp"
Instalar Peer MCP en Gemini CLI
$ gemini mcp add -s user --transport http peer-cli https://mcp.peer.xyz/mcpInstalar Peer MCP en Gemini settings.json
~/.gemini/settings.json
{
"mcpServers": {
"peer-cli": {
"url": "https://mcp.peer.xyz/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 accesiblezkp2p/peer-cli is public and reachablegithub.com/zkp2p/peer-cli ↗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-12github.com/zkp2p/peer-cli ↗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 MCPinitialize answered with protocol 2025-06-18 in 462 msAprobado
README
Ver en GitHubpeer-cli
The canonical agent interface for Peer: one JSON-first CLI, local and hosted MCP servers, and one generated contract for protocol, indexer, market, checkout, and Peer Cash workflows.
- Docs and agent-readable text: https://agents.peer.xyz
- Exact CLI schemas:
agents/tool-catalog.json - Error contract:
agents/error-catalog.json - Runtime profiles and counts:
agents/runtime-manifest.json
The generated files come from the runtime registries. Do not hand-maintain a second command list in documentation.
Install
Node.js 22 or newer is required.
The package is peer-protocol-cli; do not install the unrelated unscoped
peer-cli package.
npm install --global peer-protocol-cli@0.4.1
peer --help
Run without a global install:
npx -y peer-protocol-cli@0.4.1 quote --from USD --amount 100 --platform wise
Successful output is JSON by default. Errors always use the canonical JSON
error envelope on stderr. --format table changes successful human-facing
output only.
Safety model
Read commands execute immediately. Commands that can mutate state return a
transaction or API preview first and execute only when the process receives
--yes.
Signer material resolves from PEER_PRIVATE_KEY or --wallet-path. Passing a
private key on the command line is supported but visible in process listings;
prefer the environment or an owner-readable wallet file. Persistent config and
checkout caches are written with owner-only permissions.
Never start a write-capable MCP process with --yes unless every write tool in
that process is intentionally allowed to broadcast without a second CLI
preview.
MCP profiles
peer mcp requires one of three explicit profiles:
read-only— default protocol reads plus Peer Cash reads. No signing or broadcasting.cash— the complete custody-separatedpeer_cash_*surface. It prepares unsigned transaction plans but never accepts a private key, signs, or broadcasts.full— every generic CLI-backed MCP tool plus Peer Cash. Generic write tools still preview unless the MCP process was started with global--yes.
The current tool counts are generated in agents/runtime-manifest.json.
{
"mcpServers": {
"peer": {
"command": "npx",
"args": [
"-y",
"peer-protocol-cli@0.4.1",
"mcp",
"--profile",
"read-only"
]
}
}
}
Use --profile cash for the portable Peer Cash workflow or --profile full
for the complete operator surface.
The hosted MCP server exposes only the read-only profile over Streamable HTTP:
https://mcp.peer.xyz/mcp
Run the same transport yourself with peer mcp --transport http. HTTP refuses
the cash and full profiles; those authority-bearing profiles remain local
stdio processes.
Peer Cash
The retired standalone peer-cash-mcp server now lives here. Its tool names and
custody boundary are unchanged:
peer_cash_capabilities/peer_cash_source_capabilities— fetch live payout rails and Relay-supported source chains and tokens.peer_cash_fill_stats/peer_cash_buyer— inspect historical fill evidence and buyer protocol history.peer_cash_quote_source/peer_cash_relay_status— quote and track a cross-chain route into Base USDC without granting signer authority.peer_cash_estimate— estimate fiat received at the current oracle rate.peer_cash_prepare— return ordered unsigned approval and deposit transactions.peer_cash_finalize— resolve a confirmed receipt into a durabledepositId.peer_cash_order/peer_cash_orders— resume and inspect orders.peer_cash_prepare_access_policy,peer_cash_prepare_withdraw, andpeer_cash_prepare_top_up— prepare follow-up transactions.
Base USDC amounts are decimal strings in 6-decimal base units: 100 USDC is
100000000. Estimates are not locked quotes; the binding Chainlink rate
resolves when a buyer fills.
Install the packaged portable skill from
skills/peer-cash/SKILL.md when the agent host
supports Agent Skills.
Configuration
Configuration resolves in this order:
- CLI flags
- environment variables
~/.peer/config.json- runtime defaults
Common settings:
PEER_ENV:production,preproduction, orstagingPEER_PRIVATE_KEY/PEER_WALLET_PATH: signer material for generic write commandsPEER_RPC_URL: Base RPC overridePEER_API_KEY: Curator API key when requiredPEER_INDEXER_API_KEY/PEER_INDEXER_URL: indexer overridesPEER_MARKET_API_KEY/PEER_MARKET_BASE_URL: Peerlytics accessPEER_PAY_API_KEY/PEER_PAY_BASE_URL: hosted checkout accessPEER_BASE_API_URL: Curator override. Defaults followPEER_ENV:api.zkp2p.xyz,api-preprod.zkp2p.xyz, orapi-staging.zkp2p.xyz.PEER_CASH_RPC_URL,PEER_CASH_API_KEY,PEER_CASH_REFERRAL_CODE, andPEER_CASH_REFERRER: cash-profile overrides
Use peer config show, set, unset, and reset for persistent local
settings. peer config show masks secret values. Prefer environment variables
for credentials.
Command families
The CLI covers:
- quotes, payee registration, and payee-hash resolution
- deposit lifecycle, payment methods, currencies, oracle configuration, and batch updates
- intents, pre-intent hooks, fulfillment, release, and cleanup
- StakeVault deposits, withdrawals, authorization, indexed freshness, and matured chargeback releases
- IntentGuardian policy, live extension quotes, payer funding, and preview-first intent extension
- ProtocolViewer and indexer reads, including a raw GraphQL escape hatch
- vaults, rate managers, delegation, fees, and snapshots
- Peerlytics market, explorer, history, attribution, and API-key operations
- USDC balances and transfers
- hosted checkout creation, reads, cancellation, and local resume cache
- local config and environment inspection
Run peer --help, peer <family> --help, or inspect the generated tool catalog
for the exact current paths, flags, schemas, auth requirements, and danger
markers.
Every command also accepts --params <json> and --params-file <path>. Typed
flags override raw values.
Development
This repository uses npm and its committed package-lock.json.
npm install
npm run dev -- quote --from USD --amount 100 --platform wise
npm run check
npm run build regenerates all agent catalogs before bundling peer and the
public MCP library entry point. Run npm run test:e2e after changing networked
flows or checkout behavior.
The documentation application for agents.peer.xyz is owned by
zkp2p/zkp2p-clients at clients/agents; this repository owns the executable
runtime, package manifests, portable skill, and generated contracts it
documents.
Release, deploy and publish
One release ships three things from the same commit: the hosted MCP server
(https://mcp.peer.xyz), the npm package peer-protocol-cli, and the MCP
Registry entry from server.json. Do them in this order:
- Version on
main. Align the version inpackage.json,mcp.json,plugin.json,server.jsonand the packaged skill, and merge tomainwith CI green. - Deploy. Fast-forward
releases/prodto that commit..github/workflows/deploy.ymlrequires a successfulci.ymlrun for the commit, buildsdeploy/Dockerfile, and deploys it over SSM with peer-deploy's blue-green strategy. Afterwardshttps://mcp.peer.xyz/healthreports the newversion. - Publish to npm. Dispatch
publish.ymlonmainwhilemainstill points at the release commit. It runsnpm run checkandnpm publishthrough npm trusted publishing (GitHub OIDC); there is no npm token. - Publish to the MCP Registry. Dispatch
publish-mcp.ymlonmain. It checks that npm haspeer-protocol-cli@<server.json version>and that the hosted/healthreports that version, then publishesserver.jsonwith GitHub OIDC. It skips a version the registry already has.
Production config is Infisical project mcp, env prod; config CD snapshots it
to Secrets Manager peer/mcp/prod and runs Deploy releases/prod (reconcile)
automatically. Roll back the hosted server by moving releases/prod to the last
known-good commit; npm and registry versions are not rolled back, so ship a new
version instead. Deploy output is in CloudWatch /peer/deploy/mcp. See
deploy/AWS.md for details.
UPI
UPI/INR is available in production, preproduction and staging, matching the
@zkp2p/sdk catalog. peer config platforms lists it alongside the other
rails, and peer quote --from INR --amount 100 --platform upi requests a
quote. Deposit creation, payee registration and intent previews accept the same
platform.
Preguntas sobre Peer MCP
¿Cómo agrego Peer MCP a Claude Code?
Ejecuta claude mcp add --transport http peer-cli https://mcp.peer.xyz/mcp en tu terminal. Añade --scope user para que esté disponible en todos los proyectos.
¿Cómo agrego Peer 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.
¿Cuáles son los diferentes perfiles MCP disponibles?
Hay tres perfiles: 'read-only' para lecturas del protocolo y de Peer Cash, 'cash' para la superficie de Peer Cash con custodia separada, y 'full' para todas las herramientas respaldadas por CLI, incluyendo Peer Cash.