Ace Memory
Server Details
Persistent memory for AI agents. Semantic search, memory graph, W3C DID identity.
- Status
- Unhealthy
- OAuth
- Works in Glama
- Last Tested
- Transport
- Streamable HTTP
- URL
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections. Dates show when Glama detected each change.
1 tool update
- Changed
agent_load1 field changed- changed
Input schema / properties / query / descriptionPrevious value: -"Agent name to look up (e.g., \"Corbot\", \"code-assistant\")"New value: +"Agent name to look up (e.g., \"Corbot\", \"Data\", \"code-assistant\")"
1 tool update
- Added
agent_load
1 tool update
- Changed
agent_memory_query5 fields changed- added
Input schema / properties / asOfAdded value: +{ + "description": "ISO 8601 timestamp — return memories valid at this point in time. Use for temporal reasoning (\"what did I know on date X?\").", + "type": "string" +} - added
Input schema / properties / expandRelationshipsAdded value: +{ + "default": false, + "description": "Expand initial results via the memory relationship graph. Surfaces connected memories (CAUSED_BY, ELABORATES, RELATED_TO, etc.). Use when context-rich recall matters more than precision.", + "type": "boolean" +} - added
Input schema / properties / includeSupersededAdded value: +{ + "default": false, + "description": "Include memories that have been superseded by newer ones. Default: false (cleaner results, better recall on knowledge-update questions).", + "type": "boolean" +} - added
Input schema / properties / minRelationshipWeightAdded value: +{ + "default": 0.3, + "description": "Minimum edge weight to include during graph traversal. Default: 0.3.", + "maximum": 1, + "minimum": 0, + "type": "number" +} - added
Input schema / properties / relationshipDepthAdded value: +{ + "default": 1, + "description": "Graph traversal depth when expandRelationships is true. 1=direct neighbors, 2=neighbors-of-neighbors. Default: 1.", + "enum": [ + 1, + 2 + ], + "type": "number" +}
4 tool updates
- Added
memory_consolidate - Added
memory_curate - Added
memory_forget - Added
memory_promote
82 tool updates
- First observed
agent_benchmark_history - First observed
agent_benchmark_run - First observed
agent_benchmark_trend - First observed
agent_context_clear - First observed
agent_context_get - First observed
agent_create - First observed
agent_delete - First observed
agent_dream - First observed
agent_dream_config - First observed
agent_dream_history - First observed
agent_facts_contradictions - First observed
agent_facts_create - First observed
agent_facts_list - First observed
agent_facts_search - First observed
agent_facts_update - First observed
agent_get - First observed
agent_handoff_initiate - First observed
agent_handoff_latest - First observed
agent_handoff_resume - First observed
agent_link_verify - First observed
agent_list - First observed
agent_memory_expand - First observed
agent_memory_query - First observed
agent_memory_store - First observed
agent_transfer - First observed
agent_update - First observed
assemble_context - First observed
authorize - First observed
constitution_check_conflicts - First observed
constitution_get - First observed
constitution_get_tier - First observed
constitution_list_proposals - First observed
constitution_propose_change - First observed
constitution_validate_action - First observed
context_budget_apply_preset - First observed
context_budget_get - First observed
context_budget_set - First observed
goal_complete - First observed
goal_create - First observed
goal_find_similar - First observed
goal_get - First observed
goal_get_success_rate - First observed
goal_list - First observed
goal_update_progress - First observed
link - First observed
memory_adapters - First observed
memory_audit - First observed
memory_clean - First observed
memory_export - First observed
memory_import - First observed
memory_ingest - First observed
memory_ingest_batch - First observed
memory_source_approve - First observed
memory_source_list - First observed
memory_source_register - First observed
memory_source_revoke - First observed
memory_sync - First observed
observe - First observed
privacy_check_access - First observed
privacy_create_presentation - First observed
privacy_disclosure_log - First observed
privacy_grant_consent - First observed
privacy_list_grants - First observed
privacy_revoke_consent - First observed
recall - First observed
register - First observed
remember - First observed
session_start - First observed
skill_generate_lessons - First observed
skill_get_effectiveness - First observed
skill_get_ranking - First observed
skill_list - First observed
skill_load - First observed
skill_loader_explain - First observed
skill_loader_recommend - First observed
skill_loader_resolve - First observed
skill_loader_resolve_multi - First observed
skill_recommend - First observed
skill_record_usage - First observed
skill_unload - First observed
trust_status - First observed
whoami
Frequently Asked Questions
Claiming proves that you control a remote MCP connector. It does not move, proxy, or interrupt the server.
Open the connector listing, choose Claim ownership, and sign in to Glama.
Complete one verification method:
GitHub identity — fastest for official registry listings. For a namespace such as
io.github.alice/server, link the matching GitHub user, then choose Claim with GitHub. An organization namespace such asio.github.acme/serveralso needs that organization to have installed the Glama AI GitHub App and approved its permissions, because GitHub discloses organization membership only to apps it has installed. Use HTTP or DNS when it has not.HTTP challenge — works when you can deploy a public file. Generate a token, publish the exact JSON Glama shows at
/.well-known/glama.jsonon the same origin as the connector, then choose Check HTTP challenge.DNS challenge — works when you control DNS but cannot change the server. Generate a token, create the exact TXT record Glama shows, wait for it to propagate, then choose Check DNS challenge.
After verification, Glama sends a confirmation email and gives you access to listing details, thumbnails, health checks, and analytics. Keep the HTTP file or DNS record in place: Glama periodically checks it and ownership remains verified while the token is discoverable.
The HTTP ownership file has this structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"claim": "glama_claim_..."
}Claim tokens are opaque, stable, and bound to the signed-in Glama account. They contain no email address or other personal information. If Glama can no longer discover a verified HTTP or DNS token, it starts a seven-day grace period before removing claim-based access. Restore the same token during that period to keep ownership verified. Never publish an email address, Glama session token, GitHub token, or connector credential as ownership proof.
If verification fails, confirm that you copied the current token exactly. The HTTP file must be public, return valid JSON with a successful HTTP response, and stay on the connector's origin. DNS changes may need more time to propagate. A claim cannot transfer to a different origin or hostname: if the connector target changes, Glama starts the grace period and the new target must be claimed separately after the previous claim is released.
For a connector linked to the official MCP Registry, registry updates continue to replace its name, description, and URL by default. After claiming, open Manage connector and enable Use Glama listing details as the source of truth if edits made on Glama should be preserved. Categories and thumbnails are always managed on Glama; registry linkage and technical connection settings continue to sync.
Control your server's listing on Glama, including description and metadata
Access analytics and receive server usage reports
Get monitoring and health status updates for your server
Feature your server to boost visibility and reach more users
To improve your MCP server's ranking:
Claim ownership of the server listing
Complete the server profile with an accurate description and thumbnail
Provide a test profile so Glama can connect to and evaluate the server
Keep tool definitions clear and complete to earn a high Tool Definition Quality Score (TDQS)
Route real usage through the Glama Gateway; more recorded successful server uses also improve the ranking
For users:
Full audit trail – every tool call is logged with inputs and outputs for compliance and debugging
Granular tool control – enable or disable individual tools per connector to limit what your AI agents can do
Centralized credential management – store and rotate API keys and OAuth tokens in one place
Change alerts – get notified when a connector changes its schema, adds or removes tools, or updates tool definitions, so nothing breaks silently
For server owners:
Proven adoption – public usage metrics on your listing show real-world traction and build trust with prospective users
Tool-level analytics – see which tools are being used most, helping you prioritize development and documentation
Direct user feedback – users can report issues and suggest improvements through the listing, giving you a channel you would not have otherwise
The connector status is unhealthy when Glama is unable to successfully connect to the server. This can happen for several reasons:
The server is experiencing an outage
The URL of the server is wrong
Credentials required to access the server are missing or invalid
If you are the owner of this MCP connector and would like to make modifications to the listing, including providing test credentials for accessing the server, please contact support@glama.ai.
Discussions
No comments yet. Be the first to start the discussion!
Related MCP Connectors
Persistent memory for AI agents. Search and store durable facts, preferences and decisions.
Hosted persistent memory with semantic search, importance and TTL for AI agents.
Persistent memory for AI agents. Search, store, and recall across sessions.
Persistent memory for AI agents. EU-hosted, privacy-first, hybrid recall, contradiction detection.
Related MCP Servers
- AlicenseNot gradedqualityAmaintenanceOpen-source persistent memory infrastructure for AI agents.150321Apache 2.0
- AlicenseNot gradedqualityBmaintenanceProvides durable memory for AI agents with structured storage, semantic search, OAuth authentication, and lifecycle controls.11Apache 2.0
- AlicenseAqualityBmaintenanceGives AI agents private, persistent, semantically searchable long-term memory with RAG, governed multi-agent scopes, and real-time memory-change subscriptions.2322MIT
- AlicenseAqualityAmaintenanceProvides persistent, searchable memory for AI agents, enabling them to retain, recall, and reflect on information across conversations.191MIT
Glama MCP Gateway
Add one secure layer between your agents and this server.
TDQS
The tool set has significant overlap and ambiguity, particularly in memory and context management. For example, 'agent_memory_store', 'remember', and 'observe' all handle memory storage with unclear distinctions, while 'assemble_context' and 'session_start' both assemble context but with different approaches. This overlap makes it difficult for an agent to reliably choose the correct tool without deep domain knowledge.
Most tools follow a consistent verb_noun or noun_verb pattern (e.g., 'agent_create', 'memory_export', 'privacy_check_access'), with clear prefixes like 'agent_', 'memory_', 'skill_' for grouping. However, there are minor deviations such as 'link', 'observe', 'recall', and 'whoami' that break this pattern, slightly reducing overall consistency.
With 82 tools, the count is excessive for a memory management server, leading to bloat and potential confusion. Many tools could be consolidated (e.g., multiple memory storage and context assembly tools) or omitted without losing functionality. This large number overwhelms the core purpose and suggests poor scoping.
The tool set provides comprehensive coverage for agent memory management, including creation, updating, deletion, benchmarking, dreaming, privacy, skills, and context assembly. It supports full CRUD operations across agents, memories, goals, and other entities, with no apparent gaps in the domain's lifecycle or workflows.