This server has a remotely hosted endpoint. Open its connector listing for connection details, authentication requirements, and setup instructions:
One external brain, model-agnostic, in production. Connect it to Claude in two minutes — free trial, no credit card.
Cortex is a patent-pending semantic memory infrastructure developed by SKYNETLAB (Bergamo, Italy). Connected to your AI assistant as a remote MCP connector, it lets your conversations save decisions, context and sources — and find them again in every later session. Your AI remembers, and can show why it remembers.
🌐 Website: skynetlab-cortex.com · 📄 Patent · 📊 Benchmark · 📚 Paper · 💶 Pricing
🇮🇹 Versione italiana: README.it.md
Most memory tools for AI agents record what the agent did and retrieve similar text later. Cortex models what is true and how reliable it is:
Capability | What it means |
Quality Gate on write | Every memory passes a novelty/redundancy check before being stored. No junk accumulation. |
Typed claims & conflict tracking | Facts are extracted as claims; contradictions between memories are detected and tracked, not silently overwritten. |
Knowledge graph | Memories are linked by entities and typed relations, not just vector similarity. |
Coherence metric (Ψ_C) | Each memory carries a native coherence score — the system knows how well a memory fits what it already knows. |
Memory consolidation ("REM") | A continuous background cycle consolidates episodic memories into long-term knowledge. |
Transparent evidence | Answers can cite the memories and sources they come from. |
Cortex runs on globally distributed edge infrastructure operated in the European Union. The memory engine is covered by Italian patent application UIBM 102026000014026 (filed 15 May 2026).
Related MCP server: Cogniz Memory Platform MCP Server
Requirements: a Claude plan that supports custom connectors (the "Connectors" entry appears in Settings). No Cortex account needed beforehand — it is created on first sign-in.
In Claude open Settings → Connectors → Add custom connector
Paste this URL and confirm:
https://skynetlab-cortex-saas-mcp.cortex-320.workers.dev/mcpAuthorize access on the Cortex consent page (Google or email sign-in). Your personal memory space is created automatically, isolated from every other user.
That's it. Talk to Claude as usual: "Remember that we chose supplier X", "what did we decide about the budget?", "show me the sources for this claim". Claude picks the right tool on its own.
claude mcp add --transport http cortex https://skynetlab-cortex-saas-mcp.cortex-320.workers.dev/mcpThen authenticate when prompted (/mcp shows connection status).
For MCP clients that don't support remote connectors natively, use the mcp-remote bridge. Example configuration (see examples/):
{
"mcpServers": {
"cortex": {
"command": "npx",
"args": ["-y", "mcp-remote", "https://skynetlab-cortex-saas-mcp.cortex-320.workers.dev/mcp"]
}
}
}This repository also ships a small stdio MCP server (server/) that exposes the Cortex tools locally and forwards every call to the hosted service. It is meant for MCP clients, registries and evaluators that need a local process: it starts, lists its seven tools and answers introspection with no configuration at all; tool calls are forwarded when an access token is set.
git clone https://github.com/FilippoPilo/cortex-connector.git
cd cortex-connector
npm install
CORTEX_ACCESS_TOKEN=<your token> node server/index.jsOr with Docker:
docker build -t cortex-connector .
docker run -i --rm -e CORTEX_ACCESS_TOKEN=<your token> cortex-connectorVariable | Meaning |
| Bearer token for the hosted connector (the OAuth access token issued at sign-in, for example the one |
| Remote endpoint, defaults to the hosted Cortex connector. |
npm test runs a self test (initialize, tools/list, one call without token).
Tool | Type | Description |
Search memories | read | Semantic search across your memories |
Fetch memory | read | Full detail of one memory, with its sources |
Recall & synthesize | read | Narrative synthesis of what Cortex knows about a topic |
Show conflicts | read | Tracked contradictions between memories |
Save memory | write | Stores a memory — after a quality check against duplicates and redundancy |
Write status | read | Outcome of a queued save: quality-gate verdict and any open conflicts |
Forget memory | destructive | Deletes a memory — always with explicit confirmation |
Memories are personal: each user only sees their own. They are exportable and deletable on request, and the infrastructure operates in the European Union. Details: Privacy Policy.
To disconnect, simply remove the connector from your client's settings; your memories remain in your Cortex account until you request their deletion.
The Cortex memory engine is a hosted, patent-pending service — its source code is not published. This repository contains the public documentation, the client-side configuration examples and a small stdio bridge (server/) for connecting to it. Everything in this repository is released under the MIT License.
📧 info@skynetlab.net · Contact page
Cortex is a SKYNETLAB product — independent research lab & deeptech studio, Bergamo, Italy. Founder: Filippo Pilotta (ORCID 0009-0000-5002-4199).
Some content and product outputs are generated or assisted by artificial intelligence, pursuant to Art. 50 of Reg. (EU) 2024/1689. AI transparency.
Show the contradictions detected between memories, with their open or resolved state.
Inputs: no named parameters.
Delete a memory given its id. Ask the user for explicit confirmation first.
Inputs: id (required).
Narrative synthesis of what the user's memory knows about a topic, with the current state and what was superseded. Use it for questions like 'what do you know about X' or 'what is the current state of X'.
Inputs: query (required).
Save to the user's persistent memory (Cortex), on your own initiative while the conversation goes on: decisions and the reason behind them, stable facts about the person and their work, preferences and constraints they state, conclusions reached after effort, mistakes made and what they cost. Every write passes a quality gate: duplicates are rejected by the server and a refused write is not an error. Never save passwords, tokens, keys or card numbers.
Inputs: title (required), content (required), tags, basis, +1 more.
Outcome of a save that cortex_write returned as queued: verdict of the quality gate and any open conflicts.
Inputs: job_id (required).
Fetch the full text of a memory by its id (from search), with its history and sources. Cite its url when you use it.
Inputs: id (required).
Search the user's persistent memory (Cortex). Call it at the start of every conversation and before any answer that depends on who the user is or on what you did together before: the user must not have to repeat themselves. Returns results with id, title and url to cite. If it returns nothing, the memory is new or empty: tell the user once that you are connected to Cortex and offer to save what you are working on with cortex_write.
Inputs: query (required).
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Scored across 7 tools
Most tools have distinct purposes: conflicts, forget, write, status, and fetch are clear. However, search, fetch, and recall all involve retrieving memory content and could overlap in practice, requiring careful description reading to pick the right one.
Naming is inconsistent: some tools use the cortex_ prefix (cortex_conflicts, cortex_forget, cortex_recall, cortex_write, cortex_write_status) while others do not (search, fetch). The pattern is not uniform, and cortex_write_status breaks the simple verb_noun structure.
Seven tools is a reasonable, focused set for a persistent memory server. Each tool covers a needed operation without feeling bloated or sparse.
The toolset covers the core memory lifecycle: write, read via search/fetch/recall, delete via forget, plus conflict and status handling. An explicit update or list-all operation is missing, but write can likely serve as upsert and search covers listing, so the surface is largely complete.
Shared memory MCP server for Claude Code, Codex, Gemini CLI and Cursor. Cited, editable.
Persistent memory for AI assistants. Save once; recall from Claude, ChatGPT, or any MCP client.
Shared memory and mail for your AI agents. Verified with Claude Code; other MCP clients in testing.
Persistent memory, knowledge graph, task management and more for AI agents via MCP.
