Expose your agents via MCP as a tool
Central MCP gateway beats duct-taping OAuth into every desktop AI client separately.

Makes billing config prompt-operable; non-engineers can change pricing via their IDE.
AI-native SaaS teams, finance and engineering teams managing usage-based pricing
Stripe CLI · Shopify CLI · Twilio CLI
We kept running into the same issue while building a monetization layer for AI teams.
Small pricing changes would require engineering. Add a commitment. Adjust overage. Create a subscription tweak, everything.
So we tried something different. We built an MCP server for Flexprice.
Now every API operation is exposed as structured MCP tools. If you use Cursor, Claude Code, VS Code, Gemini, Windsurf, or any MCP-compatible client, you can connect your Flexprice account and operate billing through your AI assistant!
You can:
• Create subscriptions • Configure commitments and overages • Issue invoices • Post usage events • Manage wallets and more through your IDE or assistant now!
What we like most about this is that pricing is no longer locked behind engineering.
A non-technical co-founder or someone from finance can prompt a change, and it executes safely through authenticated tools.
Curious what HN thinks about prompt-operable infra like this. Happy to answer questions! Feel free to check out our docs for more info: https://docs.flexprice.io/docs/connect/mcp-server
Central MCP gateway beats duct-taping OAuth into every desktop AI client separately.
Copy-paste prompt collection on Gumroad, not software—content product competing with free alternatives.
Research framework with published paper, not a production red-teaming tool.
Custom pricing units solve real credit/token billing chaos, but Stripe + Chargebee already do this.
MCP server lets Claude search its own conversation history instead of re-deriving paid context.
Drops token usage 97% and blocks injection — smart sanitization beats raw WebFetch, drop-in replacement.