TimeTree MCP
UnclaimedUnofficial TimeTree MCP server for Claude, Codex, Cursor, and other MCP clients — read and manage calendars, events, memos, comments, labels, and members.
Set up this server
More in AI & ML
Browse the full directoryUnclaimed listing
Is this your MCP server?
This listing was auto-indexed from the public record. Claim it to edit the page, set compatibility and unlock growth tools. Takes under two minutes.
Claim this serverSecurity profile
Claimed and verified servers get a weekly static scan that shows what the code can reach: external services, environment variables, shell commands, agent configuration folders, plus any dependencies with known advisories. Claim this listing to get one. How the security profile works
6 of 6 tools
Documented tools (6)
From project documentation. A server handshake does not verify each tool’s description or behavior.
create_event
Create a new event in a calendar (supports alerts, recurrences, attendees, checklist)
delete_event
Delete an event from a calendar
get_events
Get events from a calendar with auto-pagination
get_updated_events
Get events updated after a specific timestamp (efficient incremental sync)
list_calendars
List all calendars with participating users
update_event
Update an existing event
Tool change history
FAQ
Questions about TimeTree MCP Server
- How do I connect TimeTree MCP Server to Claude?
- The project does not publish a launch command that MCPVault could verify. Open the repository linked on this page for its install steps; the listing names Claude Desktop, Claude Code, Cursor as compatible clients.
- Is TimeTree MCP Server free?
- The listed licence is MIT. Check the upstream terms for permitted use and commercial requirements; a public repository does not by itself mean the software is free or open source. Connected APIs and hosted services may have separate charges.
- What can TimeTree MCP Server do?
- TimeTree MCP Server documents 6 tools to the agent, including create_event, delete_event, get_events. The descriptions above come from project documentation. A live handshake does not test individual tool behavior.