An MCP front door for Claude harnesses

Turn any Claude harness
into something people install

Paste a GitHub repo of a Claude Code plugin. We run it as a hidden, server-side session and hand each customer one MCP URL for their own Claude. The harness stays on our server. How it works

Public repos clone instantly · private repos supported after sign-in

how it works

From a repo to a one-line install.

  1. 01[ clone ]

    Paste your plugin repo

    Point Aihar.app at the GitHub repo that hosts your Claude Code plugin. Public repos clone and parse instantly.

  2. 02[ run hidden ]

    We run it, sealed

    It runs as an isolated, server-side Claude session with your plugin installed. The harness never leaves our server.

  3. 03[ one URL ]

    Share one MCP URL

    Each customer gets one signed, revocable MCP URL to add to their own Claude. Their Claude talks to yours, results only.

about

The short version.

What is Aihar.app?

Aihar.app is an MCP front door for Claude Code harnesses. It takes a GitHub repo that hosts a Claude Code plugin and runs it as a hidden, server-side Claude Agent SDK session. You mint one signed MCP URL per customer; they add that single URL to their own Claude client (Desktop or Code) and get the harness's results without ever seeing its contents.

Does my harness stay private?

Yes. The plugin, prompts, and skills never leave the server. Each customer session runs under its own Linux user in an isolated directory (mode 0700) it cannot escape, behind an allowlist egress proxy, with tool calls path-jailed to markdown files. The customer's Claude speaks to yours over MCP and receives only results, never the harness.

How does a customer connect?

They run one command, claude mcp add --transport http <name> https://aihar.app/mcp/<token>, or paste the URL into Claude Desktop. That signed, revocable URL is the entire install. Their Claude then talks to your hidden session over MCP; there is nothing to download and no source to leak.

What can I turn into a product?

Any Claude Code plugin that lives in a GitHub repo: a venture-building playbook, a research workflow, a code-review harness, a writing system. If it works as a plugin on your machine, Aihar.app can host it as a sellable MCP endpoint without you open-sourcing the part that makes it good.

Is Aihar.app open source, and what does it cost?

The engine is open-core and self-hostable, so you can run it yourself or read the code. The hosted cloud at aihar.app handles isolation and scale for you. Previewing your repo, signing in, and importing your first repo are free; an active subscription, billed through Stripe, unlocks additional products and minting customer MCP URLs.

open core

The engine is open. The cloud is the service.

Aihar.app's engine is open-core and self-hostable. Run it yourself and read the code, or let the hosted cloud at aihar.app handle isolation and scale for you.

View the source on GitHub

about.

The workshop I couldn't hand over. Aihar.app

For the last year, I have run Aibl.to workshops on one thing: getting professionals from AI-curious to AI-able. The one people remember is the full-day session where a room goes from zero to a stress-tested business plan by the time we wrap. No slide deck runs that day. A harness does, one I built inside Claude Code: the prompts, the skills, the order I make the model do things in. Months of deciding what to tell it and when.

People kept asking to run it themselves, and I had no good answer. Open-source the plugin and I give away the exact thing the workshop is. Share my account and it dies the moment two people need it at once. Sell a prompt pack and I'm selling a text file that gets forwarded once and copied forever. I spend a lot of words telling people to own their AI setup, to work with it on purpose instead of on autopilot. But there's a version of that I never saw solved: how does a creator sell what they know without setting the knowledge itself on fire?

That's what Aihar.app does. I paste the GitHub repo of my Claude Code plugin. It runs the plugin as a hidden, server-side Claude session, and mints one signed MCP URL for each customer. They add that single URL to their own Claude, Desktop or Code, and their Claude talks to mine. They get the sprint. They never get the harness. The prompts, the skills, the order of operations stay on my box.

The part I refused to hand-wave is the box. Privacy-first is a line I've said in every workshop, so I wasn't going to ship the leaky version of my own product. Every customer session runs as its own Linux user, in a directory it can't climb out of, behind a proxy that only reaches the domains I allow, with file access jailed to markdown under one working folder. No API key, no payment secret, nothing sensitive is even present in the container that runs an untrusted turn. I wrote three thousand words on how creepy AI telemetry gets; the same rule applies here.

I keep saying the generic tools are in trouble, and the ones that survive are what an agent plus a skilled human still can't easily replicate. A good harness is exactly that: domain knowledge, in the shape a model can run. Aihar.app is how you sell that work without giving it away. The engine is open-core and self-hostable, because I'd rather you own the front door than rent it from me.

questions.

What is Aihar.app?

Aihar.app is an MCP front door for Claude Code harnesses. It takes a GitHub repo that hosts a Claude Code plugin and runs it as a hidden, server-side Claude Agent SDK session. You mint one signed MCP URL per customer; they add that single URL to their own Claude client (Desktop or Code) and get the harness's results without ever seeing its contents.

Does my harness stay private?

Yes. The plugin, prompts, and skills never leave the server. Each customer session runs under its own Linux user in an isolated directory (mode 0700) it cannot escape, behind an allowlist egress proxy, with tool calls path-jailed to markdown files. The customer's Claude speaks to yours over MCP and receives only results, never the harness.

How does a customer connect?

They run one command, claude mcp add --transport http <name> https://aihar.app/mcp/<token>, or paste the URL into Claude Desktop. That signed, revocable URL is the entire install. Their Claude then talks to your hidden session over MCP; there is nothing to download and no source to leak.

What can I turn into a product?

Any Claude Code plugin that lives in a GitHub repo: a venture-building playbook, a research workflow, a code-review harness, a writing system. If it works as a plugin on your machine, Aihar.app can host it as a sellable MCP endpoint without you open-sourcing the part that makes it good.

Is Aihar.app open source, and what does it cost?

The engine is open-core and self-hostable, so you can run it yourself or read the code. The hosted cloud at aihar.app handles isolation and scale for you. Previewing your repo, signing in, and importing your first repo are free; an active subscription, billed through Stripe, unlocks additional products and minting customer MCP URLs.

Gabriel Ceicoschilinkedin ·x ·github ·aibl.to