Get started

Quickstart

Three steps. Get a key, paste one URL into your agent, and confirm it can remember and recall. No SDK, no install.

1. Get your connection URL

Create a free account at app.kognite.dev, open Connect, and copy your personal connection URL. It looks like this — the token after /t/ both identifies and authenticates you, so treat it like a password:

url

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

The token is a secret. Don’t commit it to a public repo or paste it into a shared chat. You can revoke and rotate keys any time from the dashboard.

2. Add it to your agent

Kognite speaks the standard MCP Streamable HTTP transport. Most clients accept a one-line server entry. Here’s Cursor (.cursor/mcp.json) and Claude Code:

.cursor/mcp.json

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

Claude Code (terminal)

claude mcp add --transport http Kognite 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:

text

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.

Agents don’t always reach for memory on their own. To make recall automatic, add a short rule to your agent (e.g. a Cursor project rule or a Claude Project instruction): “Before answering, callmemory_search; when I state a durable fact, call memory_add.” The dashboard’s Connect page has a ready-to-paste version.

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.