Template Vault MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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 |
|---|---|
| discover_business_needsA | REQUIRED FIRST STEP. Returns the question script you MUST ask the user before calling generate_site. Why: Template Vault's value is integration discovery — the generator detects what each business needs (WhatsApp button, Instagram block, booking, online ordering, etc.) based on these answers. Skipping discovery produces minimal text-only sites and embarrasses the user. ALWAYS call this tool first when a user asks to build/generate a website. After receiving the questions, ask them ONE AT A TIME in conversation — do not dump the whole list. Note answers, then build a complete businessProfile object for generate_site. |
| list_personalitiesA | List the visual personalities (styles) Template Vault can generate. Use to pick a style that fits the business before calling generate_site. |
| generate_siteA | Generate a new website for a business. Returns a PREREQUISITE: You MUST have called A populated businessProfile should include AT LEAST: a phone or whatsapp number, hasPhysicalLocation (+ address if true), hasSocialMedia (+ handles if true), and languages. If the user truly refuses discovery, pass Content policy: Template Vault declines categories listed at https://www.the-template-vault.com/docs/mcp/content-policy (adult content, hate speech, scams, illegal goods, CSAM, impersonation/phishing). Obvious matches are rejected synchronously with a clear error; subtler cases are caught by the underlying Anthropic model. Counts against the user's monthly generation quota. |
| get_generation_statusA | Check the status of a generation job. Returns |
| list_user_sitesA | List sites owned by the authenticated user. Use to find a siteId before calling publish_site. |
| publish_siteA | Publish a site to production at slug.the-template-vault.com. First publish wires up the GitHub repo + Vercel project; subsequent calls just trigger a Vercel rebuild that picks up the latest config from Supabase. |
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 6 tools
Each tool has a clearly distinct purpose: discovery, generation, status polling, style listing, site listing, and publishing. No two tools overlap in functionality.
All tool names follow a consistent verb_noun pattern (e.g., discover_business_needs, generate_site, list_personalities), making them predictable and easy to understand.
With 6 tools, the set is well-scoped for a website generation server. Each tool serves a necessary step in the workflow without being excessive or insufficient.
The tool set covers the entire lifecycle: discovery of business needs, generation, status tracking, style selection, site listing, and publishing. No obvious gaps for the intended domain.