MCP Microsoft Todo vs Time — MCP Server Comparison | AllMCPs
Side-by-Side Model Context Protocol Comparison
MCP Microsoft Todo vs Time
In-depth architectural comparison of the MCP Microsoft Todo and Time MCP servers. Compare execution transports, security boundaries, tool capabilities, quality scores, and ready-to-paste client installation snippets for Claude, Cursor, Windsurf, and VS Code.
At a Glance & Executive Verdict
MCP Microsoft Todo
Other Tools and Integrations · Local stdio
Quality: 61/100 (Good) | Auth: OAuth 2.0
Time
Other Tools and Integrations · Local stdio
Quality: 88/100 (Excellent) | Auth: No auth required
Verdict Summary: Choose MCP Microsoft Todo if you need specialized Other Tools and Integrations tools running via a local process. Choose Time if your workspace requires Other Tools and Integrations integration with local subprocess execution. Both servers can be configured concurrently in your client's mcpServers manifest.
Which MCP Server Should You Choose?
Choose MCP Microsoft Todo when:
You need dedicated capabilities in the Other Tools and Integrations domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: OAuth 2.0 (Free / Open Source).
Microsoft To Do task management via Microsoft Graph API. MSAL device code flow (no client secret needed), persisted token cache, full MCP safety annotations.
Time and timezone conversion capabilities.
Category & Scope
Tools & Capabilities Breakdown
MCP Microsoft Todo Tools (28)
list_task_lists
List all the user's To Do lists (Tasks, Inbox, custom lists, etc.).
list_tasks
List the tasks of a To Do list. Supports OData filter, $orderby, $top, and pagination.
get_task
Fetch a task's detail by ID.
create_task
Create a new task in a To Do list. Supports recurrence and reminder.
update_task
Update an existing task (title, status, recurrence, reminder, etc.).
complete_task
Shortcut to mark a task as completed.
Ready-to-Paste Client Configurations
Paste either (or both) of these JSON server blocks into your client config file (e.g. claude_desktop_config.json or ~/.cursor/mcp.json).
MCP Microsoft Todo is categorized under Other Tools and Integrations and uses a local stdio subprocess. In contrast, Time belongs to Other Tools and Integrations using local stdio subprocess. Select MCP Microsoft Todo when you need capabilities focused on other tools and integrations and Time when you require tools for other tools and integrations.
Move a task from one list to another. Recreates the task in the target list (title, body, due, recurrence, reminder, categories preserved) then deletes the original. Note: checklistItems and linkedResources are NOT moved (Graph limitation). The task ID changes.
search_tasks
Search a term in the titles of tasks across ALL lists (case-sensitive). By default excludes completed tasks.
summarize_today
Summary of tasks due today and overdue, aggregated per list. Useful for the question "what do I have to do today?".
list_all_tasks
Fetch every active task across every list in a single round-trip (uses Graph $batch internally). Use this for the question "what are all my tasks?" instead of N×list_tasks calls. Optional `filter` is an OData filter applied per list (e.g. "importance eq 'high'"). By default `status ne 'completed'` is appended unless `include_completed` is true.
list_checklist_items
List the sub-items (checklist) of a task.
+16 more tools listed on main page
Time Tools (9)
create_entities
Create multiple new entities in the knowledge graph
create_relations
Create multiple new relations between entities in the knowledge graph. Relations should be in active voice
add_observations
Add new observations to existing entities in the knowledge graph
delete_entities
Delete multiple entities and their associated relations from the knowledge graph
delete_observations
Delete specific observations from entities in the knowledge graph
delete_relations
Delete multiple relations from the knowledge graph
read_graph
Read the entire knowledge graph
search_nodes
Search for nodes in the knowledge graph based on a query
open_nodes
Open specific nodes in the knowledge graph by their names