Glyph Hold MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| GLYPHHOLD_URL | Yes | The URL of the Glyph Hold instance. | |
| GLYPHHOLD_API_KEY | Yes | The API key for authentication. | |
| GLYPHHOLD_CA_BUNDLE | No | Path to a custom CA bundle for TLS. | |
| GLYPHHOLD_VERIFY_SSL | No | Set to false to disable SSL verification (not recommended for production). |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| glyphhold_healthC | Check service health. |
| glyphhold_capabilitiesC | Discover permitted spaces, defaults and GH2 features. |
| list_categoriesA | List categories; these classify records and do not grant access. |
| list_memoriesC | List permitted records with versions and ownership. |
| get_memoryC | Read a record and its current version. |
| search_memoriesB | Search active space; try shorter terms or synonyms when needed. Explicitly broaden across permitted spaces for other contexts; this does not change writes. |
| prefetch_memoriesC | Recall bounded active and General context. Check entity and space: even nonempty recall may be insufficient. Search explicitly when needed and get full records by ID when excerpts omit required evidence. |
| create_memoryC | Save a durable memory after search. Reuse the idempotency key for retries. |
| update_memoryC | Update using the last-read version; reread and reconcile after conflicts. |
| archive_memoryB | Archive a memory reversibly with concurrency protection. |
| move_memoryC | Explicitly move ownership; requires write grants in both spaces. |
| list_memory_revisionsD | Inspect permitted historical snapshots. |
| restore_memory_revisionC | Restore a permitted revision while checking concurrent edits. |
| get_memory_contextC | Read active context and confirmed placement guidance for one conversation. |
| set_memory_contextB | Change one conversation's active space without changing connection default. |
| get_placement_guidanceC | Read owner-confirmed guidance for placing new memories. |
| search_secretsB | Search global secret metadata by name, folder, saved website address or hostname. provider_name=builtin allows local-only access during a vault outage. No values are returned. |
| get_secret_metadataC | Inspect one secret without revealing its value. |
| create_secretA | Create in the active provider after searching for duplicates. Secrets are global. Optional folder_id selects a vault folder; empty string means unfiled, omission uses the default. space_id is deprecated. |
| reveal_secretB | Explicitly reveal one field for an authorised task. Use metadata fields to select username, password, SSH key, notes or custom fields. |
| list_secret_foldersB | List optional vault folders. Built-in storage returns supported=false. |
| create_secret_folderA | Create a vault folder after checking existing folders. Requires external writes. |
| update_secretA | Update one explicitly selected secret field using its current metadata version. Never overwrite a conflicting value without authorisation. |
| migrate_secretA | Transfer a built-in secret directly to the vault without exposing its value. Search first: pass an existing target_id and field to verify identical values, or omit target_id to create only if the name is unused. Different values require user review; neither is overwritten. Use dry_run=true to preview without changes. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
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.