The breadth is the point: a request that touches the calendar, a task and an email can be handled without three separate servers. Which parts light up depends entirely on the credentials you supply, so treat the .env file as the real configuration surface.
A Python MCP server that gives an MCP client a personal-assistant toolset spanning calendar, tasks, email, web search, weather, news and smart-home devices.
- Calendar events retrieved and new events created
- Tasks listed with status filtering, added, and moved to a new status
- Email listed, a single message read, and mail sent
- Web search, plus weather and news lookups
- Smart-home devices listed, their state read, and control commands sent
Python 3.10 or higher — the MCP SDK will not run on earlier versions — with a current MCP SDK. Credentials for the services you want go in a .env file copied from .env.example, so which tools work depends on which of those you fill in.
