connect_json_doc_database_to_cloud
Connect a JSON document database to cloud sync service
LABSCO SUMMARY
Local-first with sync as an opt-in per database is the right default for storage an agent creates on its own.
An agent that can create databases will create several, most of them scratch. Having them local by default means that costs nothing and leaks nothing, and promoting one to synced when it turns out to matter is a decision rather than a default. Querying sorted by a field rather than only by id is the minimum that makes a document store useful for anything beyond key-value, and it is here. Small surface, honest scope: this is a place for an agent to keep structured state between sessions, not a database you would build a product on.
What it is
A Fireproof-backed JSON document store where databases are created and managed as objects, with optional cloud sync per database.
What you get
- Databases created, listed and deleted as first-class things, so an agent can partition its own storage rather than sharing one bucket.
- Documents saved, loaded by id, queried sorted by a field, and deleted.
- connect_json_doc_database_to_cloud attaches a database to cloud sync and shows the dashboard, so local-first becomes shared when you want it to.
- list_json_doc_databases is described as the way to understand which databases exist before working against one.
Requirements
Nothing to supply for local use. Cloud sync is opt-in per database rather than the default.
Setup effort
One command — npx -y @jimpick/mcp-json-db-collection-server
USE CASES
01
Giving an agent somewhere to keep structured state
Create a database for the purpose, save documents into it, and load them back by id in a later session.
02
Finding what you stored
Query sorted by a field rather than needing the id you did not keep.
03
Making one of them shared
Connect that database to cloud sync — opt-in per database, so the scratch ones stay local.
04
Cleaning up
Delete the documents or the whole database once the work is done.
8 tools
Counted once with only startup setup. Other versions, modes or optional credentials may expose a different list.
create_json_doc_database
Create a JSON document database
delete_json_doc_database
Delete a JSON document database
delete_json_doc_from_db
Delete a JSON document by ID from a document database
list_json_doc_databases
Returns the list of JSON document databases. Use this to understand which databases are available before trying to access JSON documents.
load_json_doc_from_db
Load a JSON document by ID from a document database
query_json_docs_from_db
Query JSON documents sorted by a field from a document database. If no sortField is provided, use the _id field.
save_json_doc_to_db
Save a JSON document to a document database
BEFORE YOU INSTALL
What to know first
Tools you get
8 tools when we connected.
Requires
npx on PATH
CONTEXT COST
Light Standing cost
Rated by the size of the 8 tool definitions that ride along on every turn, not by how many there are
INSTALLATION
Connect your client
Add the block to your client, or run the command directly.
Server setup
Configuration file
JSON
{
"mcpServers": {
"mcp-json-db-collection-server": {
"command": "npx",
"args": [
"-y",
"@jimpick/mcp-json-db-collection-server"
]
}
}
}npx
TERMINAL
npx -y @jimpick/mcp-json-db-collection-server
