How it works

From zero to your AI reaching your machine.

Four steps. About a minute each. No cloud console, no proxy to configure, no networking chapter to read first.

  1. Step 1 · ~30 seconds

    Create your account

    Sign in with Google or GitHub. No credit card, no email verification, no cold-start survey.

  2. Step 2 · ~1 minute

    Add your first connector

    Pick one from the catalog — filesystem to reach your files, kubectl to reach your cluster, github to reach your repos. Scope what it can touch. That's it.

  3. Step 3 · ~30 seconds

    Install the desktop app

    One binary for macOS, Windows, or Linux. It auto-picks up the MCP you configured and opens a per-user encrypted tunnel to us.

  4. Step 4 · ~1 minute

    Connect your AI

    Grab the URL, paste it into your AI. It reaches every connector you set up, only while your desktop is running.

New to MCP? It's the shared language AI apps use to reach tools and data outside themselves — like a universal port. Claude, ChatGPT, and others already speak it, which is why they all work here.

Should work with any AI that speaks MCP
AI chat apps
Claude ChatGPT Gemini LibreChat and others
Agentic coding tools
Claude Code Aider Continue.dev Copilot Opencode OpenClaw and others

Anything that speaks the Model Context Protocol should work — this is a shortlist of apps we know speak it, not a promise we've end-to-end tested every one. If you hit a snag with one of these, or use one we didn't name, tell us.

Once connected

You just ask, in plain language.

Type it into the AI you paired in step 4 — from wherever you are, whatever's in your hand.

From a park bench
in Claude on your phone
You
Pull that architecture doc from ~/proposals and read me the intro.
reads ~/proposals/architecture.md
Between meetings
in ChatGPT
You
What changed in the api service today? Summarise it and flag anything risky.
runs git log on ~/projects/api
From the shop counter
in Gemini on mobile
You
Draft a follow-up email to the customer from yesterday's estimate.
reads ~/business/estimates/2026-07-25.md
Common questions

The bits people ask before signing up.

What is MCP?
The Model Context Protocol — a common language AI apps use to safely reach files, tools, and data outside themselves. Anthropic created it for Claude, but many AI apps now speak it (ChatGPT, Gemini, LibreChat, agentic coding tools, and more). Think of it as a universal port: if your AI supports MCP, this platform is how it plugs into your machine.
Why configure the MCP before installing the client?
Two reasons. First, it keeps the meaningful part of the setup — picking a tool and scoping its access — where you already are, in the dashboard. Second, when you then install the client, it auto-picks up the config you already chose. No context-switching, no half-set-up moments.
What if my machine restarts or the app crashes?
The desktop app restarts with the OS and reconnects automatically with exponential backoff. Your connector URL stays valid — no re-configuration on the AI side. If your machine is off, requests get a clear error until it's back.
What data actually leaves my machine?
Only the response to a specific request your AI made — a file's contents when it asked for it, a directory listing, a command's output. Never a whole folder, never on a schedule, never as a background sync. When the desktop app is closed, nothing crosses the tunnel until you open it again.
What does folder-scoping mean, exactly?
For each MCP, you list the absolute paths it's allowed to reach. The MCP only sees those. Path validation runs inline in the dashboard, so you can't accidentally expose your home directory by typo. Add, remove, or re-label folders any time; the next request sees the change.
Can I revoke access at any time?
Yes — three ways. Close the desktop app (tunnel closes, no requests can reach your machine). Remove folders from the dashboard (the AI immediately loses access to them). Rotate your OAuth credentials from Profile → Credentials (invalidates any existing AI-side connector until you re-paste).
Does it work offline?
No — that's by design. Every request is authenticated through our server, so if your machine can't reach us, your AI can't reach your machine either. In exchange you get per-user isolation, an audit trail, and revocation you can actually rely on.

Give it four minutes.

Free forever for two MCPs. No card, nothing to uninstall if it isn't for you.

Get started free

macOS · Windows · Linux — one small binary

Are you sure?

Configure connector

The JSON below is a copy of the connector's config schema. Fill in your values, then Save. Each top-level key becomes an environment variable the MCP process reads at spawn time.

Values are blurred by default and only visible while you're typing. Click Show to keep them visible; Hide to blur again.

Help test this connector

Record a short screen-capture that shows the connector working (or failing) end-to-end. Approved submissions earn you Pro-equivalent limits on this specific connector for as long as your account exists.

YouTube, Loom, Vimeo, or Google Drive links are accepted. Unlisted / private links are fine as long as our admin can open them.

Cookie preferences

Choose which categories of cookies we may use. You can change this any time via the footer link.

Essential

Session cookie that keeps you signed in. Required for the site to function.

Always on