Glyph Hold MCP
Related Servers
Alternatives to Glyph Hold MCP
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceMCP server that lets MCP clients inspect, create, update, and deploy ChatGPT Sites through a local Codex installation.1MIT
- AlicenseAqualityCmaintenanceA tiny MCP server that wraps Perseus Vault to provide persistent, encrypted, local-first memory for OpenAI Codex agents, enabling them to remember project conventions, decisions, and context across sessions.5MIT
- AlicenseNot gradedqualityCmaintenanceA powerful MCP server for making HTTP requests, GraphQL queries, and TCP/Telnet connections from AI assistants.7MIT
- AlicenseBqualityCmaintenanceAn MCP server that provides LLMs access to other LLMs412 npm81MIT
- AlicenseNot gradedqualityDmaintenanceMCP server that wraps the nexus CLI, giving AI agents cross-session memory, semantic search, preference learning, and smart context injection.231 npmMIT
- AlicenseAqualityCmaintenanceBridges OpenAI Codex CLI to any MCP client, allowing headless Codex sessions via tools like codex and codex-reply.211 npm1MIT
TDQS
Scored across 24 tools
Most tools target clearly distinct resources or lifecycle actions, with secrets, memories, context, health, and capabilities separated well. The main ambiguity is among the memory retrieval tools: list_memories, search_memories, and prefetch_memories overlap conceptually and require careful reading of their descriptions to choose correctly.
The surface predominantly follows a snake_case verb_noun convention, such as create_memory, update_secret, and list_memory_revisions. The main deviations are glyphhold_health and glyphhold_capabilities, which use a server-name prefix and noun-style names rather than the dominant pattern.
At 24 tools, the surface is heavy for a single MCP server and sits in the borderline range where tool selection becomes more demanding. The tools appear purposeful across the secret and memory domains, but the count is large enough to create cognitive load and increase misselection risk.
The tool set provides broad lifecycle coverage for memories, including create, read, search, update, archive, move, revisions, context, and placement guidance. Secrets are also well covered, but there is no delete_secret or delete_secret_folder operation, leaving minor lifecycle gaps that may require workarounds.