connect and share

Your knowledge, where your team already works.

A knowledge base is exposed over MCP with a scoped, revocable token — and shared with roles. Here is how the question travels, what gets shared with whom, and how to take it to your own infrastructure.

Mobile appTeam chatTerminal agentInternal systemMCPKnowledge baseindexed, permissioned, citedquerycited answerTextTablesGraphsindexed documents · text · tables · graphs

Swipe the diagram to see all of it.

The app in your pocket

Install Doctiling as an app and query the base from your phone — or let the mobile agent talk to your documents, with history and without losing the thread.

The chat they already live in

Your corporate chat bot consumes the MCP endpoint: people ask in their usual channel and the answer comes back citing the source document.

Coding agents and editors

MCP-compatible desktop clients and coding assistants query your bases as the source of truth. No more pasting half a wiki into a prompt.

CRM, tickets, portals

Anything that can call MCP pulls cited context. Read-only by default, scoped per token, revocable in one click.

who shares with whom

A knowledge base gets shared: with your team, your client or your own systems.

The value is not having a chat. It is one base answering several people and several systems, each with its own permission and its own trail back to the source.

doctor · hospital · patient

Shared clinical practice

Guidelines, protocols and literature in one base. The hospital queries it over MCP from its own tools; the patient gets answers cited from their record, not opinions.

people ops · employees

The handbook people actually read

Policies, agreements and manuals in a single base. Employees ask in the chat they already use and the answer cites the policy in force, down to the clause.

committee · the whole sales floor

One committee, one base

Proposals, call notes and pipeline indexed together. The whole committee asks over the same corpus — and the analyses each person creates stay private.

consultant · one client per base

A portfolio of bases, not a chat

One base per client or domain, isolated from each other, each with its own prompt and tools. Switch context without contaminating the last one.

security & privacy

Built from day one for controlled, private work.

Access, visibility and spending are governed by design — not bolted on later.

Invitation-only access

Sign-in is restricted to an approved allowlist. Nobody wanders in: every seat is granted explicitly — and can be revoked the same way.

Private analyses in shared knowledge bases

Share the corpus, not your drafts. Analyses and variants you create stay visible only to you unless you decide otherwise.

Guardrails on every connection

Outbound tools run over HTTPS only, with private networks and metadata endpoints blocked — and each user's AI spend is capped by a budget you control.

Runs where your data must live

Use the managed cloud, or self-host the very same product on your own infrastructure with a local database — one configuration switch.

free install

Run it on your own machine. Free, no account, no invitation.

The installers and the binaries are public on GitHub: one command and the whole studio runs on 127.0.0.1 against your local SQLite database. Point it at a local model (LM Studio or Ollama) and work without a single document leaving your machine.

See releases on GitHub

Open distribution, not open source: we publish the installers and the binaries; the product code is private. What you pay for is the hosted studio.

macOS · homebrew
brew tap doctiling/tap && brew install doctiling
windows · scoop
scoop bucket add doctiling https://github.com/doctiling/scoop-bucket && scoop install doctiling
linux / macOS · script
curl -fsSL https://raw.githubusercontent.com/doctiling/releases/main/install.sh | sh
$0 · self-hosted

Free to use on your machine

  • The whole studio: knowledge bases, editor, cited agent and mirror view.
  • Single user, local login, no invitation list. Your own AI keys or a local model.
  • Team sharing and MCP endpoints ship switched off in the local profile.
hosted · from $0 sponsored

What you pay for is running it as a team

  • Share bases with roles, per-person private analyses and comments.
  • Managed MCP endpoints with scoped, revocable tokens.
  • Dedicated database, your own domain and support on Gold and Platinum.

Stop planning your RAG. Start operating your knowledge bases.

Request your free access with your email — we review it and send the invitation shortly. No credit card. Already invited? Sign in and your first knowledge base is one click away.

    Connect Doctiling over MCP — apps, chats and coding agents