XPack – Open-Source MCP Marketplace for Building and Selling MCP Services

TL;DR

TL;DR: XPack is the world’s first open-source MCP marketplace — deploy your own store, wrap any OpenAPI as an MCP service, and start selling with built-in Stripe billing and OAuth auth in under 10 minutes.

Source and Accuracy Notes

⚠️ This section is MANDATORY. All links must be verified from actual source, not guessed.

• Project page: xpack.ai ← MUST visit and verify
• Source repository: github.com/xpack-ai/XPack-MCP-Market ← MUST read README
• License: Apache 2.0 (verified via GitHub API license.spdx_id)
• Quick start: curl -sSO https://xpack.ai/install/quick-start.sh; bash quick-start.sh

What Is XPack?

XPack positions itself as the world’s first open-source MCP monetization platform. It lets developers wrap any REST API as an MCP service, host their own marketplace, and charge for access — all self-hosted under an Apache 2.0 license.

The core promise: turn your API into a sellable MCP service in under 10 minutes, without writing new code.

Key features directly from the README:

• One-click OpenAPI to MCP service configuration
• SEO-friendly homepage and service page generation
• Built-in billing (per-call or token-usage models)
• Stripe Payment integration
• Email and Google OAuth user authentication

Setup Workflow

Prerequisites

XPack requires:

• Runtime: Node.js (runtime)
• Database: MySQL ≥ 5.7.x
• Cache: Redis ≥ 6.2.x
• Queue: RabbitMQ ≥ 4.0
• Hardware (recommended): 8-core CPU, 16 GB RAM, 200 GB storage (AMD64 Linux)
• Minimum: 2-core CPU, 4 GB RAM, 200 GB storage (AMD64 or ARM64 Linux/macOS)

Option 1: One-Line Deploy

The fastest path:

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

This single command launches a full XPack deployment. The official YouTube guide covers the full 10-minute setup.

Option 2: Docker Compose

For containerized deployment:

1. Install Docker and Docker Compose.
2. Edit the docker-compose.yml file with your MySQL, Redis, and RabbitMQ connection details.
3. Run docker compose up -d.

Post-Setup: Stripe Configuration

After deployment, configure billing:

1. Create a Stripe account and get your API keys.
2. Set your Stripe publishable key and secret key in the XPack admin panel.
3. Configure your pricing plans (per-call or token-usage).

Post-Setup: OAuth

XPack supports Email and Google OAuth out of the box:

1. In the admin panel, navigate to Settings → Authentication.
2. Enter your Google OAuth client ID and secret (from the Google Cloud Console).
3. For email auth, configure your SMTP server details.

OpenAPI to MCP: How It Works

XPack’s main value proposition is converting existing REST APIs into MCP services without code changes:

1. Import your OpenAPI spec — paste your openapi.yaml or provide the URL.
2. XPack generates MCP config — it creates the JSON structure MCP clients understand.
3. Publish to your marketplace — your service appears on your XPack storefront.
4. Set pricing and access controls — Stripe handles payments and metering.

Practical Evaluation Checklist

• [ ] Successfully deploy XPack via the quick-start script
• [ ] Import an existing OpenAPI spec and verify MCP service generation
• [ ] Configure Stripe test mode and run a billing cycle
• [ ] Test Google OAuth login flow
• [ ] Verify Redis queue processing for token-usage billing
• [ ] Check the SEO-friendly storefront pages for your MCP service
• [ ] Evaluate the admin panel for user and revenue management

Security Notes

XPack handles payment credentials and user authentication — treat the deployment with standard PCI-DSS awareness:

• Run XPack behind a reverse proxy (Nginx or Cloudflare Tunnel) with TLS.
• Use environment variables for all secrets — never commit Stripe keys or OAuth secrets to version control.
• The README notes everything is open-source (Apache 2.0) — audit the source before using with production billing keys.
• RabbitMQ and MySQL should be on isolated network segments in production.
• Regularly rotate Stripe webhook signing secrets.

FAQ

Q: Does XPack work with any REST API? A: XPack supports any API described by an OpenAPI 3.x specification. If your API has a valid openapi.yaml, XPack can generate an MCP service wrapper for it.

Q: What payment providers are supported? A: Stripe is the only payment provider listed as a built-in integration. Per-call and token-usage billing models are both supported.

Q: Is this truly self-hosted? A: Yes — you deploy XPack on your own infrastructure. No XPack cloud service is required. The marketplace, billing, and auth all run on your servers.

Q: What license is XPack released under? A: Apache 2.0 — confirmed via GitHub API. Commercial use is permitted without restrictions.

Q: Does XPack provide the MCP server runtime or just the marketplace? A: XPack generates the MCP service configuration and hosts the marketplace storefront. The actual MCP server for your API runs on your infrastructure, managed by your existing deployment pipeline.

Conclusion

XPack fills a specific niche: developers who want to monetize APIs as MCP services without building a billing system from scratch. The one-line deploy and OpenAPI-to-MCP conversion are the stand-out features — both reduce the time from “I have an API” to “I have a monetized MCP service” to under 10 minutes.

The Apache 2.0 license means you can run it commercially without vendor lock-in. If you’ve been looking for a self-hosted way to sell access to your AI toolchain via MCP, XPack is worth a serious look.

Source last checked: 2026-08-02 (commit main branch)