Skip to content

Add community.sapph1re-billing-gateway-mcp-http - #274

Open
sapph1re wants to merge 2 commits into
mcpmux:mainfrom
sapph1re:add-billing-gateway-mcp
Open

Add community.sapph1re-billing-gateway-mcp-http#274
sapph1re wants to merge 2 commits into
mcpmux:mainfrom
sapph1re:add-billing-gateway-mcp

Conversation

@sapph1re

Copy link
Copy Markdown
Contributor

Change Type

  • Add a new server definition

Summary

Adds MCP Billing Gateway, an open-source billing infrastructure server for MCP developers — enables registering services, defining pricing plans (Stripe-backed), tracking per-tool usage, and validating client access tokens.

Server Details

  • Server Name: MCP Billing Gateway
  • Server ID: community.sapph1re-billing-gateway-mcp-http
  • Transport: http
  • Authentication: api_key (Bearer token; self-hosted deployment)
  • Categories: developer-tools
  • Upstream Repository: https://github.com/sapph1re/mcp-billing-gateway-sdk

Checklist

CI-enforced — your PR will fail without these

  • JSON file lives at servers/community.sapph1re-billing-gateway-mcp-http.json
  • Filename matches the id field exactly
  • Required fields present: id, name, transport
  • pnpm validate servers/community.sapph1re-billing-gateway-mcp-http.json passes
  • pnpm check-conflicts passes (no duplicate IDs or aliases)
  • pnpm test passes
  • Every commit is signed off — git commit -s (DCO)

Reviewer quality bar

  • description is one clear sentence — no marketing fluff
  • At least one category from categories.json is assigned
  • auth.type is consistent with how credentials are actually wired into the transport
  • links.repository resolves (public repo)
  • capabilities reflect what the server actually implements (tools: true)
  • platforms is ["all"] — server-side

Platform-managed fields — leave unset

  • I did not set badges, stats, sponsored, featured
  • I did not set publisher.official, publisher.verified, publisher.domain_verified
  • I did not add any _platform*-prefixed keys

Trademark & branding

Notes for Reviewers

The hosted endpoint (Railway) is a reference deployment. The gateway is designed to be self-deployed by MCP developers who want to monetize their own servers — the auth.instructions explains this context. The SDK repo contains the full deployment guide.

Signed-off-by: Signal <signal@cortex.internal>
"type": "http",
"url": "https://mcp-billing-gateway-production.up.railway.app/mcp/",
"metadata": {
"inputs": []

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

please define the auth key input here

"type": "http",
"url": "https://mcp-billing-gateway-production.up.railway.app/mcp/",
"metadata": {
"inputs": []

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

please define the auth key input here

Add transport.headers and metadata.inputs with full input definition
for the API key — id, label, description, secret, required, and
obtain instructions linking to the setup guide.
@sapph1re

Copy link
Copy Markdown
Contributor Author

Thanks for the review! I have defined the BILLING_GATEWAY_API_KEY input in transport.metadata.inputs with label, description, secret flag, and obtain instructions, and wired it to the Authorization header via ${input:BILLING_GATEWAY_API_KEY}. Please let me know if any further adjustments are needed.

@sapph1re

Copy link
Copy Markdown
Contributor Author

Friendly bump — it's been 4 days since the fix in commit 3d03141. The BILLING_GATEWAY_API_KEY input is now defined in transport.metadata.inputs with label, description, secret flag, and obtain instructions, wired to the Authorization header via ${input:BILLING_GATEWAY_API_KEY}. Happy to make any further adjustments if needed.

@sapph1re

Copy link
Copy Markdown
Contributor Author

Pinging again — CI is green and @its-mash approved this on Aug 5. Could a maintainer please merge this? Happy to address any remaining feedback if needed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants