MCP Database Server

Created By
manpreet2000a year ago
mcp server for all types of database that connects with LLMs
Overview

what is MCP Database Server?

MCP Database Server is a Model Context Protocol (MCP) server that enables Large Language Models (LLMs) to interact with various databases using natural language queries. Currently, it supports MongoDB and plans to extend support to other databases like PostgreSQL, CockroachDB, and Redis.

how to use MCP Database Server?

To use the MCP Database Server, clone the repository from GitHub, install the necessary dependencies, and configure your database connection in the Claude Desktop configuration file. You can then interact with your database using natural language commands.

key features of MCP Database Server?

  • Natural language database operations
  • Support for MongoDB with features like listing collections, querying, inserting, deleting, and aggregating data
  • Future support for PostgreSQL, CockroachDB, and Redis

use cases of MCP Database Server?

  1. Querying a MongoDB database using simple English commands.
  2. Inserting and deleting records without writing complex queries.
  3. Aggregating data from collections to generate insights.

FAQ from MCP Database Server?

  • What databases does MCP Database Server support?

Currently, it supports MongoDB, with plans to add PostgreSQL, CockroachDB, and Redis in the future.

  • Is there a specific version of Node.js required?

Yes, Node.js version 20.12.2 or higher is required to run the server.

  • Can I contribute to the MCP Database Server?

Yes! Contributions are welcome, and you can submit a Pull Request or open an issue to discuss changes.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
manpreet2000
Star
0
Language
TypeScript
License
MIT license

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

2 days ago
Tavily Mcp
@tavily-ai

JavaScript
a year ago