mcp-json-db-collection

This MCP server implements a multi-database JSON document store built on Fireproof, exposing a simple CRUD interface across multiple JSON databases. It lets you create, read, update, delete, and query documents within any database, and supports sharing databases to the Fireproof cloud for collaboration. To integrate with Claude Desktop or similar AI tooling, configure the MCP server in your client app by pointing the tool to the server’s entrypoint so it can issue CRUD and query operations against named databases like elements, cookie_ingredients, or horse_breeds. Start by building and running the server, then use the provided JSON APIs to create databases, insert documents, run queries, and enable cloud sync for sharing and backup.

Prerequisites:

• Node.js 14+ (npm comes with Node.js)
• Basic familiarity with npm and the project structure

Steps:

1. Install dependencies

git clone https://github.com/your-org/jimpick-mcp-json-db-collection-server.git
cd jimpick-mcp-json-db-collection-server
npm install

2. Build the server

npm run build

3. Run the server locally (example)

# Depending on your environment, the server entry may be at build/index.js
node build/index.js

4. Configure your MCP client (e.g., Claude Desktop) to point to the server, using the server name json-db-collections as shown in the README configuration example.

{
  "mcpServers": {
    "json-db-collections": {
      "command": "<base-dir>/mcp-json-db-collection-server/build/index.js"
    }
  }
}

Tips:

• The server supports multiple JSON databases (e.g., elements, cookie_ingredients, horse_breeds). Use distinct database names to keep data separated.
• When sharing a database to the cloud, ensure you have Cloud access configured for Fireproof as described in your Fireproof setup.
• If you run into port or connection issues, verify the server process is running and that your client is pointing to the correct entrypoint (build/index.js).
• For production deployments, consider packaging the build artifacts and setting a stable entry script path, and secure any exposed endpoints per your environment's security requirements.