"Official Notion MCP Server Information" matching MCP servers:

Enables interaction with Notion databases through the Notion API, supporting full CRUD operations on pages and databases. Supports advanced querying, filtering, sorting, and all property types with Docker deployment for easy integration with Cursor and Claude.

A Model Context Protocol server that provides a standardized interface for interacting with Notion's API, enabling users to list databases, create pages, and search across their Notion workspace.

Enables Claude and other MCP clients to list and query allowlisted Supabase tables, insert rows, and search, read, or create Notion pages. It ships with table allowlists, validated inputs, row limits, and an optional read-only mode that unregisters write tools, plus a mock mode for trying it without credentials.

A Model Context Protocol server that enables Claude and other LLMs to interact with Notion workspaces, providing capabilities like searching, retrieving, creating and updating pages, as well as managing databases.

Enables AI assistants to save and manage question-and-answer pairs within a structured Notion database. It provides tools for database setup, entry creation, and querying existing conversation history.

Gives MCP clients like Claude, Cursor and Codex read/write access to Notion through a single token, letting agents search, create and edit pages, query databases, comment and upload files in plain language. It uses only three lightweight tools, supports batched idempotent writes, and runs headless in CI or self-hosted environments.

Provides tools for querying and updating Notion database rows by exact property filters, avoiding semantic search for reliable row selection.

Enables secure natural language querying of Notion CRM databases, allowing AI agents to retrieve client health, ARR, and deployment roadblocks through a custom MCP middleware.

A Cloudflare Workers-based service that enables intelligent searching, automatic code snippet recording, and statistical analysis of programming knowledge stored in Notion databases.

Connects MCP-capable AI clients such as Claude, Cursor, VS Code and Codex to Notion with a single token, letting them search, create and edit pages, query databases, comment and upload files in plain language. It supports headless and CI use, batched idempotent writes, markdown round-tripping, and low context overhead.

Provides structured, SQL-style query access to Notion databases, allowing Claude to filter, sort, and update pages through the Notion REST API. It enables advanced property-based filtering and database schema discovery beyond the capabilities of standard connectors.

Retrieves comprehensive patient information including personal details, insurance plans, and employee data through the get_patient tool. Supports Docker Compose deployment and integration with Watson Orchestrate for healthcare data access.

A Model Context Protocol server that connects Claude and other AI assistants to your Notion workspace, allowing AIs to interact with databases, pages, and blocks.

It enables AI assistants to execute SQL and explore databases, retrieve schemas, metrics, and overviews, and generate Plotly charts directly from query results.

Enables AI assistants to execute SQL, explore database schemas and sample data, inspect system metrics, and generate Plotly charts from query results.

It bridges AI assistants and StarRocks databases, enabling direct SQL execution, database/schema exploration, system metric access, detailed table/database overviews, and Plotly chart generation without complex client-side setup.

A sovereign, high-speed, local-first Big Data Ingestion, Filtering, and Analytical Pipeline Orchestrator.

Provides secure live database querying, schema inspection, AWS S3 security audits, and Cloudflare infrastructure control through MCP tools.

Enables LLM agents to read and modify company data from Notion and Supabase, with human-in-the-loop approval for all write and delete operations.

Official SQAI MCP server: governed structured data access powered by Mojo kernels. 3 stdio tools: listSources (discovery), queryData (deterministic read-only queries + compute with provenance), explainQuery (dry-run validation). Introspection needs no credentials; execution requires a one-time free sqai login. npm: @thyn-ai/sqai-mcp. Source: packages/mcp. Registry: io.github.thyn-ai/sqai.

Read-only MCP server that exposes your local Notion backups to AI agents — query databases, read pages, search a backed-up workspace. Offline by default: no LLM calls, no telemetry, no cloud.

A read-only MCP server that lets AI search and read both sides of a user's own LINE Desktop chat history on macOS using local database snapshots, without needing a LINE Official Account or altering unread state.

Enables MCP clients to search and describe API routes, retrieve people, admissions, academics, and billing records, download exports, and optionally make changes against a school information system, read-only by default.

Local MCP server for validating and querying Peruvian RUCs using SUNAT's official reduced registry, stored locally to keep data private.

An MCP server for interacting with Treasure Data API, allowing users to retrieve database information and check server status through natural language queries.

Official BoltPatternHQ MCP Server for instant automotive wheel fitment, PCD, center bore, and offset reference data.

Enables AI assistants to query a garage workshop database for live information on open jobs, vehicle history, parts availability, and bookings, and to append notes to job cards.

Enables querying package ecosystem data from ecosyste.ms, including package metadata, versions, security advisories, dependencies, and repository information across 40+ package registries with fast local SQLite lookups and API fallback.

MISP (Malware Information Sharing Platform) MCP server with built-in prompt injection defense via prompt-defense-audit

The official Model Context Protocol (MCP) server for SeaTable, built and maintained by SeaTable GmbH. It lets AI agents interact with data in your bases — reading, writing, searching, linking, and querying rows through a focused set of tools. The server intentionally focuses on data operations, not schema management (creating/deleting tables or columns), keeping the tool set lean and safe for auto