Personal Workspace MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| TASK_DB_PATH | Yes | Absolute path to the SQLite task database. | |
| QUERY_DB_PATH | No | Absolute path to a separate SQLite database to query. Optional. | |
| QUERY_ALLOWED_TABLES | No | Comma-separated allowlist of tables to expose from the query database. Required when QUERY_DB_PATH is set. |
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 |
|---|---|
| create_taskC | Create a task. due_date is an optional YYYY-MM-DD calendar date. |
| list_tasksC | Filter tasks with pagination. Search matches title or description. |
| get_taskB | Read one task, including its version for optimistic updates. |
| update_taskC | Update supplied fields using the current version. clear_due_date removes a deadline. |
| archive_taskB | Archive a task without deleting its data or history. |
| restore_taskC | Restore an archived task. |
| task_historyA | Read up to 100 recent audit events for a task. |
| database_schemaA | Describe the configured allowlisted SQLite tables before composing SQL. |
| query_databaseA | Execute one read-only SELECT query. Use ? placeholders and parameters for values. |
| search_locationsB | Find weather locations. Return candidates; clarify ambiguous place names. |
| weather_forecastB | Retrieve current modeled weather and daily forecasts from Open-Meteo. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| plan_day | Guide an agent to plan a day from task deadlines and optional weather. |
| analyze_database | Guide schema inspection, read-only SQL and evidence-based answers. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| schema_resource | Allowed tables and columns for natural-language-to-SQL workflows. |
| overview | Read task counts by status without mutating anything. |
TDQS
Scored across 11 tools
Every tool targets a distinct resource and action: task CRUD is well-separated from history, database schema is distinct from query execution, and location search is distinct from weather forecast. No two tools could be easily confused.
Most tools follow a clear verb_noun snake_case pattern (get_task, create_task, list_tasks, update_task, archive_task, restore_task, query_database, search_locations). A few tools use noun_noun instead (task_history, database_schema, weather_forecast), which is a minor deviation.
11 tools across three sub-domains (tasks, database, weather) is well-scoped; each tool has a clear, non-redundant role and the count is appropriate for the server's purpose.
Task lifecycle is fully covered (create, read, update, archive, restore, history), database access is complete for read-only queries (schema + SELECT), and weather covers both location search and forecasting.