MCP Personal Assistant
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MCP_PA_DB_PATH | No | Custom database file path | |
| MCP_PA_DB_TYPE | No | Database type (sqlite or tinydb) | sqlite |
| MCP_PA_DOCS_DIR | No | Directory for document storage | |
| MCP_PA_ENCRYPTION_KEY | No | Encryption key for database (optional) | |
| MCP_PA_MAX_FILE_SIZE_MB | No | Maximum file size in MB | 100 |
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
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_statusA | Get your current status including location, laptop details, and permissions |
| update_statusD | Update your status information |
| create_projectC | Create a new project |
| list_projectsA | List all projects or filter by status |
| get_projectB | Get details of a specific project |
| update_projectC | Update a project's information |
| add_project_taskC | Add a task to a project |
| create_todoC | Create a new todo/reminder |
| list_todosB | List todos, optionally filtered by completion status |
| complete_todoC | Mark a todo as completed |
| create_calendar_eventC | Create a calendar event |
| list_calendar_eventsB | List calendar events within a date range |
| upload_documentC | Upload a document to the personal assistant |
| create_external_documentB | Create a reference to an external document (e.g., cloud storage link) |
| list_documentsC | List all documents, optionally filtered by tags |
| get_documentC | Get details of a specific document |
| get_dashboardA | Get a dashboard view of active projects, upcoming todos, and events |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| Current Status | Your current status and system information |
| All Projects | List of all projects |
| All Todos | List of all todos and reminders |
| Calendar Events | List of all calendar events |
| Documents | List of all documents |
TDQS
Scored across 17 tools
Each tool targets a distinct resource and action. For example, project tools (create, get, update, list) are clearly separated from todo tools (create, complete, list) and calendar tools (create, list). There is no overlap.
All tool names follow a consistent verb_noun pattern in snake_case (e.g., create_project, list_todos, upload_document). The verbs are imperative and the nouns match resource types, making it predictable.
With 17 tools covering projects, todos, calendar, documents, status, and a dashboard, the count is well-scoped for a personal assistant. No tool feels redundant or missing.
The set covers most create, read, and list operations but lacks delete tools for projects, todos, events, and documents. Additionally, todos only have a 'complete' action, not a general update. These gaps could hinder some workflows.