Does this work with Cline's Memory Bank pattern?

Yes — and it replaces the manual parts. Instead of maintaining markdown memory files per project, Cline calls remember/recall against one deduplicated store, shared across all your projects and tools.

Does Cline save memories automatically?

Yes — once connected, the agent has remember and recall as callable tools and uses them on its own: it saves decisions and preferences mid-conversation and retrieves them when they're relevant. You can also tell it explicitly to remember something.

Memories are owner-scoped to your account, served over HTTPS, with encryption at rest for stored content and an audit trail of what agents wrote. You can review, edit, and delete every memory from the dashboard.

Can my other AI tools share this memory?

Yes — that's the point. The same store is reachable from every MCP client and over REST, so what Cline learns, Claude, Cursor, and your own code can recall too.

There's a free plan — an account and API key cost nothing, and setup takes about two minutes. Paid plans add higher quotas and team features.

Memory for every AI tool

Persistent memory for Cline

Cline forgets everything between sessions. Connect it to Kit for AI and it saves what matters as it works — and recalls it in any later session, on any machine.

Why Cline forgets

Cline runs long autonomous coding tasks in VS Code, but each task starts with an empty head — it re-discovers your project's constraints every time. Give it a memory MCP server and it carries decisions and gotchas from task to task, project to project.

What you get

remember / recall as tools the agent calls on its own — no manual note-keeping.
Retrieval by meaning: "what did we decide about auth?" finds the JWT decision.
One shared store: what this tool learns, Claude, Cursor, and your code can recall too.
Near-duplicate detection and versioning keep months of memories clean.
Same account ingests documents and URLs — memory and knowledge in one retrieval system.

Set it up in about 2 minutes

1In VS Code, open Cline → MCP Servers icon → Configure MCP Servers (opens cline_mcp_settings.json).
2Add the kit-for-ai block (below).
3Create a free API key at kitforai.com/app/settings and replace YOUR_API_KEY.
4Save — Cline lists the memory tools and calls them as it works.

{
  "mcpServers": {
    "kit-for-ai": {
      "type": "http",
      "url": "https://kitforai.com/api/mcp",
      "headers": { "x-api-key": "YOUR_API_KEY" }
    }
  }
}

Give Cline a memory today

Free account, one API key, one config block. What Cline learns today, every AI tool you use can recall tomorrow.

Start free How the MCP memory server works

FAQ

Does this work with Cline's Memory Bank pattern?: Yes — and it replaces the manual parts. Instead of maintaining markdown memory files per project, Cline calls remember/recall against one deduplicated store, shared across all your projects and tools.
Does Cline save memories automatically?: Yes — once connected, the agent has remember and recall as callable tools and uses them on its own: it saves decisions and preferences mid-conversation and retrieves them when they're relevant. You can also tell it explicitly to remember something.
Is my data private?: Memories are owner-scoped to your account, served over HTTPS, with encryption at rest for stored content and an audit trail of what agents wrote. You can review, edit, and delete every memory from the dashboard.
Can my other AI tools share this memory?: Yes — that's the point. The same store is reachable from every MCP client and over REST, so what Cline learns, Claude, Cursor, and your own code can recall too.
Is it free?: There's a free plan — an account and API key cost nothing, and setup takes about two minutes. Paid plans add higher quotas and team features.

Memory for your other tools

Deep dive: how to share one memory across all your AI models.