"Examples of MCPs (Microservices Communication Protocols) That Do Not Require API Keys" matching MCP servers:

Renders a YAML CV into a one-page PDF via notboringresume.cloud, optionally generating a cover letter adapted to the resume and job offer.

Local macOS MCP servers for Mail, Calendar, Reminders, Notes, Contacts, Messages, Shortcuts, Files, Maps, and system tools. The unified Apple Tools server and individual app servers run over stdio with native macOS permissions; this is an MIT-licensed community project, unaffiliated with Apple.

Enables managing Microsoft To Do lists and tasks through MCP, including creating, updating, completing, deleting, searching, and checklist operations via Microsoft Graph.

Open-source MCP server that connects AI assistants to Fizzy (Basecamp's task management) with 70+ tools for boards, cards, workflows, and AI-powered project management.

Enables AI clients like Claude to read and manage Microsoft To Do task lists and tasks via the Microsoft Graph API, running locally over stdio with secure token storage.

Runs 20 slash-command workflows across Google Calendar, Gmail, Linear, Slack, Granola, Google Docs, GitHub, Stripe, Notion, Google Forms, Sheets and Drive to produce morning briefs, meeting prep, action items assigned to owners and weekly updates. Reads proceed without asking, while anything that creates, sends, changes or deletes is shown for approval first.

Enables to manage to-do items through natural language, with tools for creating, reading, updating, and deleting tasks.

An MCP server that generates MCP servers. Give it an API definition - OpenAPI 3.0/3.1 or a Postman collection or extend an existing server - and it scaffolds a complete, runnable, ownable TypeScript or Python MCP server for that collection of APIs.

TO DO microsoft

MCP server for Microsoft Forms automation, enabling AI agents to inspect forms, resolve branching, validate and submit answers, upload files, and manage response links.

MCP server for Todoist API integration, allowing management of tasks, projects, sections, labels, and comments through natural language.

A Model Context Protocol (MCP) server that enables AI assistants like Claude and Cursor to interact with Microsoft To Do via the Microsoft Graph API.

Enables AI agents to read conversations, send messages, and manage members in Microsoft Teams via the Teams Chat Service REST API.

Enables AI assistants to manage Tempo timesheets and perform write operations such as create, update, delete, submit, approve, reject, reopen, and recall, with user confirmation safeguards.

MCP server for Microsoft To Do via Microsoft Graph. MSAL device code flow, no client secret needed.

Enables AI clients to create and manage tasks via a local REST API by converting natural language into HTTP requests through the Model Context Protocol.

Lets Claude and other AI clients read and modify Microsoft To Do through natural language, adding, completing, searching, updating, and deleting tasks and sub-steps by title and list name instead of ids. Personal Microsoft accounts need no Azure app registration — a single device-code sign-in grants access, with optional read-only and no-delete modes available.

Enables users to manage a personal to-do list backed by SQLite, adding single or multiple tasks, listing incomplete tasks, renaming or updating task status, and marking tasks complete. All state persists in a local database created automatically on first run.

Enables OAuth-capable MCP clients to connect to personal Microsoft To Do accounts and read lists, create or update tasks, manage checklist items, set due dates, and complete tasks.

Enables coding agents to manage Microsoft To Do lists and tasks through Microsoft Graph, with optional support for checklist items, linked resources, attachments, and delta synchronization.