Skip to main content
Glama
Postbuild MCP

Postbuild MCP

Official
README.md
# Postbuild MCP Server (`git-paid`)

[![xdlabs-io/postbuild-mcp MCP server](https://glama.ai/mcp/servers/xdlabs-io/postbuild-mcp/badges/score.svg)](https://glama.ai/mcp/servers/xdlabs-io/postbuild-mcp)
[![npm version](https://img.shields.io/npm/v/git-paid.svg)](https://www.npmjs.com/package/git-paid)
[![Postbuild Launch Readiness](https://www.postbuild.dev/api/badge?url=www.postbuild.dev)](https://www.postbuild.dev/?scan=postbuild.dev)
[![License: MIT](https://img.shields.io/badge/License-MIT-blue.svg)](LICENSE)

Official Model Context Protocol (MCP) server for **[Postbuild](https://www.postbuild.dev)** (`git-paid` on npm).

Audits any deployed URL for technical SEO, AI search crawler rules (`OAI-SearchBot`, `ClaudeBot`, `PerplexityBot`), `llms.txt`, `sitemap.xml`, OpenGraph social cards, `SoftwareApplication` JSON-LD, and Stripe checkout reachability, and generates drop-in fix files.

---

## Quick Start

### Claude Code / Cursor / Windsurf / Claude Desktop

Add `postbuild` to your MCP client configuration (`claude_desktop_config.json` or `.cursor/mcp.json`):

```json
{
  "mcpServers": {
    "postbuild": {
      "command": "npx",
      "args": ["-y", "git-paid", "mcp"]
    }
  }
}
```

Or run the CLI directly from your terminal:

```bash
npx git-paid https://yourapp.com
```

---

## Available MCP Tools

| Tool | Description |
| :--- | :--- |
| `postbuild_scan` | Audits a live URL across technical SEO, OpenGraph cards, AI search crawler directives (`OAI-SearchBot`, `ClaudeBot`, `PerplexityBot`), `llms.txt`, `sitemap.xml`, JSON-LD schema, and Stripe checkout reachability. |
| `postbuild_fix` | Generates drop-in `robots.txt`, `llms.txt`, `sitemap.xml`, JSON-LD, and targeted HTML product pages for a local repository. |
| `postbuild_pseo` | Previews and generates targeted product/guide routes and structured metadata for a domain. |
| `postbuild_directories` | Queries and filters 85 launch directories and communities by category, domain rating (DR), and submission mode. |
| `postbuild_dispatch` | Prepares pre-filled directory launch kits and submission payloads with two-phase confirmation tokens. |
| `postbuild_inbox` | Reads verification emails and extracts 6-digit OTPs from an assigned `@postbuild.dev` launch inbox. |
| `postbuild_checkout` | Inspects or provisions self-serve Stripe checkout gates for a project. |
| `postbuild_vault_sync` | Syncs domain readiness scores and directory status to an Obsidian VaultOS dashboard. |

---

## Links

- **Web App & Free Live Scanner**: [https://www.postbuild.dev](https://www.postbuild.dev)
- **npm Package (`git-paid`)**: [https://www.npmjs.com/package/git-paid](https://www.npmjs.com/package/git-paid)
- **Built by**: [XD Labs](https://www.xdlabs.io)

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