Skip to main content
Glama
Postbuild MCP

Postbuild MCP

Official
by xdlabs-io

Related Servers

Alternatives to Postbuild MCP

  • A
    license
    Not graded
    quality
    B
    maintenance
    Enables 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 npm
    MIT

Related Servers

  • A
    license
    Not graded
    quality
    B
    maintenance
    Enables 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
  • A
    license
    Not graded
    quality
    C
    maintenance
    Enables 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 npm
    MIT
  • A
    license
    Not graded
    quality
    C
    maintenance
    Enables 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.
    1
    MIT
  • A
    license
    A
    quality
    C
    maintenance
    Enables 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.
    3
    73 npm
    2
    MIT
  • A
    license
    Not graded
    quality
    C
    maintenance
    Generates 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 npm
    3
    MIT

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