XPack – Self-Hosted MCP Marketplace

TL;DR

TL;DR: XPack is an open-source platform that lets you deploy a self-hosted MCP marketplace, monetize MCP servers via Stripe, and offer OAuth login — all in under 10 minutes.

Source and Accuracy Notes

• Project page: xpack.ai
• Source repository: github.com/xpack-ai/XPack-MCP-Market
• License: Apache-2.0 (verified via GitHub API)
• HN launch thread: news.ycombinator.com/item?id=47170174 (pending — confirm from HN)
• Source last checked: 2026-06-23

What Is XPack?

XPack positions itself as the world’s first open-source MCP monetization platform. It lets you wrap any OpenAPI-compliant service into an MCP server, then sell access to it through a hosted marketplace — with built-in Stripe billing, per-call or token-usage pricing, and user account management.

The entire stack is self-hostable. Everything runs in Docker containers behind your own domain, with no vendor lock-in.

Key Features

From the README:

• One-click OpenAPI to MCP service config — paste an OpenAPI spec, get a runnable MCP server
• SEO-friendly homepage and service page — each MCP listing gets a public-facing page
• Built-in billing — per-call or token-usage metering
• Stripe Payment support — standard Stripe Checkout integration
• Email and Google OAuth sign-in — user account management out of the box
• Fully open-source — Apache 2.0, commercially usable

System Requirements

| Component | Recommended | Minimum | |---|---|---| | CPU | 8 cores | 2 cores | | Memory | 16 GB | 4 GB | | Storage | 200 GB | 200 GB | | OS | Linux | Linux / macOS | | Architecture | AMD64 | AMD64 / ARM64 |

Required runtime services: MySQL 5.7+, Redis 6.2+, RabbitMQ 4.0.

Quick Start (One-Command Deploy)

XPack ships a quick-start.sh installer that handles the full Docker-based deployment:

curl -sSO https://xpack.ai/install/quick-start.sh; bash quick-start.sh

The script deploys all required containers (MySQL, Redis, RabbitMQ, and the XPack app itself) and exposes the marketplace on port 8000 by default.

Docker-Compose Deployment

For manual control, edit the included docker-compose.yml:

vi docker-compose.yml

Then launch:

docker-compose up -d

The Docker path requires Docker and Docker Compose installed separately.

Architecture Overview

XPack-MCP-Market consists of:

• Frontend + API — Node.js app served behind Nginx (port 8000 mapped to 80)
• MySQL — user accounts, billing records, service metadata
• Redis — session management and rate limiting
• RabbitMQ — async job queue for billing and metering

All services are containerized. No compiled binaries required on the host beyond Docker.

What You Can Build With It

• A paid directory of internal MCP tools for a team or company
• A public marketplace selling third-party MCP integrations
• A freemium gateway offering a free tier with usage caps
• A B2B SaaS wrapping proprietary APIs behind the MCP protocol

Security Notes

• OAuth credentials (Google) and Stripe keys are stored in the container environment — protect the host
• MySQL password is set via MYSQL_ROOT_PASSWORD in the compose file — change before running
• No built-in DDoS protection; run behind Cloudflare or a similar proxy for public deployments
• Update containers regularly — XPack does not ship an auto-update mechanism

FAQ

Q: Do I need a Stripe account to use XPack? A: Yes, billing requires a Stripe account and API keys. Without Stripe configured, the billing features are disabled and access is free.

Q: Can I run this on macOS for development? A: Yes — XPack supports ARM64 macOS as a minimum requirement. Production recommendation is Linux AMD64.

Q: Does XPack host the MCP servers for me? A: No. XPack is the marketplace and billing layer. You deploy and operate your own MCP servers; XPack handles authentication, metering, and payments.

Q: What does the pricing page look like? A: Each MCP service in the marketplace has its own pricing page. You can set per-call flat fees or token-usage-based billing through the Stripe integration.

Conclusion

XPack fills a specific gap in the MCP ecosystem: turning a working API into a sellable MCP product without rebuilding auth, billing, and discovery from scratch. The one-command deploy is genuinely quick, and the Apache-2.0 license removes the commercial hesitation that blocks many open-source monetization tools.

If you are building on the MCP protocol and want a hosted, monetizable storefront without giving a platform a cut of your revenue, XPack is worth 10 minutes of your time.

Try it: xpack.ai