1
Copy the address
In Riktra, open Settings → Connect AI. The address is shown there, and it is the same for everyone in your company:
2
Add it as a connection
In your AI client, add it as a custom MCP connector. The client will send you to Riktra to sign in.
3
Sign in as yourself
Use your own Riktra account. The connection is per-person, not per-company — which is what lets your private context reach your conversations and nobody else’s.
4
Check that it worked
Open a completely new conversation and ask:
What should I focus on today?The answer should start from your company’s priorities and your own focus, without you explaining anything. If it does not, Settings → Debug: Context shows exactly what a new session receives right now.
What the client receives
The first call an assistant should make isget_boot_context — the company’s direction in one request, sized to a token budget so it fits at the start of every conversation without crowding it out.
After that, get_relevant_context answers specific questions, putting current structured truth first and search matches on top of it. That ordering is deliberate: a stack of old mentions can never outweigh the decision that replaced them.
When the direction changes
Boot context returns an organization revision number that increments whenever shared context changes. A client that caches between runs should compare that number rather than a timestamp. There is nothing to re-sync and nothing to re-explain. The next conversation reasons from the new direction because it fetched it.Every call is authenticated as an individual. There is no anonymous access, and no shared company key that would make one person’s connection indistinguishable from another’s.