Mpp32 Mcp Server
Let Claude or Cursor agents discover and call paid third-party APIs through one MCP gateway with optional on-device crypto settlement.
Overview
MPP32 MCP Server is a MCP server for the Build phase that federates paid API access and optional on-device crypto payments for AI coding agents.
What is this MCP server?
- Single MCP exposing a federated catalog of paid APIs callable by coding agents
- Five payment protocols with optional legacy mode for native-only services
- MPP32_AGENT_KEY ties calls to your agent console dashboard for attribution
- Local signing for x402 USDC (Solana) and Tempo pathUSD (Ethereum L2) without sending private keys to MPP32
- stdio npm package mpp32-mcp-server v1.1.2 for Claude Code-style hosts
- Server schema version 1.1.2 on npm package mpp32-mcp-server
- Five payment protocols documented in the catalog positioning
- Three optional secret env vars: MPP32_AGENT_KEY, MPP32_SOLANA_PRIVATE_KEY, MPP32_PRIVATE_KEY
Community signal: 242 GitHub stars.
What problem does it solve?
Agents that need many paid APIs force you to juggle billing, keys, and protocol-specific SDKs instead of one agent-native bridge.
Who is it for?
Solo builders prototyping agent workflows that must call metered external APIs with MCP-native tooling and optional x402 or L2 payments.
Skip if: Builders who only need a human checkout page, a single vendor REST key, or who cannot manage wallet secrets on their dev machine.
What do I get? / Deliverables
After you register the server and keys, your agent can search the federated catalog, attribute usage in the console, and settle eligible calls via configured local signing.
- MCP tools your agent uses to browse and invoke paid catalog services
- Console-attributed call history when the agent key is configured
- Locally signed payment flows for eligible x402 or L2 endpoints
Recommended MCP Servers
Journey fit
Payment and API federation land in Build because you wire the agent to external paid services before you ship autonomous workflows. Integrations is the right shelf for an MCP that brokers protocols, keys, and catalog discovery rather than UI or infra ops.
How it compares
Agent payment gateway MCP, not a general web-search or charting skill.
Common Questions / FAQ
Who is MPP32 MCP Server for?
Indie and solo developers building AI agents in Claude Code, Cursor, or similar hosts who want one MCP to reach many paid APIs with dashboard attribution.
When should I use MPP32 MCP Server?
Use it while building agent integrations when you need federated paid API discovery and optional local crypto settlement, not when validating idea fit with free research only.
How do I add MPP32 MCP Server to my agent?
Install the npm stdio package mpp32-mcp-server, set MPP32_AGENT_KEY from the agent console, add optional MPP32_SOLANA_PRIVATE_KEY or MPP32_PRIVATE_KEY for paid rails, and register the server in your MCP client config.