> For the complete documentation index, see [llms.txt](https://www.conserver.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://www.conserver.io/tools/mongo-redis-sync.md).

# Mongo Redis Sync

**Repo:** [vcon-dev/mongo-redis-sync](https://github.com/vcon-dev/mongo-redis-sync)

A small utility that mirrors vCons between a MongoDB long-term store and a Redis cache. Useful when:

* You're using Mongo as durable storage but the conserver pipeline expects vCons in Redis.
* You're migrating a deployment between the two and want bidirectional sync during the transition.
* You want hot vCons in Redis for low-latency reads while keeping the canonical copy in Mongo.

This tool predates much of the current conserver storage layer and is most useful for deployments that pre-date the unified Supabase backend used by `vcon-mcp`. For new deployments, prefer the conserver's native storage configuration — see [Storage](/conserver/storage.md).

## See also

* [Conserver Storage](/conserver/storage.md)
* [Production Deployment](/conserver/production-deployment.md)


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://www.conserver.io/tools/mongo-redis-sync.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.