IMBA Agent MCP is an MCP (Model Context Protocol) integration provided by IMBA Wallet for AI agents, with the repository name IMBAwallet/agent-mcp. It is released as a Stdio Docker image, divided into two categories: documentation (docs) and spending (spend), and installs the public npm packages @imba_wallet/agent-mcp-docs and @imba_wallet/agent-mcp. The repository itself does not contain API keys, Ed25519 private keys, or registry seeds.
Purpose and positioning: According to the official description, IMBA issues payment tools, not a booking service. In other words, it does not complete bookings for flights, hotels, or the products themselves on behalf of users; instead, it provides tools that can be used for payment, enabling agents to complete spending actions using prepaid payment methods.
Main capabilities:
- Visa/MasterCard prepaid cards—can be used to pay airlines, hotels, SaaS, or pay data centers and other scenarios billed by bank card.
- Travel eSIM—provides low-cost mobile data.
- Gift cards—provides a real-time catalog with about 20,000 entries (for example Apple, Steam, Google Play). The official guidance is to obtain them through search, and not to hardcode a specific SKU.
How to use: The repository provides a Stdio installation method:
- Documentation (no key required) image.
- Spending (operator key required) image. In addition, it also provides Claude Code marketplace installation (that is, this repository) and the Agent skill installation command: npx skills add IMBAwallet/agent-mcp --skill imba-agent
Officially, hosted remotes are also provided: docs and spend; and Playbooks are provided (what agents buy, HowTo, API docs).
Applicable scenarios: Suitable for scenarios that need to let AI agents complete payments with prepaid payment tools, purchase travel eSIMs, or purchase gift cards. Because the default Dockerfile is the documentation server, it can be used for building and scanning (such as Glama) without providing a key.
Limitations and notes (all from official materials):
- It is not ChatGPT's "moneyplugin" (Not a ChatGPT money plugin).
- ChatGPT Actions must not call spend.
- Increasing agent_tier will not unlock withdraw; the product does not support withdrawals.
- The repository does not store keys; spending is a separate image, and there is no operator key in the Glama sandbox, so the official requirement is not to publish Dockerfile.spend in Glama.
- Regarding Glama publishing: glama.json lists the GitHub user clnt2021. After pushing to main, you need to: log in to Glama with that GitHub account; open the listing and select Sync Server (the image may lag); if Maintainers still shows 0, you need to claim ownership (organization repositories require glama.json plus claiming). A Release should be created for the Dockerfile (docs) in the root directory, and Dockerfile.spend should not be published in Glama; the quality score (tool definitions/consistency) only appears after that Glama release, not after the GitHub tag.
- Regarding catalog copies: LobeHub (and similar platforms) require the GitHub user to own the listing repository. The keyless image packaging is located at clnt2021/imba_agent_mcp. When plugin.json, mcp.json, skills, Dockerfiles, or lhm.plugin.json change, both repositories need to be updated at the same time. The single source of truth for Wallet is docs/features/agent_mcp.md.
Information such as pricing, charging methods, and the specific scope of platform support is not yet explained in the provided materials.
