Database Tools for Claude AI

Created By
elber-codea year ago
MCP tool that allows you to interact with MySQL databases
Overview

What is Database Tools for Claude AI?

Database Tools for Claude AI is an MCP (Model Context Protocol) server that enables Claude AI to interact directly with MySQL databases, allowing users to execute SQL queries and retrieve data seamlessly.

How to use Database Tools for Claude AI?

To use this tool, clone the repository, install the necessary dependencies, and configure the claude_desktop_config.json file to include the database tools server settings. Once set up, you can issue commands to Claude to interact with your MySQL databases.

Key features of Database Tools for Claude AI?

  • Query MySQL databases through Claude AI.
  • Execute any valid SQL query.
  • Retrieve information about tables, including size and structure.
  • Get formatted results for easy reading in Claude.

Use cases of Database Tools for Claude AI?

  1. Listing all databases in a MySQL server.
  2. Viewing tables within a specific database.
  3. Querying the size of a specific table.
  4. Executing custom SQL queries for data retrieval.

FAQ from Database Tools for Claude AI?

  • How do I install the Database Tools for Claude AI?

Clone the repository and run npm install to install dependencies.

  • What permissions are required for the MySQL user?

The MySQL user should have permissions only for the operations you want to allow to ensure security.

  • What should I do if I encounter connection problems?

Check if MySQL is running, verify the credentials in mysql.js, and ensure the path in the Claude configuration file is correct.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
elber-code
Star
3
Language
JavaScript
License
-

Recommend Servers

View All
Tavily Mcp
@tavily-ai

JavaScript
a year ago
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)

a day ago