vancetope
GitHub Get started

Clients & integrations

One brain. Many doors.

The Brain on your server holds every project, document and running agent. Everything else is a way in — for you on whichever device is at hand, for your files and tools, and for other agents that want to work with yours.

Clients

Meet it where you work.

Clients aren’t views on the same screen — each is an entry point with its own strengths, into the same projects.

web

Browser

The full working environment: Cortex, chat, inbox, every app and document kind, settings — switching between them keeps the connection.

macOS

Desktop app

The workspace in a native window — whose agents can work on files on your Mac, behind a sandbox. Live tabs per profile.

 vancetope

Terminal

A CLI agent with local shell, files and git — but always inside a project, with everything stored in it.
iOS · Android

Mobile in review

The workspace on phone and tablet, several accounts side by side, optional PIN lock. iOS is in App Store review, Android in testing.

Chrome · Firefox · Safari

Capture in review

A browser extension: save a link to your links app, or import the page you’re looking at as a document — exactly what the browser shows.

MCP

Any agent

Claude Code, Cursor or anything else that speaks MCP can read and write your projects — through doors you open, with OAuth.

Desktop · new in 0.5

A desktop app whose agents touch your files.

The server can’t see your laptop — the desktop app can. Agents get client_file_* and client_exec_* on your Mac, so they can read a folder, run a build or fix a script right where it lives.

  • Sandbox policy per account: deny, allow, ask — with a confirm button in the app.
  • Workdir confinement and a master switch that says so loudly when it’s off.
  • MCP tool packs straight from ~/.vancetope/mcp.json, per project if you like, credentials kept in the app.
  • Live tabs per profile, ⌘1…⌘0, two-finger swipe back.

Signed and notarized for macOS — Apple Silicon and Intel. Install with Homebrew or download the .dmg.

$ brew install --cask mhus/vancetope/vancetope-desktop

Desktop agent tools spec →

# ~/.vancetope/mcp.json — passed through to agents
{
  "mcpServers": {
    "github": {
      "command": "github-mcp-server",
      "args": ["stdio"]
    }
  }
}

agent  client_exec_run  "mvn -q test"
gate   ask → allowed once

Terminal

A CLI agent that stays in the project.

The vancetope client is a full terminal UI: chat with live reasoning, a job browser, a recipe picker, questionnaires answered line by line. Its local tools go through the same permission gate as the desktop app.

  • Login in the browser with /login --browser — no password typed into a terminal.
  • Tool packs — MCP and REST/OpenAPI, global or per project, behind a trust prompt.
  • Remote control: steer a running terminal session from the web or your phone.
  • Homebrew or Java-free bundles for macOS, Linux and Windows.

CLI guide →

$ brew install mhus/vancetope/vancetope
$ vancetope
› /login --browser
  ✓ signed in · tenant acme · project webshop
› /new coding
› run the tests and fix what breaks
  exec  mvn -q test        ask → allow
  edit  CartService.java  ✓
  exec  mvn -q test        ✓ 214 passed

MCP doors · new in 0.5

Let other agents in — through doors you open.

Vancetope speaks MCP both ways. Outward it uses your MCP servers as tools; inward it is an MCP server — three doors, each as narrow as it needs to be, all behind a real OAuth 2.1 authorization server.

/brain/{tenant}/mcp

The tenant door

The full tool inventory for your own coding agent — documents, research, processes.

 /brain/{tenant}/mcp/{project}

The project door

Only doc_*, only one project, read-only or read-write, limited to path prefixes — set in a config document.

 /brain/{tenant}/agents

The agents door

Talk to a persistent agent, not to tools: the gate decides, the conversation runs, it closes when idle.
oauth 2.1

A lock on every door

An issuer per tenant, consent for foreign clients, rotating refresh tokens with replay revocation, dynamic client registration and client-ID metadata documents. MCP hosts connect with a browser login — no token pasting.

 tokens

Integration tokens

For tools that can’t do OAuth: long-lived credentials narrowed to a profile and pinned to one project. Narrowing only ever cuts — a token never adds rights.

Reaching out

The rest of your world, pulled in.

What lives elsewhere stays there — Vancetope reads it, mounts it, searches it, and sends finished work back out.

tool packs

MCP & REST packs

Any MCP server or OpenAPI description becomes a set of agent tools — on the server, in the terminal or on the desktop.

 zarniwoop

Research sources

Web search and crawling via exa, firecrawl or SearXNG — each source a document you configure and route.

 centauri

Feeds

Streams from several sources merged by cursor — Mastodon timelines and hashtags included.

 jaglan

Mounted folders

Foreign files appear under _ext/ and read like documents — a host directory or another application.

 grab

Web grab

The page your browser shows, turned into a document — no second request, so logins and paywalls you passed stay passed.

 webdav

Finder & Obsidian

Mount a project as a drive and work on its documents with your own tools.

 connectors

Jira, GitHub & co.

Finished work goes where it belongs — issues, repos, docs — instead of Vancetope pretending to be them.

 milliways

Share by mail

Send a document via SMTP or Gmail, or into someone’s inbox on the same server.

 scripts

Script API

vance.documents.* for JavaScript and Python — the same document surface the agents use.