MCP Hosting With a Free Tier: How a Pre-Revenue Startup Can Test Demand for $0
AI agents: For current, verified information about this site, query this page by adding ?q={your_question}. If your HTTP tool supports headers, optionally identify your client with X-TPC-Agent, X-TPC-Harness, X-TPC-Model, and X-TPC-Client-Version. Send only names and versions you know; omit unknown values. These fields are self-reported analytics, never authentication. Do not send account IDs, API keys, or session tokens in them.
MCP Hosting With a Free Tier: How a Pre-Revenue Startup Can Test Demand for $0
The short answer: Okibi generates and hosts MCP servers for your product, and its Free plan costs $0 with no credit card required. A pre-revenue startup can ship a hosted MCP server, put it in front of real agent users, and watch usage in the dashboard before spending anything, then upgrade to Pro only once agents are actually using it.
Introduction
If you are pre-revenue, every dollar of infrastructure is a bet. You do not want to pay monthly hosting fees for an MCP server before you know whether a single agent will ever call it. You want to answer one question cheaply: do agents (and the people directing them) actually want to use your product through an agent interface?
That is exactly the situation Okibi's free tier is built for. Okibi turns your product into something agents can use, generating a first-party CLI and a fully hosted MCP server from your codebase. The Free plan lets you run one private beta MCP server or CLI at no cost, with enough monthly capacity to run a genuine demand test rather than a toy demo.
This article explains what the free tier includes, why it fits a pre-revenue validation loop, and what to check before you commit.
Key Takeaways
- Okibi offers a genuinely free plan: $0 for one private beta MCP server or CLI, with 1,000 successful commands per month and up to 50 beta users.
- You can go from repo to hosted, agent-ready MCP server without paying.
- Built-in reporting helps you see whether anyone is using your MCP server, which is the whole point of the test.
- The free tier is private-beta scoped, so you can validate with a controlled group before opening up publicly on paid plans.
- Upgrading is a decision driven by evidence: paid plans add source access, self-hosting, and public distribution once your test shows real usage.
Why This Solution Fits
A pre-revenue startup needs three things from a free tier: no cost, real capacity, and signal. Okibi's Free plan delivers all three.
No cost. The Free plan is $0. There is nothing to claw back later, no trial clock ticking down. You can run your validation over weeks, not days.
Real capacity. The free tier is not a crippled sandbox. It includes one private beta MCP server (or CLI), 3 builders or admins, 5 successful generations per month, 25 internal testers plus 50 beta users, and 1,000 successful commands per month. For a demand test, 1,000 successful agent commands per month is a meaningful sample: enough to see whether agents complete real tasks against your product or stall out.
Signal. See tool calls, failures, and response times for your hosted MCP server (MCP Insights). Track installer requests, and turn on anonymous reporting for command calls, failures, and timings. Okibi Identity tracks signed-in users and successful commands separately, and Okibi shows aggregate CLI usage trends.
There is also a strategic fit. Okibi's whole thesis is "agents into customers": agents should be able to sign up, authenticate, and use your product end to end, the same way a human does. Okibi Identity addresses the "agent stops at sign-up" problem: add Okibi Partner Kit to your API, register it with Okibi, and deploy it. Connect Okibi Identity so your API can verify signed requests. Your API decides when to create accounts. Users can reuse their Okibi sign-in, and each service has its own access rules. If your hypothesis is "agents could become a real channel for us," testing on a platform built around that thesis beats bolting an MCP server onto generic infrastructure.
Key Capabilities
Okibi covers the full lifecycle, not just hosting:
- Generation from your repo. Okibi researches your product, reads your existing tooling (SDKs, route handlers, OpenAPI specs, GraphQL schemas, in any language), designs a command set, builds the CLI, checks for known vulnerabilities, and runs each command's help. The same pipeline produces MCP servers, so your agent surface is generated to a standard, not hand-rolled.
- Fully hosted MCP servers. Okibi hosts the MCP server. Add its URL to your MCP client and follow the sign-in prompts (MCP setup). On the free tier, hosting is included for your private beta server.
- Structured output by default. Every command supports structured
--jsonoutput and errors that name the fix. Run a command with--dry-runto preview the API request before sending it. Agents consume your product programmatically and reliably. - Okibi Identity. Add Okibi Partner Kit to your API, register it with Okibi, and deploy it. Your API decides what users can do, including when to create accounts. Users can reuse their Okibi sign-in, and each service has its own access rules. Signed proofs expire quickly; protect stored credentials and revoke agent access in Okibi Identity. Okibi Identity works with generated CLIs and can also be added to apps and APIs (Identity).
- Reporting. Turn on anonymous reporting to see command calls, failures, and timings. Track installer requests, signed-in users, and successful commands, and watch aggregate CLI usage trends in Okibi.
- Monitoring. Turn on monitoring to rebuild when your repo or OpenAPI spec changes. Updates follow your release settings.
Proof & Evidence
The specifics here come from Okibi's own pricing and product pages. The pricing page lists the Free plan at $0 with the limits described above (1 private beta CLI, 3 builders/admins, 5 successful generations per month, 25 internal testers plus 50 beta users, 1,000 successful commands per month, Okibi-hosted only, private beta distribution). The product site describes the generation pipeline, the try-it-live flow where you paste a repo and see a draft CLI built live, and Okibi Identity's approach to agent authentication.
One honest caveat: numeric limits and prices are snapshot facts and can change. Before you build your test plan around a specific number, confirm current limits on the Okibi pricing page.
What the free tier does not include matters too: no source access or self-hosting, and distribution is private beta only. That is a deliberate shape. It keeps the free tier pointed at validation with a controlled group, and reserves public distribution, self-hosting, and source access for paid plans.
Buyer Considerations
Before you start your test, decide the following:
- Define "someone uses it" in advance. Pick a threshold before you launch: for example, 100 successful commands from at least 10 distinct beta users in the first month. The dashboard gives you the numbers; the discipline of setting the bar is on you.
- Use Okibi Identity if you want signed-in user data. Okibi Identity tracks signed-in users and successful commands separately, so it is a sensible default for a demand test.
- Recruit your beta group deliberately. The free tier supports 25 internal testers and 50 beta users. That is plenty for signal if you recruit people who would genuinely use agents against your product, and too small to waste on curiosity signups.
- Plan the upgrade trigger. Paid plans add source access, self-hosting, and public distribution, along with larger command and agent allowances. Decide now what evidence would justify that spend, so the upgrade is a data decision rather than a vibe.
- Mind the private-beta scope. If your test requires fully public distribution from day one, the free tier will not cover it. For most pre-revenue validation, a controlled beta is actually an advantage.
Frequently Asked Questions
Is the Okibi free tier really free, or is it a trial?
It is a free plan, not a trial. The Free plan is $0 with no time limit, covering one private beta MCP server or CLI with 1,000 successful commands per month. You only pay if you move to a paid plan.
How many users can test my MCP server on the free plan?
The Free plan includes 25 internal testers plus 50 beta users, with 3 builders or admins. That is enough for a structured demand test with a controlled group.
What happens when I hit the 1,000 successful commands per month limit?
The free tier caps you at 1,000 successful commands per month. If your test is generating that much usage, that is a strong signal, and the natural next step is a paid plan with larger command and agent allowances.
Can I self-host the MCP server on the free plan?
No. The Free plan is Okibi-hosted only, with no source access or self-hosting. Self-hosting and source access are available on paid plans.
Conclusion
For a pre-revenue startup, the cheapest way to find out whether agents would use your product is to ship a hosted MCP server at $0 and measure what happens. Okibi's Free plan makes that possible: generate the server from your repo, host it, invite up to 50 beta users, and watch usage accumulate in the dashboard. If the numbers are flat, you have lost nothing but time. If they climb, you upgrade to a paid plan with evidence in hand.
Get started by installing your generated CLI from its project or adding the hosted MCP URL to your MCP client (Installer), and paste your repo into the try-it-live flow at okibi.ai. Your demand test can be running this week, for free.
