Skip to main content

​
What the MCP server is

The Parly MCP Server gives AI agents a bounded way to recover private state, preflight and send private payments, and interact with Parly app APIs when the operator enables the web API bridge. It is designed for agent-owned payment workflows that use Parly’s public app APIs safely.

​
Security model

The MCP server should run with an agent credential only. It should not inherit relayer execution power, relayer sealed-box credentials, or treasury authority. This separation keeps agent workflows useful without turning them into operator or governance tools.

​
What the MCP server exposes

Private balance tools:
  • recover_largest_note
  • preflight_shielded_payment
  • send_shielded_payment
  • execute_shielded_payment, kept as a compatibility alias
  • preflight_batch_shielded_payment
  • send_batch_shielded_payment
  • execute_shielded_payment, as a compatibility alias
MPP tools:
  • mpp_create_session
  • mpp_preflight_session_payment
  • mpp_settle_session_payment
When the web API bridge is configured, the MCP server can also expose app tools for:
  • Privacy Links status, public reads, owner lists, claims, publishing, visibility, reports, and social status
  • one-time deposit creation, wallet-deposit route quotes, payment status, payout status, refund claims, and invoice receipt verification
  • public relayer listing and relayer registration helpers
  • admin operations summary, reports, reserved names, payout queue, signed workflow actions, UI settings, and Telegram status When the public web API bridge is configured, MCP can call public-user APIs for:
  • Privacy Link status and public reads
  • owned Privacy Link listing
  • profile and invoice link claim, create, edit, publish, and visibility updates
  • profile and invoice payment preparation
  • profile and invoice one-time deposit address creation
  • supported wallet-deposit quotes
  • payment, payout, and payer-history status reads
  • failed-payment refund claims where available
  • short-lived receipt download URLs
  • invoice receipt verification
  • payout-scope verification
  • public relayer listing and relayer registration
  • CSV parsing for supported batch payment workflows
Treasury and admin controls are not exposed as public MCP tools.

​
recover_largest_note

This tool recovers the largest live note controlled by the configured agent credential for a given asset. It is useful for agents that need to reason about current private spendable balance before attempting execution.

​
preflight_shielded_payment

This tool validates one private payment request before proof generation or transaction submission. It is useful when an agent needs to check the route shape, asset lane, destination, and amount before attempting a send.

​
send_shielded_payment

This tool sends a private Parly payment from notes controlled by the configured agent credential. It is the direct immediate send path for agent workflows.

​
send_shielded_payment

This tool sends a private Parly payment from notes controlled by the configured agent credential. It is the direct immediate send path for agent workflows.

​
batch private sends

Batch tools support up to 10 same-chain payout lanes from one private note:
  • preflight_batch_shielded_payment
  • send_batch_shielded_payment
Cross-chain deposits use the public payment-route APIs. Cross-chain private sends are exposed only where the active public route supports them.

​
mpp_create_session

This tool creates an MPP-compatible session descriptor around the current agent-owned execution path. It is useful when an agent or service wants a machine-readable spending lane without changing the core settlement model.

​
mpp_settle_session_payment

This tool settles a Parly payment from a previously created session descriptor. It reuses the same execution engine rather than introducing a separate settlement protocol.

​
Web API tools

Web API tools call the same routes used by the Parly app. They do not bypass wallet signatures, admin sessions, rate limits, 403 policy checks, or audit history. Use PARLY_WEB_API_BASE_URL to enable this bridge. Admin routes still require an admin session or signed workflow authorization. Relayer keys and treasury keys do not belong in MCP runtime configuration. MPP settlement is counterparty-locked and spend-limit checked before proof work or settlement.

​
Runtime behavior

When the MCP server starts, it should make the active credential scope and adapter state explicit. That includes:
  • whether it is running with the agent credential only
  • whether MPP compatibility is enabled
  • whether web API tools are enabled
  • which service name and version are active when the adapter is used

​
Who it is for

The MCP server is intended for:
  • agent builders
  • copilots
  • service agents
  • automated systems
  • teams integrating bounded AI-driven payment workflows