---
name: glizzy-pages
description: Publish and update shareable HTML pages through the Glizzy Pages MCP server. Use when the user asks to present data, create a visual report, publish an interactive HTML artifact, or revise a page previously published through Glizzy Pages.
---

# Glizzy Pages

Use the connected `glizzy-pages` MCP server to publish complete HTML documents and return stable share links.

## Required MCP connection

The remote MCP server is:

```
https://pages.glizzyhq.com/mcp
```

It authenticates in the browser with the user's team Google account. Never request, create, store, or use an API key. Never call the Glizzy Pages HTTP API directly.

If the MCP tools are unavailable, tell the user to connect the server and complete Google sign-in. Do not attempt another publishing method.

## Tools

- `create_page`: Publish a new complete HTML document. Use `google` access unless the user explicitly requests a public link.
- `list_pages`: Find the user's existing pages and stable slugs.
- `get_page`: Read the current source and metadata for one page.
- `update_page`: Update an existing slug. HTML changes create a new version without changing the share URL.

## Workflow

1. For a new artifact, create a complete HTML document and call `create_page`.
2. For a revision, identify the stable slug, call `get_page`, preserve everything the user did not ask to change, then call `update_page`.
3. After every create or update, return the tool's `shareUrl`, access mode, and whether the page was created or updated.

## Page requirements

- Produce a complete HTML document, not a fragment.
- Keep CSS and JavaScript inline or use stable HTTPS assets.
- Make pages responsive and accessible.
- Do not include secrets, private tokens, or credentials in HTML.
- Keep page HTML smaller than 750 KB.
- Scripts run in a sandbox without access to the parent app or its cookies.
- Prefer updating the existing slug when the user is revising a prior page.