personal-context
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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": true
} |
| logging | {} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| extensions | {
"io.modelcontextprotocol/ui": {}
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_all_contextA | Get all personal context files at once. Returns a dictionary mapping filename to file contents for all context markdown files (identity, writing-style, opinions, expertise, projects, communication). |
| get_writing_styleA | Get Aaron's writing style context. Returns the full writing-style.md file which describes voice, tone, patterns, vocabulary, and annotated examples of how Aaron writes. This is the most commonly needed context file. |
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 2 tools
The two tools are distinct: one retrieves all context files, the other retrieves a specific file. While get_all_context includes the writing style, the descriptions clarify the appropriate use case for each, so there is little confusion.
Both tool names follow a consistent 'get_' prefix followed by a noun, making them predictable and easy to understand. The naming pattern is uniform.
With only two tools, the set feels thin. The server's purpose is to provide personal context, but it only offers bulk retrieval and a single specific file. This is on the low end of the expected range and may be insufficient for flexible access.
The tools cover retrieval but lack any way to fetch individual context files other than writing style, forcing agents to fetch everything and parse. There is also no update or creation capability, so the surface is incomplete for a context management domain.