Skip to main content
Glama
Template Vault MCP

Template Vault MCP

by julioMeif

Template Vault MCP

License

Connect Claude Desktop, ChatGPT, Cursor, Windsurf — or any MCP-speaking AI client — to Template Vault, an AI website builder for small businesses.

What it does

This package is the thin client-side adapter for the Template Vault MCP server. It bridges stdio-based MCP clients (Claude Desktop, Cursor) to our hosted HTTP+OAuth server.

Once connected, your AI can:

Tool

Purpose

discover_business_needs

Interview the user about their business with niche-tailored follow-ups (always called first).

list_personalities

List the visual styles (classic, minimal, gradient, zen, immersive, glass).

generate_site

Generate a full website from a populated business profile. Returns a job id.

get_generation_status

Poll the build status (pending → processing → completed).

list_user_sites

List the user's existing sites.

publish_site

Deploy a site to production at slug.the-template-vault.com.

End-to-end, a one-page Spanish-and-English bilingual site for a Miami pool builder takes ~60 seconds from "build me a website" to a real running URL.

Related MCP server: WebCake Storefront MCP

Install

Claude Desktop

Open your claude_desktop_config.json (Settings → Developer → Edit Config) and add:

{
  "mcpServers": {
    "template-vault": {
      "command": "npx",
      "args": ["-y", "template-vault-mcp"]
    }
  }
}

Restart Claude Desktop. The first time you ask it to use a Template Vault tool, your browser will open for OAuth — log in (or sign up) at the-template-vault.com, click Allow, done.

Claude.ai (web)

Claude.ai speaks HTTP MCP natively — you don't need this adapter. Just add a custom connector:

  1. Settings → Connectors → Add custom connector

  2. URL: https://www.the-template-vault.com/api/mcp

  3. Click Connect → OAuth flow → Allow

Cursor

In ~/.cursor/mcp.json:

{
  "mcpServers": {
    "template-vault": {
      "command": "npx",
      "args": ["-y", "template-vault-mcp"]
    }
  }
}

ChatGPT (Developer Mode)

OpenAI's MCP support uses an HTTP endpoint directly. Add the connector URL https://www.the-template-vault.com/api/mcp in ChatGPT's developer settings.

Auth & data

  • OAuth 2.1 + PKCE with refresh tokens — authorize once, stay connected for 90 days.

  • No credentials are stored in this repo. Tokens live in mcp-remote's per-user cache (~/.mcp-remote-auth/ by default).

  • Quota — each generate_site call counts against your monthly Template Vault plan (5 free / month on the free tier).

  • Per-user isolation — your AI can only see and act on YOUR sites.

Pricing

  • Free — 1 site, 5 generations/month

  • Pro — $15/mo, 5 sites, 25 generations, custom domains

  • Business / Agency — for multi-site / agency use

See pricing.

Content policy

We decline generation requests for content categories listed in CONTENT_POLICY.md — including adult content, hate speech, scams, illegal goods, CSAM, and impersonation/phishing sites. Requests that match these categories return an explicit error message rather than silently generating.

The Template Vault generator itself (Anthropic Sonnet) applies its own content safety on top — so a borderline request that gets past our pre-filter will typically be refused by the model. Multiple layers, defense in depth.

How it works

┌──────────────────────┐         stdio        ┌─────────────────────────┐
│  Claude Desktop /    │ ─────────────────▶  │ template-vault-mcp     │
│  Cursor / Windsurf   │ ◀───────────────── │ (this package)          │
└──────────────────────┘                     └────────────┬────────────┘
                                                          │ HTTPS + OAuth
                                                          ▼
                                             ┌─────────────────────────┐
                                             │  Template Vault         │
                                             │  api/mcp (hosted)       │
                                             └────────────┬────────────┘
                                                          │
                                                          ▼
                                                Site generation
                                                + Vercel deploy

The adapter has no business logic — it forwards stdio messages to the hosted MCP server and forwards responses back. All tool descriptions, schemas, and workflows live server-side; you always get the latest version without updating the package.

Open source

MIT licensed. The platform itself (the generator, the editor, the deployer) is closed source; this adapter is the open-source layer customers and contributors can inspect, fork, and build on.

PRs welcome for the adapter — bug fixes, additional client integrations, Docker improvements. Tool changes happen server-side; for those, open an issue or contact us at contact@the-template-vault.com.

Available Tools

6 tools
discover_business_needsA
Read-onlyIdempotent

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.

Inputs: businessHint.

generate_siteA
Destructive

Generate a new website for a business. Returns a jobId immediately — the build runs asynchronously (~30-90s). Poll get_generation_status to find the site_id + preview URL once it's done.

PREREQUISITE: You MUST have called discover_business_needs first and asked the user the resulting questions. Calling generate_site without a populated businessProfile produces a poor site missing integrations — WhatsApp buttons, Instagram embeds, booking widgets — and that embarrasses both the user and Template Vault.

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 { skippedDiscovery: true } so the backend can warn in the admin log.

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.

Inputs: businessName (required), businessDescription (required), industry (required), businessProfile (required), +3 more.

get_generation_statusA
Read-onlyIdempotent

Check the status of a generation job. Returns status (pending|processing|completed|failed), siteId (when completed), and an estimated progressPercent. Recommended polling interval: 5 seconds. The job typically takes 30-90 seconds total.

Inputs: jobId (required).

list_personalitiesA
Read-onlyIdempotent

List the visual personalities (styles) Template Vault can generate. Use to pick a style that fits the business before calling generate_site.

Inputs: no named parameters.

list_user_sitesA
Read-onlyIdempotent

List sites owned by the authenticated user. Use to find a siteId before calling publish_site.

Inputs: no named parameters.

publish_siteA
DestructiveIdempotent

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.

Inputs: siteId (required).

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    A4.4/5.0

    Scored across 6 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: discovery, generation, status polling, style listing, site listing, and publishing. No two tools overlap in functionality.

    Naming Consistency5/5

    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.

    Tool Count5/5

    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.

    Completeness5/5

    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.

    Maintenance

    ActivityInactive
    ResponsivenessNo recent community issues

    Related MCP Connectors

    Related MCP Servers