mcpField
W
WIP: Caution!!! AI code and probably wrong in many ways though it "runs".

WIP: Caution!!! AI code and probably wrong in many ways though it "runs".

Local
github.com/angrysky56Databases0Updated 100w ago
Repository

About WIP: Caution!!! AI code and probably wrong in many ways though it "runs".

Workspace DB Manager is a TypeScript MCP server for managing SQLite databases associated with workspaces. It discovers database files and tracks filesystem changes, while offering database management and cross-database operations.

Key features

  1. 01Automatic SQLite database discovery
  2. 02Filesystem change monitoring
  3. 03Connection pooling and management
  4. 04Database tracking and status updates
  5. 05Cross-database operations

Use cases

  1. 01Discover databases in workspace paths
  2. 02Track database file additions and removals
  3. 03Monitor database modifications
  4. 04Manage multiple workspace databases

MCP support

Workspace DB Manager is an MCP server for workspace database management. The README does not specify the tools or resources it exposes to MCP clients.

Configuration

Local server config is the same for every client. Copy it into your client’s MCP config file.

No install method listed yet

We haven’t collected a package or remote endpoint for this server. Follow the instructions in the project README.

Repository

Tools

No tool list yet

Local servers expose tools only once running on your machine, and the maintainer has not provided a tool list.

Details

From the project README

WIP: Caution!!! AI code and probably wrong in many ways though it "runs".

Workspace DB Manager

CI

A TypeScript MCP (Model Context Protocol) server for managing workspace databases with filesystem integration.

Features

  • SQLite database management with automatic discovery
  • Real-time filesystem monitoring for database changes
  • Database connection pooling and management
  • Automatic database tracking and status updates
  • Cross-database operations support
  • TypeScript/ES Module architecture

Getting Started

  1. Install dependencies:
npm install
  1. Build the TypeScript code:
npm run build
  1. Initialize the core database:
npm run init-db
  1. Start the server:
npm start

Development

# Run in development mode with auto-reload
npm run dev

# Run tests
npm test

# Build TypeScript
npm run build

Continuous Integration

This project uses GitHub Actions for continuous integration:

  • Runs on Node.js 20.x, 21.x, and 22.x
  • Automatically runs tests on every push and pull request
  • Checks TypeScript compilation
  • Generates and uploads test coverage reports
  • Fails if code quality standards are not met

Configuration

The server can be configured through a WorkspaceConfig object:

const manager = new WorkspaceDBManager({
    watchPaths: ['/path/to/workspace'],
    pollInterval: 1000, // Optional: file system polling interval
    database: {
        verbose: true // Optional: enable verbose database logging
    }
});

Database Operations

Automatic Database Discovery

The server automatically detects and tracks:

  • New database files
  • Database modifications
  • Database removals
Database Management
// List all managed databases
const databases = await manager.listManagedDatabases();

// Get system configuration
const config = await manager.getConfig('some_key');
Events

The server emits events for various operations:

  • database-added: When a new database is discovered
  • database-changed: When a database is modified
  • database-removed: When a database is removed
  • error: When an error occurs
  • initialized: When the server is fully initialized

Testing

# Run all tests
npm test

# Run tests with coverage
npm test -- --coverage

Contributing

  1. Fork the repository
  2. Create your feature branch
  3. Commit your changes
  4. Push to the branch
  5. Create a Pull Request

License

ISC

Comments

Markdown supported

New to MCP?

From what the protocol is to installing your first server, these answers cover most first questions.

An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.