Walletap is the agent-ready wallet platform.

Walletap was the first wallet platform to ship a Model Context Protocol server, and it's still the only one. The package is open source at github.com/walletap/walletap-mcp, published on npm as @walletap/mcp-server, and exposes every Walletap REST endpoint as a typed MCP tool. If you can describe what you want, you can build it, send it, or measure it.

Four capability areas, mapped directly to Walletap's public API. Every tool is described to the AI so it can pick the right one for any request you make.

The owner of Aurora Coffee Co. opens Claude and types a single prompt:

The agent, via the Walletap MCP server, does this end to end:

1. Calls upload_file_from_url with the logo URL → receives a file_… id with 1×/2×/3× variants.
2. Calls create_template with { name: "Aurora Coffee Co.", type: "loyalty", pass: { backgroundColor: "#0E0E0E", logo: { fileId: "file_…" }, useStampCollection: true, stampCount: 8 } }.
3. Calls create_pass with the new templateId, passing customFields.collectedStamps = 2 and the recipient's email.
4. Reports back: template id, pass id, and the Apple / Google / Huawei wallet links.

Total elapsed time: under thirty seconds, no dashboard clicks, no API code written. The shop owner reads the result and the customer's phone receives the pass.

The recommended path is the hosted MCP server at https://mcp.walletap.io. Authentication is OAuth — first call walks you through Walletap sign-in and consent. No install, no local config. Pick your client below.

# ~/.codex/config.toml
[mcp_servers.walletap]
type = "http"
url  = "https://mcp.walletap.io"

// Gemini SDK + MCP TypeScript client — connect once, expose every Walletap
// tool as a Gemini tool call. Auth is via Walletap API key (no UI step yet).
import { Client } from "@modelcontextprotocol/sdk/client/index.js";
import { StreamableHTTPClientTransport } from "@modelcontextprotocol/sdk/client/streamableHttp.js";
import { GoogleGenAI } from "@google/genai";

const transport = new StreamableHTTPClientTransport(
  new URL("https://mcp.walletap.io"),
  { requestInit: { headers: { "X-API-Key": process.env.WALLETAP_API_KEY } } }
);
const mcp = new Client({ name: "gemini-walletap", version: "0.1.0" });
await mcp.connect(transport);
const { tools } = await mcp.listTools();

const ai = new GoogleGenAI({ apiKey: process.env.GEMINI_API_KEY });
const chat = ai.chats.create({
  model: "gemini-2.5-pro",
  config: { tools: [{ functionDeclarations: tools.map(t => ({
    name: t.name, description: t.description, parameters: t.inputSchema,
  })) }] },
});

{
  "mcpServers": {
    "walletap": {
      "command": "npx",
      "args": ["-y", "@walletap/mcp-server"],
      "env": {
        "WALLETAP_API_KEY": "wtap_sk_..."
      }
    }
  }
}

Building wallet passes used to require a developer, a designer, a marketer, and a project manager working through three vendors and an Apple Developer membership. With MCP, the marketer talks to the agent and ships in an afternoon. The platform stops being a UI you learn and starts being a system you describe.

Walletap was built around an API-first contract from day one — the MCP server is a natural extension of that. Every endpoint is exposed; every tool is typed; every change is auditable. We ship the same machinery the dashboard uses, just spoken instead of clicked.