MCP Database Server

What fireproof-storage/mcp-database-server MCP server does

The fireproof-storage/mcp-database-server MCP server connects an MCP client to a Fireproof database used as a JSON document store. Its documented scope is intentionally small: it demonstrates how to make application data available to AI systems through MCP.

Documents can be created, retrieved, changed, and removed. The server also supports querying documents with results sorted by a selected field. This makes it suitable for straightforward structured records where JSON documents and basic ordering are sufficient.

The project description identifies the underlying database as a Fireproof ledger database with multi-user sync. The README excerpt focuses on the JSON document server and its CRUD and sorting behavior, so more advanced synchronization workflows are not described here.

How it works

MCP clients communicate with the process over standard input and standard output. A client starts the server as a local process, then uses the server's document operations through the MCP connection. The database layer is provided by Fireproof, while the MCP interface makes the stored records available to an AI application.

This architecture is useful for local integrations because the README does not describe a hosted endpoint, account setup, or API credential requirement. The server is presented as a demo and example rather than as a complete database administration layer.

Setup and configuration

The repository README instructs developers to install the project dependencies with npm and build the project before running it. It then shows a Claude Desktop MCP configuration whose command points to the generated build/index.js file.

The configuration file locations given are:

• macOS: ~/Library/Application Support/Claude/claude_desktop_config.json
• Windows: %APPDATA%/Claude/Claude_desktop_config.json

The example uses a placeholder absolute path, so the command must be adjusted to point to the built entry point in the local checkout. The README does not provide a published npm package or a universal executable command.

For debugging, the project includes an npm run inspector script that launches the MCP Inspector and provides a browser URL for inspection. The Inspector is a development aid, not the database server itself.

Tools and capabilities

The fireproof-storage/mcp-database-server MCP server provides the following documented capabilities:

• Create JSON documents
• Read JSON documents
• Update JSON documents
• Delete JSON documents
• Query documents with sorting by any field

These operations cover basic document lifecycle management. The provided material does not specify tool names, input schemas, filtering expressions, pagination, indexes, authentication, or transaction controls.

Limitations and notes

The project is described as a simple example, so its documented feature set should not be treated as a complete general-purpose database API. Only CRUD operations and field-based sorting are confirmed by the README excerpt. Details about document identifiers, persistence locations, concurrent writes, sync configuration, and multi-user access are not provided.

The fireproof-storage/mcp-database-server MCP server uses stdio, which can make interactive debugging less convenient. The repository recommends the MCP Inspector for that purpose. Claude Desktop compatibility is explicitly documented; compatibility with other MCP clients is not established by the supplied material.