MCP Server
Cortex
io.github.FilippoPilo/cortex
What this MCP does
Stores, searches, recalls, updates, and removes user memories while tracking conflicts and synthesizing relevant context.
Capabilities
Tools
7
tools
cortex_conflicts
Show conflicts
Use this when the user asks what contradicts what in their memory, or when a memory you just read is flagged as conflicting and the user has to decide which version holds. Returns the pairs of contradicting statements with their status. Do not use it as a list of memories: it only returns detected contradictions.
Read only
Input schema
{'type': 'object', 'properties': {}}
cortex_forget
Forget memory
Use this when the user asks to delete a specific memory, given the id returned by search. Ask the user to confirm before calling it: the deletion is permanent and cannot be undone. Do not use it to fix a memory that is merely out of date: saving the corrected version with cortex_write is what keeps the history.
Destructive
Input schema
{'type': 'object', 'required': ['id'], 'properties': {'id': {'type': 'string', 'description': 'The id of the memory to delete, exactly as returned by search'}}}
cortex_recall
Recall & synthesize
Use this when the user asks about a topic as a whole ("what do you know about X", "where are we with X", "catch me up on X"): returns one narrative synthesis of the relevant memories, saying what holds now and what was superseded. Do not use it to look up a single fact or when you need sources to cite: search returns individual memories with their urls.
Read only
Input schema
{'type': 'object', 'required': ['query'], 'properties': {'query': {'type': 'string'}}}
cortex_write
Save memory
Use this whenever the user tells you to remember, note down, keep or save something, in any language. Use it as well when they state something they will need again later and would not want to repeat: a decision and the reason behind it, a stable fact about them or their work, a preference or a constraint, a conclusion they reached after effort, a correction of something believed before. Then say in one line what you saved, so they can tell you to drop it. The server rejects duplicates by itself: a refused write is not an error, do not rephrase it and try again. Do not save questions, brainstorming, passing remarks or anything the user has not actually stated, and never save passwords, tokens, keys, card numbers or other credentials, even if the user pastes them.
Input schema
{'type': 'object', 'required': ['title', 'content'], 'properties': {'tags': {'type': 'array', 'items': {'type': 'string'}}, 'basis': {'enum': ['observed', 'inferred'], 'type': 'string', 'description': "Origine dell'informazione: 'observed' se letta direttamente da una fonte (documento, output di uno strumento, dato reale), 'inferred' se e' una deduzione o una stima. Registrata al salvataggio e restituita al richiamo."}, 'title': {'type': 'string', 'description': 'Short title, in the user\'s language, e.g. "Billing service: chosen database"'}, 'claims': {'type': 'array', 'items': {'type': 'object', 'required': ['subject', 'predicate', 'object'], 'properties': {'object': {'type': 'string'}, 'subject': {'type': 'string'}, 'predicate': {'type': 'string'}, 'claim_text': {'type': 'string'}, 'confidence': {'type': 'number'}}}, 'description': "Opzionale. Fatti atomici gia strutturati, uno per decisione o affermazione: se li passi, il rilevamento dei conflitti li usa direttamente invece di estrarli dal testo. Esempio: {subject: 'Project Vega', predicate: 'adotta', object: 'Redis'}."}, 'content': {'type': 'string', 'description': "Text to remember, in the user's language"}, 'event_time': {'type': 'string', 'description': 'Optional. Set only when an explicit, unambiguous ISO 8601 date (e.g. 2026-09-28 or 2026-09-28T14:00:00Z) of the event or measurement applies to the whole memory. Never infer a date and never use the save date: omit it if unknown. Save facts from different dates as separate memories.'}}}
cortex_write_status
Write status
Use this when a previous cortex_write returned a job_id as queued and the user asks whether it was saved: returns the quality gate verdict for that job and any contradiction it opened. Do not call it for a write that already came back with a verdict.
Read only
Input schema
{'type': 'object', 'required': ['job_id'], 'properties': {'job_id': {'type': 'string', 'description': 'The job_id returned by a cortex_write that came back as queued'}}}
fetch
Fetch memory
Use this when a search result looks relevant and you need its full text before answering. Takes the id returned by search, and returns the memory with its url, which you cite in your answer. Do not call it with an id from anywhere else: only search results carry valid ids.
Read only
Input schema
{'type': 'object', 'required': ['id'], 'properties': {'id': {'type': 'string', 'description': 'The id of a memory, exactly as returned by search'}}}
Output schema
{'type': 'object', 'required': ['id', 'title', 'text', 'url'], 'properties': {'id': {'type': 'string'}, 'url': {'type': 'string'}, 'text': {'type': 'string'}, 'title': {'type': 'string'}, 'metadata': {'type': 'object'}}}
search
Search memories
Use this when the answer depends on the user's own context: facts about them or their work, decisions they made, preferences or constraints they stated, or anything they refer back to from an earlier conversation ("as we agreed", "my project", "the client we discussed"). Use it as well when the user asks for something done their usual way, in their format, tone, style or stack ("the way I normally write these", "my usual setup"): their way is what the memory holds. Also use it when the user asks what you know or remember about something. Returns the matching memories with id, title and url to cite; fetch returns the full text of one. Cortex is the user's own memory layer: what is saved through it stays available in the other AI apps they connect to the same account. Do not use it for general knowledge, for questions that do not depend on this particular user, or when everything needed is already in this conversation.
Read only
Input schema
{'type': 'object', 'required': ['query'], 'properties': {'query': {'type': 'string', 'description': 'What to look for, in natural language and in the user\'s own words, e.g. "which database we chose for billing"'}}}
Output schema
{'type': 'object', 'required': ['results'], 'properties': {'results': {'type': 'array', 'items': {'type': 'object', 'required': ['id', 'title', 'url'], 'properties': {'id': {'type': 'string'}, 'url': {'type': 'string'}, 'title': {'type': 'string'}}}}}}
History
Recent tool changes
Changed
cortex_write
Oct. 1, 2026, 2:45 a.m.
Changed
cortex_conflicts
Sept. 19, 2026, 2:41 a.m.
Changed
cortex_forget
Sept. 19, 2026, 2:41 a.m.
Changed
cortex_write_status
Sept. 19, 2026, 2:41 a.m.
Changed
cortex_write
Sept. 19, 2026, 2:41 a.m.
Changed
cortex_recall
Sept. 19, 2026, 2:41 a.m.
Changed
fetch
Sept. 19, 2026, 2:41 a.m.
Changed
search
Sept. 19, 2026, 2:41 a.m.
Added
cortex_conflicts
Sept. 17, 2026, 12:41 p.m.
Added
cortex_forget
Sept. 17, 2026, 12:41 p.m.
Added
cortex_write_status
Sept. 17, 2026, 12:41 p.m.
Added
cortex_write
Sept. 17, 2026, 12:41 p.m.
Added
cortex_recall
Sept. 17, 2026, 12:41 p.m.
Added
fetch
Sept. 17, 2026, 12:41 p.m.
Added
search
Sept. 17, 2026, 12:41 p.m.
Discover
Similar MCP servers
Stable Baseline
io.stablebaseline/sb
Manages company documents, knowledge graphs, whiteboards, projects, plans, tasks, teams, and improvement workflows.
Dayze — Life Context
com.dayze/life-context
Provides authenticated personal life-context data and tools for contacts, memories, events, expenses, trips, assets, places, and …
YouSpot
com.youspot/youspot
Connects personal contacts, companies, notes, files, CRM records, email, Slack, LinkedIn, and calendars, with search, relationshi…
mcp
io.nestr/mcp
Manages Nestr workspaces, roles, circles, tensions, governance proposals, comments, daily plans, graph relationships, agents, and…
personalbrain-mcp
io.github.lonniev/personalbrain-mcp
Provides read and write access to a personal knowledge graph, including thoughts, notes, links, attachments, queries, and change …
Kaiku
tech.kaiku/kaiku
Manages team issues, comments, attachments, projects, wiki pages, and related development workflows.
Dock
ai.trydock/dock
Provides collaborative workspaces with tables, documents, HTML surfaces, files, formulas, comments, activity tracking, agent mess…
ContextLayer
io.github.DotNova/context-layer
Stores and retrieves organizational documents and knowledge-graph context while managing projects, tasks, teams and work sessions.