voog-mcp 1.0.2

CLI and MCP server for Voog CMS — Liquid templates, pages, products, ecommerce

voog-mcp

CLI and MCP server for Voog CMS — manage Liquid templates, pages, products, ecommerce settings, and redirects from your terminal or directly from Claude / any MCP client.

What is Voog?

Voog is a multilingual website builder and CMS with built-in ecommerce, used for content sites and small online stores. This package wraps its admin API so you can edit templates, pages, products, and redirects from your shell or an LLM agent.

Install

From PyPI:

pip install voog-mcp
# or, no install: uvx voog-mcp --help

Or directly from GitHub (latest unreleased main):

uvx --from git+https://github.com/runnel/voog-mcp.git voog --help

For development:

git clone https://github.com/runnel/voog-mcp
cd voog-mcp
python3.10 -m venv .venv && source .venv/bin/activate
pip install -e ".[dev]"

Configure

Run voog config init to interactively create the global config:

voog config init

This creates:

• ~/.config/voog/voog.json — site registry
• ~/.config/voog/.env (template) — where to put API tokens

Example voog.json:

{
  "sites": {
    "mysite":   {"host": "mysite.com",   "api_key_env": "MYSITE_API_KEY"},
    "client_a": {"host": "clienta.com",  "api_key_env": "CLIENT_A_KEY"}
  },
  "default_site": "mysite"
}

Example .env:

MYSITE_API_KEY=...your token here...
CLIENT_A_KEY=...another token...

Get a token from your Voog admin: Admin → API.

Per-repo site selection

In a repo dedicated to one Voog site, drop a voog-site.json to pin the site:

{"site": "mysite"}

Now voog pull / voog push from that directory always target the right site, even if the global default differs.

Use the CLI

voog --help                      # all commands
voog --site mysite products      # list products on mysite
voog pull                        # download templates (uses voog-site.json)
voog push layouts/Front\ page.tpl
voog redirects
voog config check                # verify all configured tokens

Use as MCP server

Add to your Claude Code config (or any MCP client):

{
  "mcpServers": {
    "voog": {
      "command": "uvx",
      "args": ["--from", "git+https://github.com/runnel/voog-mcp.git", "voog-mcp"]
    }
  }
}

Every tool requires a site parameter. Start with voog_list_sites to discover what's configured:

voog_list_sites()
→ [{"name": "mysite", "host": "mysite.com"}, ...]

voog_get_page(site="mysite", page_id=42)
→ {...}

What's NOT supported

voog-mcp covers the surface area needed to manage content and a small ecommerce catalog. The following Voog API areas are intentionally out of scope for now:

• Form definitions and form responses
• Comments and visitor data
• Site-level settings, languages, and translations
• Customer, order, and cart data (ecommerce orders/checkout flows)
• Users, roles, and permissions
• General asset/media library uploads (product images are supported)
• Site creation (voog-mcp targets existing sites)

If you need any of these, open an issue — or a PR.

License

MIT