"Automating Page and Interface Testing" matching MCP servers:

A TypeScript-based MCP server that enables users to query financial news, stock data, and index information while managing text notes with creation and summarization capabilities.

Enables synchronization and management of FoundryVTT journal entries within a Notion Story Bible, including media export and conflict resolution tools. It provides a Model Context Protocol interface for LLMs to preview, apply, and monitor data mirroring between tabletop RPG platforms and digital databases.

Enables AI agents to store and retrieve project context, bugs, decisions, and session logs by reading and appending markdown files in a local Obsidian vault, without requiring any cloud services.

Enables local MCP clients to list, read, write, and search notes in an Obsidian vault via an HTTP server running inside Obsidian.

Provides AI clients with per-project todo management and persistent context notes via MCP, enabling task tracking and resume summaries.

Enables AI agents and users to manage workspace files, monitor system metrics, take persistent notes, and retrieve weather data via MCP tools and resources.

Provides an in-memory notebook interface with tools to create, retrieve, list, update, and delete notes, designed to test agent behavior through realistic MCP tool interactions.

Enables MCP clients to search and read notes from an Obsidian or markdown vault through four governed tools, with enforced read-only access, a page budget, and path sandboxing.

Enables Windows users to search and retrieve Outlook calendar appointments, tasks, and mail, as well as local/OneDrive files via Windows Search and OneNote pages, with additional OneNote page creation and update capabilities, all through MCP over stdio.

Exposes a Notion-synced AI OS as read-only MCP tools, enabling MCP-compatible AI clients to search the vault, fetch page contents, list projects, and check project statuses without scraping public links.

Exposes meeting transcripts to any MCP-capable AI client so it can list meetings, page through a single transcript, and search across all of them for a topic with exact timestamps. Speaker labels, emails, phone numbers, and paths are pseudonymized or redacted before anything crosses the protocol, and transcripts are read-only.

Enables AI assistants to interact with Joplin notes, notebooks, and tags through a standardized MCP interface, supporting CRUD operations, search, and organization.

Enables AI clients to inspect, read, and propose page edits in Planist workspaces over MCP. Supports listing pages, fetching structured content, and submitting edit proposals for review.

Provides fast, read-only access to Karpathy-style Markdown wikis through MCP, with search, page retrieval, and orientation tools. Supports local stdio and remote Streamable HTTP deployments backed by Git, including automatic webhook synchronization.

Enables AI assistants to interact with Roam Research graphs through comprehensive API access, supporting page/block operations, markdown import, search, memory storage, and complex batch actions for managing knowledge graphs.

Enables MCP clients to search, read, write, and organize pages, spaces, comments, attachments, labels, and member access in self-hosted Docmost Community Edition wikis via its internal HTTP API, using Markdown for page and comment bodies.

A standalone Model Context Protocol server for Microsoft OneNote desktop, connecting via the Windows COM API through a PowerShell bridge to enable page CRUD, search, export, and organization tools without an API key.

A local workspace whose accessible pages and MCP tools are generated from the same definitions, so AI agents can do everything a person can: create, update and find notes, tasks and projects, build and arrange pages, and read any page back as a screen reader gets it.

Full-featured Notion MCP server enabling deep page reading, block editing, snapshot/restore, file uploads, table manipulation, page restore, and destructive page copying.

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.