> 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.md).

# Tools

Standalone tools and adapters that produce, consume, or operate on vCons.

The vCon ecosystem is more than the spec and the libraries. It's a set of practical tools you can run today. This section indexes them.

## Generators and converters

Tools that produce vCons.

* [vCon Faker](https://www.conserver.io/tools/vcon-faker.md): synthetic vCons from LLM-generated dialog + TTS audio
* [vCon Anthropic Chats](https://www.conserver.io/tools/vcon-anthropic-chats.md): converts Claude Code sessions and claude.ai exports into vCons
* [vCon SIPREC Adapter](https://www.conserver.io/tools/vcon-siprec-adapter.md): records SIPREC sessions as vCons
* [vCon MCP Adapters](https://www.conserver.io/tools/vcon-mcp-adapters.md): converts AI agent traces (Anthropic, OpenAI, Claude Code, Helicone, Langfuse, LangSmith) into vCons

## Administration & operations

Tools for managing vCons at scale.

* [vCon Admin](https://www.conserver.io/tools/vcon-admin.md): Streamlit toolkit for importing, exporting and inspecting vCons
* [Redis to Mongo Sync](https://www.conserver.io/tools/mongo-redis-sync.md): archived one-way copy from Redis to MongoDB

## Datasets

* [Public vCon Datasets](https://www.conserver.io/tools/vcon-datasets.md): public GitHub datasets of vCons, and how to load one with vcon-data

## Apps and stores

* [vCon Apps and Stores](https://www.conserver.io/tools/vcon-apps-and-stores.md): what vCon stores and apps are, the example app, and the TADHack dataset

## Adding a tool

If you've built something that produces, consumes, or operates on vCons and you'd like it indexed here, open a pull request against [vcon-dev/vcon-docs](https://github.com/vcon-dev/vcon-docs) adding a new page under `tools/`. Keep entries to: what it does in one sentence, when you'd use it, install / link, and one minimal usage example.


---

# 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 by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://www.conserver.io/tools.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.
