Skip to main content
Glama
Postbuild MCP

Postbuild MCP

Official

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault

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.

Postbuild MCP (git-paid) audits deployed web applications for technical SEO, AI search crawler access (OAI-SearchBot, ClaudeBot, PerplexityBot), llms.txt, sitemap.xml, OpenGraph cards, SoftwareApplication JSON-LD, and Stripe checkout reachability. Use postbuild_scan, postbuild_directories, and postbuild_pseo for read-only inspection and previews. Use postbuild_fix, postbuild_dispatch, postbuild_inbox, postbuild_checkout, and postbuild_vault_sync when writing local artifacts, dispatching launches, verifying inboxes, or provisioning Stripe checkout.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{}
prompts
{}
resources
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
postbuild_scanA

Execute a read-only 8-point technical SEO, AI crawler (OAI-SearchBot, ClaudeBot, PerplexityBot), llms.txt, sitemap.xml, OpenGraph, JSON-LD, and checkout reachability audit against a live URL. Bare domains in url are normalized to https:// and DNS-resolved through an SSRF guard that rejects loopback, RFC1918 LAN, and cloud metadata IPs before fetching (rate-limited to 10 requests/min; no authentication required; computes the deterministic <slug>@postbuild.dev address without creating server state or local files). Use this tool when evaluating a deployed site's readiness score and failing checks; do not use it to write fix files (postbuild_fix), filter the 85 launch directories (postbuild_directories), or inspect full HTML product page drafts (postbuild_pseo).

postbuild_checkoutA

Provision a Stripe Product, USD Price, and hosted Payment Link (https://buy.stripe.com/...) via STRIPE_SECRET_KEY and write .postbuild/PostbuildCheckoutGate.jsx into cwd. When product_name or description are omitted, metadata is inferred by scraping url; interval switches Price creation between one-time (one_time) and recurring (month/year) billing, while allow_live gates sk_live_ keys (test keys sk_test_ run immediately, whereas live keys abort with LIVE_CONFIRMATION_REQUIRED before any Stripe API call or file write unless the user explicitly requested a live product). Each invocation creates a fresh Stripe Product/Price/Payment Link and overwrites only .postbuild/PostbuildCheckoutGate.jsx. Use this tool when adding Stripe monetization to a project; do not use it to check whether a live site already has checkout (postbuild_scan) or to generate SEO/llms.txt assets (postbuild_fix).

postbuild_directoriesA

Search and filter the local catalog of 85 launch targets (74 software/AI/SaaS directories and 11 launch communities) without network calls or side effects. Filters (category substring, status state, and min_da Domain Rating floor) combine with logical AND and are capped at limit records (unlicensed sessions return a 5-directory preview; a Launch Pass license pb_live_... unlocks all 85); repeated calls in the same session return stateful delta stubs unless bypass_cache: true forces full record hydration. Use this tool to explore and shortlist directories by authority or submission type; do not use it to generate pre-filled launch URLs and Show HN copy (postbuild_dispatch) or to verify directory confirmation emails (postbuild_inbox).

postbuild_pseoA

Generate a read-only preview of 7 targeted HTML product and comparison pages (features, comparison, workflow guide, developer guide, checklist, FAQ, AI search reference) tailored to url. Performs a live HTTP GET on url to classify the site vertical (saas_ai, ecommerce, agency_b2b, or local_service), filters the 7 generated routes by intent when supplied, and compacts unchanged fields across repeated session calls unless bypass_cache: true is set (returns 3 preview routes without authentication, or all 7 with a Launch Pass license pb_live_...; never writes to disk). Use this tool to inspect generated page slugs, target keywords, and HTML copy in memory; do not use it to write HTML files into a repository (postbuild_fix) or to run the 8-point site readiness audit (postbuild_scan).

postbuild_dispatchA

Prepare pre-filled submission URLs, Show HN titles, and 160-character launch copy across 85 directories (or the subset in directory_ids) and ping IndexNow for direct targets, gated by two-phase optimistic concurrency control. Calling with dry_run: true performs a read-only preview against expected_version and issues a single-use HMAC-SHA256 commit_token (ct_...); calling with dry_run: false requires that commit_token plus a valid Launch Pass license (pb_live_...), advancing the domain watermark to v2+ or rejecting stale watermarks/tokens with OCC_REJECTED before any mutation. Committing records dispatch state and pings IndexNow but does not submit external forms requiring human login or CAPTCHAs. Use this tool when preparing and committing a launch wave; do not use it for read-only directory browsing (postbuild_directories) or for clicking email verification links (postbuild_inbox).

postbuild_inboxA

Retrieve inbound directory verification emails and 6-digit OTP codes from a domain-bound <slug>@postbuild.dev inbox, and optionally follow allowlisted confirmation links. Requires a valid Launch Pass license (pb_live_...) whose verified domain owns inbox (when inbox is omitted, defaults to the licensed domain's inbox; mismatched domains fail with FORBIDDEN_INBOX); when auto_verify: false (default), the call is strictly read-only and wraps untrusted email text in <<<UNTRUSTED_CONTENT_DATA_ONLY>>> guards, whereas auto_verify: true sends SSRF-guarded HTTP GET requests across at most 2 ESP redirect hops to allowlisted directory confirmation paths. Use this tool after submitting directory forms to complete email/OTP verification; do not use it to generate submission links (postbuild_dispatch) or to inspect initial domain readiness (postbuild_scan).

postbuild_fixA

Scan url over HTTPS and write missing technical SEO and AI search readiness artifacts (robots.txt with OAI-SearchBot/ClaudeBot/PerplexityBot allow rules, sitemap.xml, llms.txt, og-card.png, .postbuild/PostbuildCheckoutGate.jsx, and 7 HTML product pages under .postbuild/pseo/) into cwd. url supplies the canonical hostname, title, and metadata embedded into the files written under cwd (public/ or repo root); requires a valid Launch Pass license (pb_live_...) for url's domain and is idempotent and non-destructive by default, preserving any existing user robots.txt/sitemap.xml/llms.txt files and reporting them in skippedFiles. Use this tool when remediating audit gaps in a local repository; do not use it for read-only site audits (postbuild_scan), in-memory HTML page previews (postbuild_pseo), or provisioning live Stripe Payment Links (postbuild_checkout).

postbuild_vault_syncA

Audit every URL in urls over HTTPS and write a consolidated Markdown readiness dashboard plus JSON telemetry cache into vault_path. When vault_path contains an .obsidian/ directory, writes _dashboards/Postbuild Launch.md and _meta/postbuild-telemetry.json for Obsidian VaultOS; otherwise writes LAUNCH_STATUS.md and .postbuild/telemetry.json at the root of vault_path (when urls is omitted, audits the domain bound to the active pb_live_... Launch Pass license; overwrites only those generated status/telemetry files and never alters user notes). Use this tool to persist multi-project launch telemetry to a repository or Obsidian vault; do not use it for a single-URL in-memory JSON audit (postbuild_scan) or to generate robots.txt/sitemap.xml/llms.txt (postbuild_fix).

Prompts

Interactive templates invoked by user choice

NameDescription
launch_readiness_auditRun a complete post-deploy technical SEO, AI search crawler, llms.txt, and checkout readiness audit on a live URL.

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A4.7/5.0

Scored across 8 tools

Disambiguation5/5

Each tool has a clearly distinct role across the launch workflow: audit, fix, pSEO preview, checkout provisioning, directory search, dispatch, inbox verification, and multi-project telemetry. Overlaps such as scan vs. vault_sync and pseo vs. fix are explicitly bounded by read-only vs. write behavior and single-URL vs. multi-URL scope.

Naming Consistency5/5

All tools follow a consistent `postbuild_` prefix with snake_case noun/verb identifiers. The convention is predictable across the entire set.

Tool Count5/5

Eight tools is well-scoped for a launch-readiness server. Each tool covers a meaningful phase of the workflow without excessive fragmentation.

Completeness5/5

The surface covers the full launch lifecycle: auditing, fixing SEO artifacts, generating pSEO pages, provisioning Stripe checkout, discovering directories, dispatching submissions, verifying inbox confirmations, and persisting telemetry. No obvious core operation is missing.

Maintenance

ActivityMaintained
ResponsivenessNo recent community issues