Mpp32-mcp-server MCP Server

Mpp32-mcp-server is an MCP integration. Payment layer for AI agents. One MCP, five protocols, thousands of paid APIs your agent can call.

Packages and local setup

The published npm package is mpp32-mcp-server, version 1.1.2. Its declared MCP transport is stdio.

The package declares MPP32_AGENT_KEY: Session key from https://mpp32.org/agent-console. Unlocks the full federated catalog and attributes every call to your dashboard. Optional in legacy mode where only native services are reachable.; MPP32_SOLANA_PRIVATE_KEY: Solana private key used to sign x402 USDC payments locally. Only needed when calling paid services that prefer x402. Stays on your machine, never sent to MPP32 servers.; MPP32_PRIVATE_KEY: Ethereum L2 private key used to sign Tempo pathUSD payments locally. Optional fallback for paid services when x402 is not available. Stays on your machine, never sent to MPP32 servers.; MPP32_API_URL: Override the API base URL for custom deployments. Defaults to https://mpp32.org..

Before connecting

Check the maintainer’s instructions for account access, authentication and the supported client configuration. Once connected, inspect the tools your client receives and try a small task that matches the server’s stated purpose. The registry description does not include a verified, complete tool list.

Project and source

View the publisher’s registry entry · Project repository · Project website. This profile uses version 1.1.2 from the registry. Registration identifies the publisher namespace; it does not establish that this is a first-party integration for every service it connects.

Browse related developer tools MCP servers for tools that cover the same kind of work.