Skip to main content
Glama
AnuragRai017

Database Updater MCP Server

by AnuragRai017
README.md
# database-updater MCP Server
[![database-updater-MCP-Server MCP server](https://glama.ai/mcp/servers/AnuragRai017/database-updater-MCP-Server/badges/score.svg)](https://glama.ai/mcp/servers/AnuragRai017/database-updater-MCP-Server)

A Model Context Protocol server for updating databases from CSV and Excel files.

## Features

### Tools
- `update_database` - Update database from CSV/Excel files
  - Supports CSV and Excel (.xlsx, .xls) file formats
  - Compatible with multiple database types (PostgreSQL, MySQL, MongoDB, SQLite)
  - Configurable connection settings and table mapping
  
- `create_note` - Create and manage notes (for documentation)
  - Store important information about database updates
  - Track changes and modifications

## Usage

### Update Database
Use the `update_database` tool with the following parameters:
```json
{
  "filePath": "/path/to/your/file.csv",
  "databaseType": "PostgreSQL",
  "connectionString": "postgresql://user:pass@localhost:5432/db",
  "tableName": "target_table"
}
```

### Supported Database Types
- PostgreSQL
- MySQL
- MongoDB
- SQLite

## Development

Install dependencies:
```bash
npm install
```

Build the server:
```bash
npm run build
```

For development with auto-rebuild:
```bash
npm run watch
```

## Installation

To use with Claude Desktop, add the server config:

On MacOS: `~/Library/Application Support/Claude/claude_desktop_config.json`
On Windows: `%APPDATA%/Claude/claude_desktop_config.json`

```json
{
  "mcpServers": {
    "database-updater": {
      "command": "/path/to/database-updater/build/index.js"
    }
  }
}
```

### Debugging

Since MCP servers communicate over stdio, debugging can be challenging. We recommend using the [MCP Inspector](https://github.com/modelcontextprotocol/inspector):

```bash
npm run inspector
```

The Inspector will provide a URL to access debugging tools in your browser.

TDQS

C2.8/5.0

Scored across 2 tools

Disambiguation5/5

The two tools have completely distinct purposes with no overlap: create_note is for creating a new note, while update_database is for updating a database from a file. An agent can easily tell them apart based on their different functions and target resources (note vs. database).

Naming Consistency2/5

The naming is inconsistent: create_note follows a verb_noun pattern, but update_database uses a verb_noun pattern with a different verb style (update vs. create) and lacks a clear object for the update action. While both are readable, they do not follow a predictable or uniform convention across the set.

Tool Count2/5

With only 2 tools, this server feels thin for a 'Database Updater' purpose. The scope suggests operations like querying, deleting, or managing database entries, but only update_database directly relates, while create_note seems out of place. This mismatch makes the count inappropriate for the apparent domain.

Completeness2/5

The tool surface is significantly incomplete for a database updater server. There are no tools for reading, deleting, or querying the database, and create_note does not align with the core domain. This leaves obvious gaps that will hinder agents in performing typical database operations.

Maintenance

ActivityInactive
ResponsivenessNo issues