Evaluation RuleDecision layer

Rayrun Rule: Adopt When Client Tool Calls Stay Under 100,000 Per Developer

Does Rayrun's per-tool-call pricing and MCP hosting model fit our agency's client mix, or will usage overruns erode the retainer margin? Adopt Rayrun when per-client credential isolation and per-tool access policies are contractually required and projected tool calls fit inside the pooled 100,000-per-developer Team allowance; otherwise stay on the free tier until a paying client justifies the $25 seat.

By InnovaAI ResearchPublished Updated

“Does Rayrun's per-tool-call pricing and MCP hosting model fit our agency's client mix, or will usage overruns erode the retainer margin?”

Adopt Rayrun when per-client credential isolation and per-tool access policies are contractually required and projected tool calls fit inside the pooled 100,000-per-developer Team allowance; otherwise stay on the free tier until a paying client justifies the $25 seat.

Common Mistake

Agencies sign a fixed monthly retainer for MCP hosting and then discover that one chatty client workflow consumes the pooled call allowance, turning a predictable retainer into a variable cost they absorb. The fix is to meter client usage from the activity history before quoting a flat fee, or to price the retainer with a call-volume ceiling written into the scope.

Why This Works

Rayrun's value is concentrated in the control plane: one endpoint, a shared credential vault, roles and client-specific access, and activity history, all of which map directly to agency multi-client delivery. The free tier already covers 25 source-built services and 50,000 tool calls a month, so an agency can validate the workflow on a single client at $0 before committing. The Team plan at $25 monthly pools 100,000 tool calls per developer, but the per-tool-call overage model (USD 0.2 per 1,000 calls) means margin depends on forecasting client usage accurately, not on the seat price.

Apply When
  • •The agency manages three or more client environments that each need MCP server access with separate credential sets.
  • •Combined monthly tool calls across all clients stay below 100,000 per developer on the Team plan at $25 monthly.
  • •At least one client requires security review or contractual assurance that upstream API keys are never stored in their environment.
  • •The delivery team already scaffolds TypeScript or Python MCP projects and can deploy with rayrun deploy without new tooling.
  • •The agency wants to productize a fixed-fee MCP deployment (the $1,800 Starter offer) rather than bill hourly for integration work.
Open the Rayrun courseRayrun decision recordBrowse the Academy

More on Rayrun