Postbuild MCP
OfficialRelated Servers
Alternatives to Postbuild MCP
- AlicenseNot gradedqualityBmaintenanceEnables AI coding assistants to audit a site's technical SEO and AI-search readiness — including localhost dev servers — and retrieve rule explanations, fix templates, and generated llms.txt files so the assistant can edit the repo to resolve what it finds.6 npmMIT
Related Servers
- AlicenseNot gradedqualityBmaintenanceEnables users to audit websites and online stores for generative and answer-engine readiness, generate deployable llms.txt and llms-full.txt files, JSON-LD schema, and AI crawler rules, analyze robots access for AI bots, and extract clean page content for LLM use.MIT
- AlicenseNot gradedqualityCmaintenanceEnables AI assistants to run read-only technical SEO and AI-search-readiness audits on any URL via GET/HEAD requests. Checks on-page elements like titles, meta descriptions, headings, canonical and Open Graph tags, JSON-LD validity, alt text and link health, plus robots.txt, sitemaps and llms.txt for crawler access.7 npmMIT
- AlicenseNot gradedqualityCmaintenanceEnables auditing websites for AI/LLM readiness and generating fixes such as robots.txt rules, llms.txt, JSON-LD schema, and meta tags, plus checking brand and domain citations through natural language.1MIT
- AlicenseAqualityCmaintenanceEnables AI agents to check whether a public website is crawlable, understandable, and ready for AI search workflows through local-only audits of robots.txt, sitemaps, metadata, and llms.txt.373 npm2MIT
- AlicenseAqualityCmaintenanceAudit a site for AI readiness: AI-crawler access, schema, FAQ and content structure. Generates the fixes.684 npmMIT
- AlicenseNot gradedqualityCmaintenanceGenerates a complete suite of AI readiness files (llms.txt, ai.txt, schema, RAG indexes) for any website to optimize representation in ChatGPT, Claude, Gemini, and Perplexity.25 npm3MIT
TDQS
Scored across 8 tools
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.
All tools follow a consistent `postbuild_` prefix with snake_case noun/verb identifiers. The convention is predictable across the entire set.
Eight tools is well-scoped for a launch-readiness server. Each tool covers a meaningful phase of the workflow without excessive fragmentation.
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.