The Virtuals plugin connects Base MCP to the Virtuals Agent Commerce Protocol (ACP) MCP server. ACP is a platform for creating and operating autonomous AI agents that transact onchain, hold payment cards, and own email identities. Base MCP’s wallet is used only to sign the SIWE login challenge — every subsequent Virtuals tool call carries a session JWT. Server:Documentation Index
Fetch the complete documentation index at: https://docs.base.org/llms.txt
Use this file to discover all available pages before exploring further.
https://mcp.acp.virtuals.io/
Operations: agent management (create / list / prepare-launch), agent cards (signup, issue, set limits, 3DS), agent email (identity, inbox, search, compose, reply, OTP/link extraction).
Try it
Sign in
List agents
Create everything
Pattern
Virtuals is session-authenticated: every tool requires atoken parameter obtained via SIWE. The plugin orchestrates the round trip — get_wallets → login_start → sign (Base MCP) → user approves → get_request_status → login_complete — then reuses the JWT for the rest of the session. Use login_refresh when the ~1 hour token expires.
After auth, Virtuals operations route through the Virtuals backend (card issuance, email, agent ops) — not through Base MCP. Only the SIWE signature uses Base MCP. Don’t echo card numbers, 3DS codes, OTPs, or email bodies to chat unless the user explicitly asks.
Installation
Run Base MCP and Virtuals side by side:Terminal
Reference
Full plugin spec on GitHub
Step-by-step SIWE auth flow, troubleshooting for the six common signature-verification failure modes, and orchestration recipes for agent / card / email operations.