MCP Database Server

Connection Pooling

All database connections use connection pooling to optimize performance:

• SQLite: Uses a single persistent connection.
• SQL Server: Default pool of 5 connections.
• PostgreSQL: Default pool of 10 connections.

Connection Security Best Practices

1. SQL Server: In production, use --trustServerCertificate false and ensure proper SSL certificates are installed on the server.
2. PostgreSQL: Use --ssl true and ensure the server is configured for SSL connections.
3. Credentials: Use environment variables instead of command-line arguments to prevent credential leakage in process lists.
4. Permissions: Store your Claude Desktop configuration file with appropriate file system permissions.

Supported Features

• Full SQL query support for SELECT, INSERT, UPDATE, and DELETE operations.
• Table management (CREATE TABLE, ALTER TABLE, DROP TABLE).
• Schema introspection.
• Connection pooling.
• SSL support for secure connections.

Limitations

• ID Retrieval: For the run method with INSERT statements, the adapter attempts to retrieve the last inserted ID by adding a RETURNING clause. This requires your tables to have an id column.
• Complex Logic: Complex stored procedures or PostgreSQL-specific features may require custom implementation.

The SQLite adapter utilizes standard SQLite features and storage classes:

Storage Classes (Dynamic Typing):

• NULL
• INTEGER
• REAL
• TEXT
• BLOB

Concurrency: By default, the server enables Write-Ahead Logging (WAL) mode to improve performance and allow better concurrency.

The SQL Server adapter supports three primary authentication methods:

SQL Server Authentication

Use the --user and --password flags to provide explicit credentials.

Windows Authentication

Omit the --user and --password flags to use a trusted connection (Windows Authentication).

Azure Active Directory

For Azure SQL Database, provide the Azure AD user identity via the --user flag and configure the server address accordingly.

# SQL Server Authentication
node dist/src/index.js --sqlserver --server myserver --database mydatabase --user myuser --password mypassword

# Windows Authentication
node dist/src/index.js --sqlserver --server myserver --database mydatabase

When crafting SQL queries via Claude, be aware of these syntax differences between SQL Server and SQLite:

When crafting queries via Claude, be aware of these syntax differences between SQL Server and SQLite:

Supported Features

• Full SQL query support for SELECT, INSERT, UPDATE, and DELETE operations.
• Table management (CREATE TABLE, ALTER TABLE, DROP TABLE).
• Schema introspection.
• Connection pooling.
• SSL support for secure connections.

Limitations

• Last Inserted ID: For the run method with INSERT statements, the adapter attempts to retrieve the last inserted ID by adding a RETURNING clause. This requires your tables to have an id column.
• Advanced Features: Complex stored procedures or highly specific PostgreSQL features may require custom implementation.

Install the MCP Database Server globally using NPM to make the package available for use with MCP clients like Claude Desktop.

npm install -g @executeautomation/database-server

To use the SQLite adapter within Claude Desktop, add a configuration entry to your mcpServers object. You can use npx to run the package directly or point to a local installation.

Using npx (Recommended for production/general use):

{
  "mcpServers": {
    "sqlite": {
      "command": "npx",
      "args": [
        "-y",
        "@executeautomation/database-server",
        "/path/to/your/database.db"
      ]
    }
  }
}

Using local installation (For development):

{
  "mcpServers": {
    "sqlite": {
      "command": "node",
      "args": [
        "/absolute/path/to/mcp-database-server/dist/src/index.js", 
        "/path/to/your/database.db"
      ]
    }
  }
}

To ensure successful interactions with the database tools, follow these guidelines:

1. Be specific about database type: If you have multiple database configurations, tell Claude which one you want to use.
2. Security awareness: Avoid exposing sensitive database credentials in your conversations.
3. SQL syntax differences: Remember that SQL syntax might differ between database types (e.g., SQLite vs. SQL Server).
4. Error handling: If Claude encounters an error, it will report the error message; use this information to correct your query or instructions.
5. Complex operations: For complex operations, consider breaking them down into smaller, incremental steps.

For Amazon RDS MySQL instances using IAM database authentication, use the --aws-iam-auth flag. SSL is automatically enabled.

Prerequisites: AWS credentials must be configured via aws configure, AWS_PROFILE environment variable, or standard AWS environment variables (AWS_ACCESS_KEY_ID, etc.).

Required parameters:

• --host: RDS endpoint hostname
• --database: Name of the database
• --aws-iam-auth: Enable AWS IAM authentication
• --user: AWS IAM username (also the database user)
• --aws-region: AWS region where RDS instance is located

CLI Command:

node dist/src/index.js --mysql --aws-iam-auth --host <rds-endpoint> --database <database-name> --user <aws-username> --aws-region <region>