M
MCP Directory CURATED DIRECTORY
911 MCP servers indexed
中文
← Back to directory
P

Pare DB

Community
Structured database CLI operations as typed JSON
How to install ↓ Compare GitHub source repository ↗
Category
Database #58 of 58
Stars
★ 138 Popular
Transport
stdio (local process)
Runtime
Node.js >= 20
Credentials
No credential needed
License
MIT
Last commit
Tools
4

Static review · not runListed 2026-08-07

FMRS 32/100 · D · Weakest Reliability 4/20 — Read the FMRS scoring method →

Fit and risk

What it can accessRuns commands or codeConnects to a database

Best for

  • AI coding tools that need to interact with PostgreSQL, MySQL, Redis, or MongoDB via typed JSON
  • Scripting and automation workflows involving database operations

Not for

  • Users requiring GUI or complex database administration features
  • Scenarios needing non-standard or specialized database CLIs

Required permissions

  • Requires local installation and execution of psql, mysql, redis-cli, or mongosh commands
  • Requires database connection credentials

Risks and side effects

  • AI agents may execute destructive database operations (e.g., DELETE, UPDATE) if not careful
  • Potential exposure of sensitive data if credentials are present
  • Misconfiguration may lead to database connectivity or permission issues

Setup

Before you start

Runtime：Node.js >= 20

Other optional settings (1)
PARE_TOOLS optional Universal tool filter across all servers, formatted as comma-separated server:tool pairs (e.g., git:status,npm:install); takes precedence over per-server vars.

Install via npm using npx: npx @paretools/db. It is recommended to configure tool selection via environment variables like PARE_DB_TOOLS to limit available tools. For MCP clients, add a server entry with command npx and args -y @paretools/db.

claude_desktop_config.json 
{
  "command": "npx",
  "args": [
    "-y",
    "@paretools/db"
  ]
}

Shown for Claude Desktop. Other clients may use a different file or key (VS Code uses "servers") — the configurator below converts it.

Generate and validate client config

Check that it works

After restarting the MCP client, confirm that the tools psql, mysql, redis-cli, and mongosh appear in the client's tool list, or run npx @paretools/init doctor to validate the setup.

Troubleshooting

  1. Ensure the required database CLI tools are installed and executable
  2. Check MCP client configuration for correct command and arguments
  3. Verify database connection strings or credentials are correct

Things to try

Once connected, you can ask your AI assistant things like:

  • Query the latest 10 rows from the users table in my Postgres database using psql.
  • Use redis-cli to check whether my cache server is up and list all keys.
  • Use mongosh to count the documents in the orders collection in MongoDB.
  • Query today's total sales from the orders table with mysql.

Tools 4

psql
Execute PostgreSQL queries and return structured JSON
mysql
Execute MySQL queries and return structured JSON
redis-cli
Execute Redis commands and return structured JSON
mongosh
Execute MongoDB queries and return structured JSON

Use cases

Enable AI agents to query databases and get structured results directly
Automate database tasks like migrations or data checks
Reduce token usage for AI agents when parsing database CLI output

Supported clients

Claude Desktop
Claude Code
Cursor

Listed from the project's documentation, not tested by this site.

Overview

Pare DB is an MCP server from the Pare project that wraps common database CLI tools (psql, mysql, redis-cli, mongosh) and returns schema-validated JSON instead of raw terminal text. Designed for AI agents (e.g., Claude, Cursor) to interact directly with databases without fragile parsing. Suitable for developers and teams using AI coding tools to perform standard database operations like queries, table management, and data manipulation. Not intended for users needing advanced database administration features or non-standard CLI workflows. It requires local installation of the underlying CLI tools and communicates via stdio. Risks include potential data misuse by AI agents, such as destructive operations, and exposure of sensitive data if credentials are present. Troubleshooting typically involves verifying CLI tool installation, correct MCP configuration, and database connectivity.

Similar servers

Compare with other MCP servers

More servers from this repository

Pare BazelPare BuildPare BunPare CargoPare CmakePare DenoPare DockerPare DotnetPare GitPare GithubPare GoPare HTTPPare InfraPare JvmPare LintPare MakePare NixPare NpmPare ProcessPare Python

Source revision 57e1980e8375 Data synced 2026-10-12 Read the FMRS scoring method