About matchstick
Checks a site build: sitemaps, structured data, robots.txt and what crawlers see.
Configuration
Local server config is the same for every client. Copy it into your client’s MCP config file.
Tools
11Saved tool list · updated 5d ago
| Parameter | Type | Required | Description |
|---|---|---|---|
| dir | string | No | Build output folder, e.g. "dist". Default: "dir" in matchstick.config.json |
| live | boolean | No | Check the live site instead of a build: read its robots.txt and sitemaps and fetch its pages. For sites built elsewhere (Lovable, Webflow, Shopify, a CMS). Needs site. Makes real requests to it |
| site | string | No | Site URL, e.g. "https://example.com". Default: "site" in the config file |
| probe | boolean | No | Fetch the live site as each known crawler, to catch a CDN or WAF blocking one that robots.txt doesn't. Makes real requests to --site |
| rules | array | No | Only report these rules |
| preset | enum | No | Framework layout: "next" or "next-export"next | next-export |
| render | boolean | No | Also open pages in headless Chrome (needs playwright-core) to find content that needs JavaScript |
| maxItems | integer | No | Occurrences listed per finding (default 50); "total" always has the full count |
| fetchBase | string | No | Fetch pages that have no file from this running server, e.g. "http://localhost:3000" |
| gscExport | string | No | Path to a Search Console export of those URLs (the Table.csv in its download), instead of notIndexed |
| pageLimit | integer | No | Open at most this many pages (default with live: 200) |
| notIndexed | array | No | URLs Search Console reports as not indexed ("Crawled - currently not indexed" and the like): the result triages each one |
| renderLimit | integer | No | Render at most this many pages (default 100) |
Details
The maintainer has not added details yet. Check the README in the repository.
Comments
Markdown supported
New to MCP?
From what the protocol is to installing your first server, these answers cover most first questions.
An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.