"database" matching MCP servers:

MCP Server for OceanBase database and its tools

An implementation for managing Neo4j graph database operations through the Model Context Protocol, enabling users to execute Cypher queries against their Neo4j database via AI assistants like Cursor and Claude Desktop.

Enables LLMs to orchestrate AI agents and tasks, inspect DAG workflows, monitor cluster metrics, and perform safe database queries and statements through standardized MCP tools.

Enables MCP clients to discover and execute operational tools such as database mutations and system diagnostics over stdio, with deterministic structured outputs and Langfuse observability.

Connect your AI models to your favorite SurrealDB database, and let the LLMs do all your work for you.

Enables stateless human-in-the-loop DevOps automation, demonstrating MCP SEP-2322 multi-round trip requests for emergency database migration authorization.

MCP server that lets multiple coding-agent sessions on the same machine discover each other and collaborate through a shared SQLite database.

A multi-server implementation that uses OpenAI's LLM to orchestrate multiple tool servers providing web search, weather lookup, random facts, and PostgreSQL database querying capabilities.

Provides a self-hosted shared work queue for AI agents via MCP, using a local SQLite database for task management.

A Meta-MCP Server that acts as a tool discovery service, helping AI assistants find appropriate MCP servers from a database of 800+ servers when they need capabilities that aren't currently available.

Self-hostable MCP server for portable AI agent playbooks: manage skills, MCP configurations, personas, instructions, memory, and canvas documents. The public Next.js source implements Streamable HTTP MCP at /api/mcp/manage; users can run it with the repository's Dockerfile and their own database configuration.

Enables multiple AI coding-agent sessions on one machine to hand tasks to each other and get results back through a shared local folder of JSON messages, with no cloud, database, or network service. Supports direct messages, broadcasts, blocking receive, and an optional headless worker that picks up, runs, and auto-replies to tasks.

An MCP server that lets AI agents register a name and bio, discover one another, exchange messages, and be woken when mail arrives rather than polling, backed by a shared SQLite database over stdio for one machine or HTTP for a team.

It gives AI agents a ranked, token-budgeted digest of what changed since their last cursor, with drill-down handles and cursor acknowledgement, read from a local database of file and SQL source changes. It enables agents to act on current business state without re-reading and diffing everything themselves.

Enables agents to report and query performance metrics to build a community-driven quality database for MCP tools. This server helps agents discover and select the most reliable tools based on success rates and user-reported quality scores.

A universal interface that enables AI Agents to communicate with Hologres databases, allowing them to retrieve database metadata and execute SQL operations.

An MCP server that enables concurrently-running Claude Code sessions to cross-talk via channels, DMs, and leader coordination, all backed by a shared beads database.

A Model Context Protocol server providing vector database capabilities through Chroma, enabling semantic document search, metadata filtering, and document management with persistent storage.

A Model Context Protocol server that allows AI agents to execute SQL queries against a MySQL database, supporting operations like reading data, creating tables, inserting, updating, and deleting records.

Enables agents to crawl and read websites politely, learning per host which reader, URL rewrite, or detail path actually reaches good information, and reusing those wins across runs or a shared database. Failures come back as coded errors with concrete next steps, so blocked or empty pages point to an honest alternative instead of endless retries.