Documentation
Plug it in, run it, keep control.
Kastel holds your company's knowledge and exposes it over the MCP protocol to the AIs of your choice. These guides cover the path from your Kastel to the AI your teams already use.
Where to start
Hosted by KastelYour first dayCreate the space, connect your AI keys, open it to the team.Self-hostInstall KastelThe free plan, on your own servers, in one command.IntegrationPlug in an AIClaude, Cursor, ChatGPT, or any other MCP client.01
Get started
From signup to an AI that answers on your real files.
Your first dayFrom signup and payment through to an AI that answers.Invite your teamThe four roles, passwordless sign-in, your company directory.02
Connect your AI
The scoped token, the block to paste, the AI your teams already use.
Connect your AIScoped token, a ready-to-paste block per AI, five-minute start.03
Install
Get Kastel running on your own infrastructure, and keep it there.
Install KastelOne command, no account, no call back to our servers.Your AI keysYour key, your provider, billing you directly.Fully localOllama, vLLM or LM Studio: no inference leaves your infrastructure.Back up, migrate, verifyVerifiable backups, portable export, upgrades never automatic.04
Connectors
Plug in your sources: what gets read, by whom, and how to unplug it.
How a connector worksWho authorises, what gets resynced, the two ways to unplug.Your Google applicationWhy it has to be yours, and how to create it in ten minutes.Google DriveWhat gets read, what never does, the default window.NotionThe integration, the pages you share, a clean removal.SlackThe workspace, the private channels, what gets synced.05
Govern
Who has access, who decides, what gets erased.
Who has access, who decides, who consulted whatEach person's scope, what a plugged-in AI inherits, the log.Approve, correct, roll backThe decision queue, all-or-nothing approval, governed rollback.GDPR erasureWhat goes when a document disappears, and what it never reaches.What runs on its own at your companySix on the register, three you can stop.06
Operate
Day to day: upkeep, costs, departures, exit.
Keeping your Kastel in good shapeWhat decays, the weekly check, contradictions and statements.AI costs and capsYour keys, your bill, the monthly cap and its two exceptions.If you stopFull export, what read-only means, the six expiry notices.When someone leavesWhat removal cuts, what it does not, what deliberately stays.07
Reference
The technical contract, generated from the engine.
MCP toolsEvery tool, its parameters, what it returns, how it refuses.The command lineThe full kastel command inventory, generated from the engine.The configuration fileThe one settings file, exactly as the installer writes it.The HTTP APIWhat Kastel exposes to a machine, and what it does not.