mcp-database

The MCP Database Server provides Claude with programmable database access across SQLite, SQL Server, PostgreSQL, and MySQL. It exposes tools for performing read and write operations against these databases, enabling Claude to run SELECT queries to fetch data (read_query) and to execute INSERT/UPDATE/DELETE statements (write_query). To use it, start the server locally (or integrate it into your deployment) and configure Claude Desktop to point at the server entry point. You can connect to SQLite by passing a file path, or connect to other databases by supplying the appropriate host, database, and authentication details as shown in the README's usage examples. The server supports both direct usage and local development workflows, so you can either install the package globally and call it directly, or run it from your local environment during development.

Prerequisites:

• Node.js (recommended LTS) and npm installed on your system
• Git to clone the repository

Installation steps:

1. Clone the repository git clone https://github.com/executeautomation/mcp-database-server.git cd mcp-database-server

2. Install dependencies npm install

3. Build the project npm run build

Optional for local development / testing:

• Run the server from your local environment after building: node dist/src/index.js [arguments as needed]

If you prefer using the package directly via npm globally (as described in the README for direct usage):

• npm install -g @executeautomation/database-server
• This allows you to run the server directly without building it locally.

Notes and tips:

• The server supports multiple database types; ensure you pass the correct command-line options for the target database (sqlite, sqlserver, postgresql, mysql) as shown in the README.
• For AWS IAM authentication with MySQL (RDS), you must configure AWS credentials or use environment variables (AWS_PROFILE, AWS_ACCESS_KEY_ID, AWS_SECRET_ACCESS_KEY).
• When configuring Claude Desktop, use the appropriate JSON snippet for the target database and point the command to the built index.js file (or to the global npm package if using the direct/global approach).
• Ensure SSL/TLS settings are applied as required by your database providers, and review connection timeouts (defaults are provided in the README).
• If you encounter path issues, replace the placeholder path /absolute/path/to/mcp-database-server/dist/src/index.js with the actual absolute path to the built entry point on your system.