Personal Context MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PERSONAL_INFO_DATA_DIR | No | Directory path where personal information data is stored | ./data |
| PERSONAL_INFO_BACKUP_DIR | No | Directory path where backups are stored | ./backups |
| PERSONAL_INFO_MAX_FILE_SIZE | No | Maximum file size in bytes (default 1MB) | 1048576 |
| PERSONAL_INFO_BACKUP_ENABLED | No | Enable automatic backups before data modifications | true |
| PERSONAL_INFO_ENCRYPTION_KEY | No | Encryption key for AES-256 encryption (optional, used when encryption is enabled) | |
| PERSONAL_INFO_ENCRYPTION_ENABLED | No | Enable AES-256 encryption for sensitive data | false |
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
} |
| resources | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| update_personal_infoD | Update existing personal information |
| list_available_personal_infoC | List all available personal information within current permissions |
| delete_personal_infoD | Delete specific personal information |
| batch_get_personal_infoA | Retrieve multiple categories of personal information in a single request. Retrieve personal information based on category and current permissions, you can get a wide range of information, personal, pets, family, friends, work, etc and even more. You must list once all the categories with the list_available_personal_info tool before using this tool to understand what you can get. |
| batch_save_personal_infoB | Save multiple pieces of personal information in a single request. More efficient than making multiple individual save requests. |
| setup_otpC | Set up One-Time Password (OTP) for encrypted personal data. On MCP App-capable clients, the QR code and backup codes appear in the app panel; otherwise use the structured result. |
| verify_otpA | Verify an OTP token to access encrypted personal data. Required before reading encrypted information. |
| otp_statusB | Check the current OTP configuration status and whether OTP verification is required. |
| disable_otpB | Disable OTP authentication and encryption for personal data. |
| lock_otpA | Immediately lock the current OTP session and block access to encrypted personal data. Requires re-verification with verify_otp to access data again. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| OTP setup | OTP QR code, secret, and backup codes (MCP App) |
TDQS
Scored across 10 tools
Most tools have distinct purposes, but there is some overlap between batch_get_personal_info and list_available_personal_info, as both involve listing or retrieving personal info categories. However, their primary functions (retrieving data vs. listing available categories) are differentiated enough to avoid major confusion. The OTP-related tools (setup_otp, verify_otp, lock_otp, disable_otp, otp_status) are clearly distinct from the personal info management tools.
All tool names follow a consistent snake_case pattern with clear verb_noun structures. Personal info tools use verbs like get, save, delete, update, and list, while OTP tools use verbs like setup, verify, lock, disable, and status. This consistency makes the tool set predictable and easy to understand.
With 10 tools, the count is well-scoped for managing personal information and OTP security. It covers core operations (CRUD for personal data, OTP lifecycle) without being excessive or too sparse. Each tool serves a clear purpose, and there are no redundant or trivial additions.
The tool set provides strong coverage for personal info management (create/retrieve via batch, update, delete, list available) and OTP security (setup, verify, lock, disable, status). A minor gap is the lack of a tool for creating new personal info from scratch (e.g., create_personal_info), as batch_save_personal_info implies updating existing data, but agents can work around this using batch operations. Overall, it supports most workflows effectively.