mcp-database

This MCP server implements a simple JSON document store built on top of the Fireproof database. It exposes CRUD (Create, Read, Update, Delete) operations for JSON documents and supports queries that can sort documents by any field. The server is designed to plug into Model Context Protocol workflows, enabling AI systems to fetch, store, and manipulate structured JSON data within a Fireproof-backed store. To use it with Claude Desktop or other MCP-enabled clients, configure the server in your MCP config so that the client can start the server process and communicate via standard I/O channels.

When debugging, you can use the MCP Inspector tool to connect to the server’s stdio streams and inspect requests, responses, and performance. The inspector can be launched via npm run inspector if you’re developing locally, and it will provide a URL for debugging tools in your browser.

Prerequisites:

• Node.js and npm installed on your system
• Access to the project repository (or a prebuilt package)

Installation steps:

1. Install dependencies

   npm install
   

2. Build the project

   npm build
   

3. Run or configure the server path
   • Ensure the built entry point is available at the path referenced in your MCP config (e.g., /path/to/fireproof-mcp/build/index.js).
   • If integrating with Claude Desktop, update the Claude config with the correct path:

     {
       "mcpServers": {
         "fireproof": {
           "command": "/path/to/fireproof-mcp/build/index.js"
         }
       }
     }
     

Notes and tips:

• The server uses stdio for communication; ensure the host process manages input/output streams correctly.
• If you encounter startup issues, verify that the build output exists at the configured path and that Node.js version is compatible with your package.
• For debugging, run npm run inspector to start the MCP Inspector and obtain a debugging URL.
• If environment variables are needed (e.g., Fireproof credentials or project IDs), pass them in the environment for the running process or extend the mcp_config with an env object as needed.