Connect AI tools

Give Cursor, Claude, ChatGPT, Codex, and similar tools access to Keystone over MCP (or the HTTP API) without exposing the whole company.

People use the console with email sign-in. Agents use API keys.

Create a key

  1. Open Settings → Keys (or the Connect page for copy-paste snippets).
  2. Create a workspace key for a bot or a personal key for your own agent.
  3. Grant at least: recall, retain, reflect, and feedback (names appear as memory:* style scopes in the UI).
  4. For a department agent, set bound scopes to that team only.

Treat the secret like a password—show it once, store it in your agent host’s secret store.

Bound scopes (recommended)

Binding limits what the agent can see and write to that team (and its projects).

Agent Bind to
Accounting assistant Accounting team scope
Engineering assistant Engineering team scope
Company-wide research bot Organization only if you truly want firm-wide memory

Even if a document was shared too widely in SharePoint, a key bound to Engineering still cannot enter Accounting’s scope.

Do not reuse one unbound org-wide key across every department bot.

Point the host at Keystone

In Cursor (and similar MCP hosts), add a server that calls your Keystone MCP URL with the Bearer key. The Connect page in the console shows the exact URL and JSON for your deployment.

Typical tools the agent gets:

  • Look up organizational facts
  • Save a durable note (agent notes stay non-official until an operator promotes them)
  • Fetch an entity card
  • Send feedback on a recalled fact
  • Ask a short grounded question

What agents can and cannot do

  • They see facts allowed by scope binding and document access.
  • Agent notes do not silently overwrite official documents.
  • Department agents should not receive admin powers (conflicts, merges, connectors) unless you intentionally build a triage bot.

Console vs agent

Path Best for
Console Ask Humans exploring memory with full UI
MCP key Tools that must call Keystone unattended

Operators and owners can browse all scopes in the console for governance; department keys should stay narrow.

Related