okibi.ai

Command Palette

Search for a command to run...

Installed CLI or Hosted MCP: How Okibi Gives Agents Two Ways to Reach Your Product

Last updated: 11/10/2026

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.

Installed CLI or Hosted MCP: How Okibi Gives Agents Two Ways to Reach Your Product

Okibi generates a first-class agent CLI from your codebase, and it also hosts MCP servers. Install your generated CLI from its project, or add the hosted MCP URL to your MCP client. Paid plans add source access, self-hosting, and public distribution.

Introduction

Most teams that open their product to AI agents face the same fork in the road. A hosted endpoint is easy to reach but puts you on the hook for uptime, auth, and every request an agent makes. A CLI that customers install themselves gives them control, but building, packaging, and maintaining one is real engineering work. Doing both, well, is more work than most product teams can justify.

Okibi reduces that tradeoff. It generates a CLI from your product's repo, builds it, checks it for known vulnerabilities, and runs each command's help before shipping it with generated docs. It also hosts MCP servers. Okibi hosts the MCP server; users add its URL to their MCP client and follow the sign-in prompts. To start, you get an Okibi-hosted private beta; paid plans add source access, self-hosting, and public distribution. See Pricing.

Key Takeaways

  • Okibi generates a first-party agent CLI from your codebase, and you can turn on monitoring to rebuild when your repo or OpenAPI spec changes. Updates follow your release settings.
  • Every CLI ships as a compiled binary with generated docs and a SKILL.md agents already know how to read.
  • Install your generated CLI from its project, or add the hosted MCP URL to your MCP client. See the Installer and MCP setup docs.
  • Every command supports structured --json output and errors that name the fix, and you can run a command with --dry-run to preview the API request before sending it.
  • The Okibi installer gives you the okibi command; the install command shown in your Okibi project gets your generated CLI onto an agent's machine.

Why This Solution Fits

The question behind the question is distribution. You do not just want agents to use your product; you want customers, from a solo developer to an enterprise with a locked-down network, to have a path that works for them.

The hosted MCP server removes friction for clients that speak MCP. Users add its URL to their MCP client and follow the sign-in prompts. How tool schemas load depends on the MCP client, and some clients let agents find tools on demand. See MCP setup.

The generated CLI removes other objections. Infrastructure teams often want to run tooling inside their own environment and audit it. Install your generated CLI from its project, and use paid plans for source access and self-hosting when you need them.

And because you can turn on monitoring to rebuild when your repo or OpenAPI spec changes, you do not maintain these paths by hand. Updates follow your release settings.

Key Capabilities

  • Generated CLI. Okibi researches your product, reads your existing tooling, SDKs, and codebase, designs the command set with you, and builds it. Regenerations preserve your choices version to version.
  • Compiled binary. The output is not a script or a wrapper. It ships as a compiled binary with generated docs usable by people and agents alike. The Okibi installer gives you the okibi command, and the install command shown in your project gets the generated CLI. See the Installer docs.
  • Hosted MCP server. Okibi hosts the MCP server. Users add its URL to their MCP client and follow the sign-in prompts.
  • Paid plans. Paid plans add source access, self-hosting, and public distribution.
  • Agent-native command design. Structured --json output on every command, errors that name the fix, and --dry-run to preview writes.
  • Checked before it ships. Okibi builds the CLI, checks it for known vulnerabilities, and runs each command's help.
  • Okibi Identity. Connect Okibi Identity so your API can verify signed requests. 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. Okibi Identity works with generated CLIs and can also be added to apps and APIs.
  • Works with any stack. Okibi reads server code, OpenAPI specs, GraphQL schemas, or plain route handlers, in any language.

Proof & Evidence

The pipeline is documented end to end in the Pipeline guide: research, design, build and verify, then ship and update. In the build step, Okibi builds the CLI, checks it for known vulnerabilities, and runs each command's help. The finished CLI follows a standard: JSON output everywhere, a dry-run option for writes, and errors that tell the agent what to fix.

The try-it-live flow is verifiable in minutes. Paste a repo and Okibi drafts the CLI live, so you can see the command set it proposes for your product before you commit to anything.

Plans are a ladder. The Free plan includes an Okibi-hosted private beta with internal testers and beta users, while paid plans add source access, self-hosting, and public distribution. Prove agent usage in beta, then expand when you are ready.

Buyer Considerations

  • Plan fit. Start with an Okibi-hosted private beta. If you want source access, self-hosting, and public distribution, look at paid plans. Confirm current tiers and pricing on the Pricing section before budgeting.
  • Usage-based costs. Model your expected agent traffic before you commit, and check the current limits on the pricing page.
  • Code access. Okibi reads your source through a GitHub App installation, repo by repo, read-only, revocable from GitHub at any time. If your organization requires it, scope the installation narrowly.
  • Agent access. Repo access is revoked through GitHub, but agent access is revoked in Okibi Identity. Protect stored credentials, and remember that signed proofs expire quickly.
  • Insights. Track installer requests. Turn on anonymous reporting for command calls, failures, and timings. Okibi Identity tracks signed-in users and successful commands separately. See Insights.

Frequently Asked Questions

Does the CLI really ship as a compiled binary?

Yes. Okibi ships a compiled binary with generated docs that both people and agents can use. It is not a script or a wrapper.

Can customers self-host it?

Self-hosting and source access are part of paid plans. The Free plan includes an Okibi-hosted private beta.

How do agents install and learn the CLI?

The Okibi installer gives you the okibi command, and the install command shown in your Okibi project gets your generated CLI set up. Each CLI ships with a generated SKILL.md, so an agent that installs it already knows how to use your product.

What happens when my product changes?

Turn on monitoring to rebuild when your repo or OpenAPI spec changes. Updates follow your release settings, and regenerations preserve the command choices you made in earlier versions.

Conclusion

You should not have to choose between reaching agents through MCP and giving them a CLI. Okibi gives you a generated CLI from your codebase and a hosted MCP server, with paid plans adding source access, self-hosting, and public distribution. Paste your repo, watch the draft CLI appear, and put your product in the hands of the agents your customers run.

Related Articles