> For the complete documentation index, see [llms.txt](https://mcp.conserver.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://mcp.conserver.io/vconic-for-resellers/01-quick-start-guide.md).

# Quick Start Guide

**Audience:** Reseller sales engineers and pre-sales staff who need a working demo on a laptop in under 20 minutes.

> VCONIC MCP Server is the reseller distribution of the open-source [`vcon-mcp`](https://github.com/vcon-dev/vcon-mcp) project. All install artifacts ship under the `vcon-mcp` name (npm package, Docker image, REST API path). VCONIC branding applies to packaging, support, and partner tooling — it is not a fork.

## Reseller lens

Use this guide to stand up a single-tenant demo from your laptop. For multi-customer / production patterns, jump straight to the [Installation Guide](/vconic-for-resellers/02-installation-guide.md).

## What you need

* Docker 24+
* A Supabase project (cloud or [self-hosted](/deployment/self-hosted-supabase.md))
* An MCP-capable AI client (Claude Desktop is the easiest demo)

## 1. Pull the image

```bash
docker pull public.ecr.aws/r4g1k2s3/vcon-dev/vcon-mcp:latest
```

Tags published per build: `main-<7-char-sha>`, `latest` (main HEAD), and semver tags (e.g. `1.2.0`, `1.2`, `1`) on tagged releases.

## 2. Apply database migrations

Run migrations against the Supabase project once. The image bundles the Supabase CLI:

```bash
docker run --rm \
  -e SUPABASE_DB_URL='postgresql://postgres:<pwd>@<host>:5432/postgres' \
  public.ecr.aws/r4g1k2s3/vcon-dev/vcon-mcp:latest \
  migrate
```

For deeper context on migrations and what they touch, see [Migration Guide](/reference/migration_guide.md).

## 3. Start the server (stdio for Claude Desktop)

The fastest demo path is stdio, launched directly by Claude Desktop. Add this block to your Claude Desktop config (`~/Library/Application Support/Claude/claude_desktop_config.json` on macOS):

```json
{
  "mcpServers": {
    "vconic": {
      "command": "docker",
      "args": [
        "run", "-i", "--rm",
        "-e", "SUPABASE_URL=https://your-project.supabase.co",
        "-e", "SUPABASE_ANON_KEY=your-anon-key",
        "public.ecr.aws/r4g1k2s3/vcon-dev/vcon-mcp:latest"
      ]
    }
  }
}
```

Restart Claude Desktop. The `vconic` server appears in the MCP tools menu.

## 4. Smoke-test from the client

Ask the assistant something simple:

> "Show me the database shape."

It should call `get_database_shape` and return tables and row counts.

## 5. Next steps

* Production install → [Installation Guide](/vconic-for-resellers/02-installation-guide.md)
* Tune env vars → [Configuration Guide](/vconic-for-resellers/03-configuration-guide.md)
* See available tools → [MCP Tools reference](/api-reference/tools.md)

## See also

* [Quick Start (developer view)](https://github.com/vcon-dev/vcon-mcp/blob/main/docs/guide/quick-start.md)
* [Getting Started](/guide/getting-started.md)
* [Docker deployment](/deployment/docker.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://mcp.conserver.io/vconic-for-resellers/01-quick-start-guide.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.