Free vs paid app automation servers the wrapper is free; the platform isn't.

Run the GitHub server yourself and you operate under your own token's API quota — generous for a person, tight for an agent fleet that comments, labels, and opens PRs all day. Run mobile-mcp or MCP Appium and you need actual devices or emulators attached to the host. Run Skyvern and you need browser infrastructure: headless Chrome instances, proxies if the target sites care, and the patience to maintain them.

None of that appears in the repo's install instructions, but it's the operating cost of "free" in this category. The npm install is the cheapest step you'll take.

Automation means acting on someone's account — a Trello board via mcp-server-trello, a Terraform workspace, a GitHub org. Self-hosting forces you to provision a credential for every platform an agent touches, scope it correctly, and accept that the agent acts as you. That's tolerable inside one team. It collapses entirely when the agent calling the tool isn't yours: nobody hands out their GitHub token to a third-party agent.

This is the structural reason paid hosted endpoints exist in automation: the operator holds the credentials and the infrastructure, and exposes a narrower, safer capability that strangers can pay to use.

With an x402-priced listing, an agent needs no account and no key. It hits the endpoint, gets 402 Payment Required with a price, pays in USDC on Base, and the call executes — settlement in about two seconds, payment confirmed before the handler runs, Ed25519-signed receipt for the audit trail, no chargebacks. Prices start at $0.01 per call.

Per-call maps cleanly onto automation work because the unit of value is obvious: one form filled, one PR opened, one device test run. An agent with unpredictable workload pays for exactly the automations it performs, instead of a subscription sized for a peak that may never come.

Self-host free when: the accounts being automated are your own, your token quotas survive your agents' call patterns, and you can keep browser or device infrastructure alive. Pay per call when: agents outside your org need the capability, the upstream platform's quota is the bottleneck, or the infrastructure behind the wrapper (browsers, emulators, proxies) costs more to run than the calls are worth to you.

If you maintain an automation server with real running costs, that's precisely the profile that monetizes well: claim the listing, price above your marginal cost, and let agents pay per automation. Loomal takes 5% on settled transactions, currently waived.