Where Kijito stands today, what to expect during the beta, how to reach us, and what to try if your AI won't connect.
Kijito is in public beta. It runs as a single-box service on a best-effort basis: we aim to keep it up and respond quickly to outages, but there is no formal uptime guarantee or SLA yet. We do nightly encrypted backups and watch the service for problems. If something looks broken, it may genuinely be. Reach out and we'll take a look.
Updates restart the service, usually once a night around 08:00 UTC. It's back in under a minute, and during it your agent may see a slow or failed call. That's expected: it should wait 30 seconds and retry. We'll give notice before any longer maintenance.
To report a security vulnerability or abuse, email [email protected]. For anything else (billing, data requests, general questions) email [email protected]. Please don't include secrets, passwords, or recovery codes in an email.
A few things to check, in order:
https://api.kijito.ai/mcp (this is the only hosted transport).kijito_remember, kijito_recall, kijito_dream and the rest. If not, fully restart the client/session. Many clients only load connectors at startup.claude mcp add --transport http --scope user kijito https://api.kijito.ai/mcp, sign in with claude mcp login kijito in your own terminal, then restart Claude Code. If you added it for one project only, start Claude Code from that project's folder. The steps are in the quickstart.Still stuck? Email [email protected] with your client name and what you tried. We read every message.