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

An MCP server for managing contextual data as markdown files with metadata, enabling agents to save, retrieve, search, and delete contexts using simple CRUD operations.

Unofficial Notion MCP server built on Notion's private API (token_v2 cookie). Gives LLM agents full read/write access to the entire workspace — no integration token and no per-page sharing.

A TypeScript-based MCP server that implements a simple notes system, providing resources for accessing notes via URIs, tools for creating notes, and prompts for generating summaries.

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 advanced todo list management and content organization using Notion's API, supporting features like creating databases, dynamic filtering, and collaborative task tracking.

Enables AI agents to read, create, update and delete any file in a mounted folder of markdown notes, patch individual headings, blocks or frontmatter keys, search by text or JsonLogic queries over frontmatter, tags and links, and stream note changes as events. Runs as a standalone container requiring no Obsidian installation and binds only to private networks such as Tailscale or WireGuard.

Built-in MCP server that gives AI agents direct access to an Obsidian vault for reading, writing, searching notes, and executing commands.

AI assistant integration with Logseq knowledge graph: 21 tools to read, write, query, and search notes, enabling seamless interaction with your notes.

A multi-agent system that analyzes meeting transcripts to generate summaries, extract key points, and identify actionable tasks through an easy-to-use web interface.

Enables AI clients to read, write, search, and manage files in an Obsidian vault via MCP over SSE, running standalone without the Obsidian desktop app.

A bridge server that allows LLM tools to interact with an Obsidian vault through a local REST API, enabling file operations, note management, and metadata access through natural language.

Enables natural language interaction with a personal knowledge base stored locally on your computer, supporting semantic search, note reading, and writing through Claude Code or mobile apps.

Self-hosted MCP server that lets AI agents and MCP clients read and modify Milanote content — boards, notes, links, to-do lists with due dates, columns, labels, comments, sharing, trash and export — through the session of your own signed-in Google Chrome. Works over stdio or HTTP and speaks the same tool set as the accompanying REST API and Python client.

Provides persistent local memory of Claude Code sessions with TODO management and searchable activity logs via MCP tools.

Enables coding agents to use an Obsidian vault as long-term memory, with search, reading, and writing of notes, plus automatic capture of learnings that are propagated to MOCs, daily notes, and the knowledge index with git commits.

Enables natural-language semantic search over your own local files through an MCP server, fully offline without API keys or a server daemon, with optional LLM-grounded answers and exact file:line sources.

Reads the local SQLite cache of the Notion desktop app to enable fast, offline search and retrieval of Notion pages from Claude.

An MCP server that gives Claude direct access to your reMarkable tablet's notebooks, enabling document search, PDF rendering, handwriting transcription, and diagram conversion, all locally without API keys.

A lightweight Notion MCP server that minimizes token usage by returning Markdown instead of raw JSON, enabling efficient read/write operations on Notion pages.

An MCP server that lets Claude Code recall the context of past conversations from any project on demand.