LavoLoopIntegration guide

REMOTE MCP / X402

Connect ChatGPT and other agents to LavoLoop safely

Connect to one public remote MCP server. There is no LavoLoop CLI to install and no Agent Token to paste into a client. The first connection completes LavoLoop sign-in and OAuth consent; the agent can then initiate payments within policy.

Remote MCP endpointhttps://mcp.lavoloop.com/mcp

Compatible clients

Any remote MCP client that supports Streamable HTTP and OAuth can connect, including versions of ChatGPT, Codex, and other agent products that expose custom remote MCP support. The setting may be called Connectors, MCP servers, or Custom connectors.

Connection flow

  1. 01
    Add a custom MCP server

    Enter the URL above as the remote server endpoint. Do not open the OAuth page yourself; the client discovers authorization metadata from the MCP response.

  2. 02
    Authorize LavoLoop once

    When the client opens a browser, sign in with an email OTP and approve access. Before the first connection, finish wallet creation and delegated signing in the LavoLoop console.

  3. 03
    Call tools in natural language

    Ask for the balance or recent payments first, then ask the agent to call a paid API. Every external client is attached to a dedicated LavoLoop Agent and payment policy.

Example prompts

Show my LavoLoop test USDC balance.List my 10 most recent x402 payments.Call this x402 API, authorize at most 0.20 USDC, and use a new idempotency key.

Available tools

get_balanceRead only

Reads available and reserved Base Sepolia test USDC.

list_paymentsRead only

Reads up to 50 recent payments, approval states, service domains, and settlement references.

paid_fetchExecutes payment

Requests a GET or POST x402 resource under budget, domain, and approval policy.

Default policy for a new connection

The first OAuth consent creates a dedicated Agent for that client. These testnet defaults can be changed later in the console:

Network / asset
Base Sepolia / test USDC
Per-payment limit
1 USDC
Daily limit
5 USDC
Monthly limit
25 USDC
Allowed domains
Public HTTPS x402 services by default

SECURITY BOUNDARY

OAuth does not replace wallet authorization

The external client receives only a short-lived, scoped OAuth token. CDP login credentials, wallet keys, and delegated-signing credentials never leave LavoLoop. Every payment still passes domain, per-payment, daily/monthly budget, approval, idempotency, and audit checks.

Connection test

  1. After adding the MCP server, the client should open the authorization page on lavoloop.com.
  2. After consent, the tool list should contain get_balance, list_payments, and paid_fetch.
  3. Call get_balance first; it is read-only and cannot create a payment.
  4. For paid_fetch, use a testnet x402 API you trust and a small maxAmountUsdc.
  5. Confirm the Agent, payment state, and audit record in the LavoLoop console.

Troubleshooting

Opening the MCP URL returns 401

That is expected and proves the endpoint requires OAuth. Start the connection from an MCP client instead of treating the URL as a web page.

Authorization asks you to finish wallet setup

Sign in to the LavoLoop console, create the Base Sepolia wallet, complete delegated signing, and reconnect.

A payment is awaiting_approval

Approve it in the console, then ask the agent to retry with exactly the same arguments and idempotency key.

Protocol and client references

OpenAI: MCP and ConnectorsOpenAI: authentication for custom remote MCP