Documentation v1.24
Last updated 2026-08-20 Give feedback

Connect An Agent

Use this guide to install the native MagicPay plugin, authenticate its remote MCP, verify capabilities, and run the first Memory-managed workflow.

Before You Start

You need one supported runtime where the agent can install skills or persistent instructions and connect a remote MCP server. Use the runtime's native MCP authentication flow rather than a local MagicPay command.

Install The Right Surface

Install the host-native MagicPay plugin. It contains only the skill, the skill-shipped MagicFill actuator, and a remote MCP declaration. The host keeps using its own built-in browser; no package, MagicPay CLI, library, local service, or second browser runtime is installed.

Authenticate Once

Use the MCP connection page opened by the host. Enter the email and OTP there; the same OAuth flow verifies the account, authorizes the remote MCP, and redirects to the host. Never send the setup OTP through agent chat.

Verify

Confirm the runtime can call the remote MagicPay MCP before starting a real checkout flow.

  1. Call get_magicpay_capabilities through the connected remote MCP.
  2. Require client_browser, remote database session authority, and skill-script MagicFill delivery.
  3. Restart the runtime if newly installed skills are not visible.
  4. Begin with a browser-only task, then move to a protected form such as a shipping address.
MagicPay public documentation.