AiAkiv Memory
Server Details
Shared long-term memory for AI agents: save and recall context as a searchable knowledge graph.
The last two health checks of this connector failed. If this server requires authentication, missing or expired test credentials may be the cause. A test profile lets Glama authenticate for health checks and discover tools; it is separate from your personal connections.
If you are the author, claim ownership, then add or update a test profile under Admin → Test Profile.
- Status
- Unhealthy
- Uptime
- 42.5% over 79 days
- OAuth
- Works in Glama
- Last Tested
- Transport
- Streamable HTTP
- URL
- Repository
- AiAkiv/aiakiv-plugins
- GitHub Stars
- 0
- ChatGPT
- AiAkiv Memory
- Claude
- –
TDQS
Scored across 21 tools
The set is unusually well-routed: descriptions explicitly distinguish search vs entity lookup vs graph traversal vs SQL vs timeline, and the partner tools mirror the own-memory tools clearly. Some boundaries remain subtle, especially among find_memory_connections, query_memory_graph, and search_memory, but the do-not-use guidance keeps misselection low.
All tools use snake_case, verb-first names with predictable noun phrases, and the own/partner variants are paired symmetrically. Minor verb variation such as find/search/query/list/get reflects real distinctions rather than inconsistency.
Twenty-one tools is heavy for an MCP surface, especially with multiple mirrored partner/graph/search variants plus separate guide, card, and app-action tools. Each tool has a role, but the count sits in the borderline-heavy 16-25 range and increases selection overhead.
Core memory lifecycle is covered: save, search, fetch, update, hide, plus timeline, entity lookup, graph, SQL, projects, partner reads, and card creation. Gaps are largely intentional console/operator actions: no permanent delete or un-hide, no partner-link create/revoke, no card edit/delete, and no direct save-target switch.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
2 tool updates
- Changed
save_memory1 field changed- changed
Input schema / properties / summary / descriptionPrevious value: -"The retrieval surface, required unless `payload`, up to 500 characters. Searches rank against this rather than the content, so exact identifiers kept verbatim and the acting party named in the first sentence are what make the record findable later."New value: +"The retrieval surface, required unless `payload`, up to 500 characters. Searches rank against this rather than the content, so exact identifiers kept verbatim and the acting party named in the first sentence are what make the record findable later. For a decision or an implementation, one sentence on why this option was chosen over the alternatives lets a later \"why\" question find it."
- Changed
update_memory2 fields changed- added
Input schema / properties / add_entity_renamesAdded value: +{ + "anyOf": [ + { + "items": { + "additionalProperties": true, + "type": "object" + }, + "type": "array" + }, + { + "type": "null" + } + ], + "default": null, + "description": "Pairs `{\"old\": \"...\", \"new\": \"...\"}` (entity names or ids) recording that an entity was renamed, so a lookup by either name also returns the other. Both must already exist in this event's team; each pair also links both entities to this event. Idempotent; failures come back in `rejected_entity_renames`.", + "title": "Add Entity Renames" +} - added
Input schema / properties / remove_entity_renamesAdded value: +{ + "anyOf": [ + { + "items": { + "additionalProperties": true, + "type": "object" + }, + "type": "array" + }, + { + "type": "null" + } + ], + "default": null, + "description": "Same shape, removing such a pair. Entity links stay. A pair in both lists is refused as `conflicting_request`.", + "title": "Remove Entity Renames" +}
1 tool update
- Changed
save_memory1 field changed- changed
Input schema / properties / tags / descriptionPrevious value: -"List of short slash-paths. Reusing the closest paths from a prior response's `suggested_tags` or `tag_tree` keeps them consistent. Ids, hashes, and dates are soft-rejected."New value: +"List of short tags. Reusing tags from a prior response's `suggested_tags` first, then `tag_tree`, keeps them consistent. An existing tag not shown in those lists still matches when written by its name. Ids, hashes, and dates are soft-rejected."
2 tool updates
- Changed
get_aiakiv_memory_guide1 field changed- changed
Input schema / properties / topic / descriptionPrevious value: -"One of `\"tour\"` (first-run tutorial, llms-tour.txt), `\"playbook\"` (projects and personas, llms-playbook.txt), `\"setup\"` (install and connect, llms.txt), or `\"demo\"` (public demo-memory walkthrough, llms-tour-demo.txt). It defaults to `\"tour\"`, so a request for one of the other three carries the topic. Any other value returns an error listing these four."New value: +"One of `\"tour\"` (first-run tutorial, llms-tour.txt), `\"playbook\"` (projects and personas, llms-playbook.txt), `\"setup\"` (install and connect, llms.txt), `\"demo\"` (public demo-memory walkthrough, llms-tour-demo.txt), or `\"console\"` (the console app actions for teams, links, audit and cards, llms-console.txt). It defaults to `\"tour\"`, so a request for one of the other four carries the topic. Any other value returns an error listing these five."
- Added
run_aiakiv_app_action
2 tool updates
- Changed
get_aiakiv_memory_guide1 field changed- changed
Input schema / properties / topic / descriptionPrevious value: -"One of `\"tour\"` (first-run tutorial, llms-tour.txt), `\"playbook\"` (projects and personas, llms-playbook.txt), `\"setup\"` (install and connect, llms.txt), `\"demo\"` (public demo-memory walkthrough, llms-tour-demo.txt), or `\"console\"` (the console app actions for teams, links, audit and cards, llms-console.txt). It defaults to `\"tour\"`, so a request for one of the other four carries the topic. Any other value returns an error listing these five."New value: +"One of `\"tour\"` (first-run tutorial, llms-tour.txt), `\"playbook\"` (projects and personas, llms-playbook.txt), `\"setup\"` (install and connect, llms.txt), or `\"demo\"` (public demo-memory walkthrough, llms-tour-demo.txt). It defaults to `\"tour\"`, so a request for one of the other three carries the topic. Any other value returns an error listing these four."
- Removed
run_aiakiv_app_action
2 tool updates
- Added
create_aiakiv_card - Removed
find_related_memories
1 tool update
- Changed
find_related_memories4 fields changed- changed
Input schema / properties / candidate_ids / descriptionPrevious value: -"Candidate ids a preceding search response announced. Unannounced ids are treated as plain seeds."New value: +"Ignored." - changed
Input schema / properties / count / descriptionPrevious value: -"Max leads (1-5)."New value: +"Ignored." - changed
Input schema / properties / query / descriptionPrevious value: -"One self-contained sentence."New value: +"Ignored." - changed
Input schema / properties / seed_ids / descriptionPrevious value: -"Events to expand from, normally the top search hits. Omitted, it seeds itself and works standalone. Specific seeds give specific leads, while a seed hanging off an entity that appears everywhere buries its neighbours in noise."New value: +"Ignored."
21 tool updates
- First observed
describe_memory_schema - First observed
find_memories_by_entity - First observed
find_memory_connections - First observed
find_partner_memory_connections - First observed
find_related_memories - First observed
get_aiakiv_memory_guide - First observed
get_memory_content - First observed
get_partner_memory_content - First observed
get_save_target - First observed
hide_memory - First observed
list_memory_projects - First observed
list_memory_timeline - First observed
list_partner_links - First observed
query_memories_with_sql - First observed
query_memory_graph - First observed
query_partner_memory_graph - First observed
run_aiakiv_app_action - First observed
save_memory - First observed
search_memory - First observed
search_partner_memory - First observed
update_memory
Related MCP Connectors
Long-term memory and a knowledge graph for AI agents: recall, notes, secrets and data sources.
Persistent memory and knowledge graphs for AI agents. Hybrid search, context checkpoints, and more.
Persistent memory for AI agents: save, search and connect context across tools and sessions.
11Persistent long-term memory for AI agents: semantic search, knowledge graph, and task canvas.
Related MCP Servers
AlicenseAqualityDmaintenanceProvides persistent long-term memory for AI agents through semantic search and automated knowledge graph extraction. It enables agents to store, recall, and reason over facts, preferences, and relationships across multiple conversations and sessions.1415 npmMIT- AlicenseNot gradedqualityBmaintenanceEnables persistent, graph-based memory for AI agents, allowing them to store, traverse, and recall relationships between facts, decisions, and context across sessions for efficient reasoning and reduced token usage.MIT
- AlicenseNot gradedqualityDmaintenanceProvides persistent knowledge graph memory for AI agents, enabling them to store, recall, and query facts about people, projects, and relationships across sessions.MIT
- FlicenseNot gradedqualityDmaintenanceA knowledge-graph-based memory system for AI agents that enables persistent information storage between conversations.6-
Glama MCP Gateway
Add one secure layer between your agents and this server.