Get started

Quickstart

Three steps. Paste one URL into your agent, approve it in the browser, and confirm it can remember and recall. No key to copy, no SDK, no install.

1. Add Kognite to your agent

Kognite speaks the standard MCP Streamable HTTP transport and implements the MCP authorization flow (OAuth 2.1 with PKCE and dynamic client registration). Nothing to copy and no account to create first — add the server, and your client handles the rest. Here’s Cursor (.cursor/mcp.json) and Claude Code:

{
  "mcpServers": {
    "Kognite": {
      "url": "https://mcp.kognite.dev/mcp",
      "type": "streamable-http"
    }
  }
}

claude mcp add --transport http Kognite https://mcp.kognite.dev/mcp

2. Approve the connection

Your client opens a browser tab. Sign in or create your free account right there, approve the connection, and the client keeps a short-lived token it refreshes on its own. You can revoke it later from API Keys → Connected applications.

Prefer to paste a key instead?

For a client that can’t do the browser handshake, create a key at app.kognite.dev under Connect and put it in the URL instead. The token after /t/ both identifies and authenticates you, so treat it like a password: don’t commit it to a public repo or paste it into a shared chat, and rotate it from the dashboard if it leaks.

https://mcp.kognite.dev/t/YOUR_KEY

Using Claude Desktop, VS Code, ChatGPT, Windsurf, Zed, or JetBrains instead? Each has its own config shape — see MCP clients for the exact block and the gotchas (Claude Desktop needs the mcp-remote bridge; Copilot caps the tool count).

3. Remember something, then recall it

Restart the client so it picks up the new server — you should see Kognite’s memory_*tools listed. Now, in an agent chat, tell it a durable fact and confirm it persisted:

You:  Remember that I deploy to Hetzner and never use Railway.
Agent: (calls memory_add) ✓ stored.

—— new conversation, or a different tool, later ——

You:  Where do I deploy?
Agent: (calls memory_search) You deploy to Hetzner — you never use Railway.

That’s the whole loop. The memory persists across sessions and is shared by every tool pointed at the same key, so a fact learned in Cursor is recalled in Claude Code.

Prefer plain HTTP?

If your agent isn’t MCP-capable — a backend job, a custom loop — use the same operations over the REST API with a Bearer key.