mstodo-bridge
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| HOST | No | Host interface to bind the HTTP server to, e.g., 0.0.0.0 for remote access. | |
| PORT | No | Port for HTTP mode. Defaults to 46377. | |
| HTTPS_PROXY | No | Standard HTTPS proxy environment variable, used as an alternative to TASKBRIDGE_PROXY for HTTPS traffic. | |
| ADMIN_PASSWORD | No | Admin password for the web management console. If not set, a password is automatically generated. | |
| PUBLIC_BASE_URL | No | Public base URL for the server, used for authentication callback display and redirects. | |
| TASKBRIDGE_PROXY | No | Outbound HTTP/HTTPS proxy for server requests. | |
| TASKBRIDGE_CONFIG_DIR | No | Directory where credentials are stored. Defaults to ~/.mstodo-bridge. | |
| TASKBRIDGE_MS_CLIENT_ID | No | Overrides the built-in OAuth client ID for Microsoft authentication. |
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
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| logoutA | Disconnect Microsoft To Do: deletes the locally stored tokens (and any pending login). The Microsoft-side app consent is NOT revoked; to fully revoke, remove the app at account.microsoft.com > Privacy. |
| login_statusA | Check whether Microsoft To Do is connected. Use before task tools; if not connected, call login. |
| loginA | Connect Microsoft To Do. Call WITHOUT arguments to start: it returns an authorize URL for the user to open and consent, plus a ready-to-relay message covering the paste-back fallback. When the user later sends you a localhost callback URL from their address bar, call login AGAIN passing it as callbackUrl to finish. |
| list_providersA | Show the Microsoft To Do provider and its auth state and capabilities. Run this first to learn what is available. |
| list_task_listsA | List the task lists (folders) of a provider. |
| create_task_listC | Create a new task list (folder). |
| delete_task_listA | Delete an entire task list and its tasks. Irreversible. |
| list_tasksA | List tasks. Give listId for one list; omit it to page across every list of the provider. |
| search_tasksA | Search open tasks by substring across every list of every connected provider. |
| get_taskC | Fetch one task by list and task id. |
| create_taskB | Create a task. dueDate accepts ISO date (2026-08-25) or RFC 3339 datetime. parentTaskId nests it as a subtask where supported. |
| update_taskA | Update a task (partial). Set status "completed" or "needsAction", change title/notes, or set dueDate (null removes it). |
| complete_taskC | Mark a task completed. |
| delete_taskB | Delete a task permanently. |
| move_task_between_listsA | Recreate an existing task in another list and delete it from the source list (Graph To Do has no native move). Use to reorganize. |
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 15 tools
Most tools target distinct resources and actions, but there are overlapping boundaries: update_task can mark a task completed, making complete_task redundant, and login_status overlaps with list_providers for checking auth state. Descriptions help clarify intended use, but an agent could still struggle to choose between these pairs.
Task and list tools consistently follow a verb_noun pattern: list_tasks, create_task, delete_task_list, move_task_between_lists. The auth tools (login, login_status, logout) deviate from that pattern, but they form their own predictable auth-related group, so the overall naming is mostly consistent.
Fifteen tools is on the upper end of the ideal range but is reasonable for a Microsoft To Do bridge covering auth, providers, task lists, and individual tasks. A few tools like complete_task and list_providers feel somewhat redundant, suggesting the count could be trimmed slightly, but it is not excessive.
The server covers the core lifecycle well: list, create, get, update, complete, delete, search, and move tasks, plus list and auth management. Minor gaps exist, such as no way to rename a task list and no dedicated get_task_list operation, but agents can work around these with the available tools.