@share-html/mcp-server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SHARE_HTML_API_TOKEN | Yes | Your personal access token for share/artifacts. Treat like a password. | |
| SHARE_HTML_API_BASE_URL | Yes | The base URL for the share/artifacts API, e.g., https://shareartifacts.dev/api/v1 |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_recipeA | List first-party share/artifacts recipes, or get one reviewed prompt and static HTML starter by recipeId. Omit recipeId to discover the catalog. |
| publish_htmlA | Publish a complete static HTML document and return its stable URL. Omitted sharing is private to the owner. Explicitly choose public or combine domain, specific-email, and password access with an optional expiration. |
| publish_presentationA | Create slides, a slide deck, pitch deck, talk, lesson, or keynote as a first-class HTML presentation. First call get_recipe with recipeId "presentation-deck". Structural validation and DOM checks alone are not visual QA. When browser or rendering tools are available, render and inspect the actual rendered pixels of every slide at the declared desktop canvas, a narrow viewport, and print size; fix the source HTML/CSS and re-render affected slides until the full deck passes before publishing, re-rendering every slide after shared CSS changes. If rendering is unavailable, tell the user that visual QA was not completed; publishing may proceed with that disclosure. ShareHTML sanitizes and validates the deck, persists it, applies access controls and CSP, and returns its presentation viewer URL. |
| update_pageC | Replace a page with new static HTML while preserving its shareable URL. |
| get_pageB | Get the current status, version, and URL for one page. |
| list_pagesA | Search and page through the current user's published, offline, and platform-taken-down artifacts by title or page ID. Follow nextCursor to continue through large libraries. |
| publish_pageB | Bring an unpublished page back online at its existing URL. |
| unpublish_pageA | Take a page offline without deleting it or changing its shareable URL. |
| delete_pageB | Permanently remove a page from the user's artifact library. |
| get_page_sharingB | Get who can open a page and when access expires. |
| set_page_sharingA | Choose owner-only, public, or restricted access. Restricted methods are OR alternatives. Use the revision returned by get_page_sharing. |
| end_current_viewing_sessionsB | Invalidate current private viewing sessions. People who are still authorized can open the page again. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 12 tools
Each tool has a clearly distinct purpose: lifecycle, sharing, and publishing for pages are well separated. The only potential overlap is between 'publish_html' and 'publish_page', but 'publish_html' creates a new page while 'publish_page' brings an offline page back online; the descriptions clarify this difference.
Most tools follow a consistent verb_noun pattern (get_page, publish_html, update_page, list_pages, etc.), but there are deviations: 'end_current_viewing_sessions' uses a verb_phrase and 'get_page_sharing'/'set_page_sharing' add a suffix. Overall, the naming is predictable and readable.
With 12 tools, the count is well-scoped for a page management server, covering creation, retrieval, updates, sharing, and deletion without excessive granularity or obvious redundancy.
The surface covers the full lifecycle of pages: creation (publish_html), retrieval (get_page, list_pages), updates (update_page), deletion (delete_page), and sharing controls (get/set_page_sharing, end_current_viewing_sessions, unpublish/publish_page). There are no apparent gaps for the stated purpose.