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_healthA | Check the configured Glyph Hold service health and version. |
| list_categoriesA | List available Glyph Hold memory categories. |
| search_memoriesB | Search Glyph Hold memories with deterministic SQLite FTS. |
| prefetch_memoriesB | Ask Glyph Hold for conservative memory context relevant to a message. |
| create_memoryB | Create a Glyph Hold memory after confirming it should be stored durably. confidence must be 1-5. auto_prefetch_level must be one of never, low, normal, high, or pinned. |
| create_secretC | Create encrypted Glyph Hold secret metadata and value. |
| reveal_secretC | Reveal a secret value only when the user explicitly asks for the value. |
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 7 tools
Each tool targets a distinct concept: memory vs secret, different retrieval methods (prefetch vs search), health check, categories. No overlap confuses selection.
All tools follow snake_case verb_noun pattern (create_memory, create_secret, list_categories, etc.) with consistent naming conventions.
7 tools cover the core functionalities of memory and secret management without bloat, appropriate for the server's purpose.
Missing update/delete operations for both memories and secrets, and no explicit list or get tool for single memories or secrets. Gaps may impede full lifecycle management.