How to Price Paid MCP Servers
heiba_wk · reddit · 2026-07-17
The author explores whether per-call pricing makes sense when designing billing for paid MCP servers.
The core dilemma:
- Agents might select the wrong tool, timeout and retry, make exploratory calls, or get stuck in loops.
- While compute resources are consumed, users may not view these failed calls as "valuable outcomes."
- Per-call billing is easy to quantify, whereas task- or outcome-based billing aligns better with user goals but is harder to define.
The author mentions their experience with FluxA's agent payment flow, highlighting that visual invoices were the most helpful—clearly showing how much was spent, why, and whether the call succeeded.
The post concludes by asking the community: if you run a paid MCP server, what exactly should you charge for?
More from coding & agent
- Anthropic researcher: 99% of engineers now run swarms of 300+ self-improving agents — AlishaOutridge · 2026-09-11
- Gergely Orosz: Shipping 10x PRs With AI Agents, Sites Fill With Small Regressions — ducha_aiki · 2026-09-11
- Same Echo Maze prompt, three frontier models: all passed visually but shipped the same hidden bug — eyishazyer · 2026-09-11
- Astra storyboards plus Minimax H3 per-shot generation boost video success rates — Hailuo_AI · 2026-09-11
- Codex tip: use Sol with Astra and Luna sub-agents to save usage — pvncher · 2026-09-11
- agents-best-practices: a provider-neutral Agent Skill for designing and auditing agentic harnesses — tom_doerr · 2026-09-11