Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
作者による説明(英語の原文)
Find checked US roofers, siding and gutter contractors by city. Read-only, no login.
この3つを1つのスコアにまとめることはしません。意見、測定、人気はそれぞれ別のものだからです。
このサーバーのやさしい解説はまだ書いていません。以下はレジストリから読み取った事実です。
使っているAIアプリを選んで、設定をコピーしてください。
必要なもの
どのアプリを使っていますか?
上でアプリを選んでください。選んだアプリを覚えておくので、次からはボタンに「…にインストール」と表示されます。
ウェブ、デスクトップ、モバイルのClaudeで使えます:
https://mcp.theroofinglist.com/mcpターミナルでこれを実行します
claude mcp add --transport http the-roofing-list https://mcp.theroofinglist.com/mcpプロジェクトの .cursor/mcp.json、または ~/.cursor/mcp.json に貼り付けます
{
"mcpServers": {
"the-roofing-list": {
"url": "https://mcp.theroofinglist.com/mcp"
}
}
}ブラウザがアプリを開いてよいか確認し、そのあとアプリが設定を表示して確認を求めます。キーの値は空欄のままなので、自分で入力してください。
プロジェクトの .vscode/mcp.json に貼り付けます
{
"servers": {
"the-roofing-list": {
"type": "http",
"url": "https://mcp.theroofinglist.com/mcp"
}
}
}ブラウザがアプリを開いてよいか確認し、そのあとアプリが設定を表示して確認を求めます。キーの値は空欄のままなので、自分で入力してください。
ChatGPTがつなげるのは、インターネット上のサーバーだけです:
https://mcp.theroofinglist.com/mcpメニューの名前は、プランや時期によって少し違うことがあります。
選んだアプリは、この端末のCookieに保存されます。アカウントは不要です。
この設定は、作者のレジストリ登録情報から作成しています。READMEと違う場合は、READMEに従ってください。
このサーバーのツール一覧はまだ読み取っていません。エンドポイントは順番にチェックしています。
誰でも見られる情報をチェックしており、コードは読んでいません。当てはまらない項目は数に入れていません。 · 2026年11月7日にチェック
レジストリ名は、リポジトリを所有するGitHubアカウント redpath1 で確認済みです
このリポジトリはまだGitHubから読み取っていません
このリポジトリはまだGitHubから読み取っていません
まだチェックしていません。エンドポイントは順番にチェックしています
まだチェックしていません。エンドポイントは順番にチェックしています
まだチェックしていません。エンドポイントをチェックするときにツール一覧を読み取ります
レジストリでこのカテゴリにある有効なすべてのサーバーと比較しています。スターは、公開者がリポジトリの所有者である場合だけ数えます。
当てはまる基本チェック1項目のうち1項目に合格しました。コードは読んでいません。キーやトークンを追加する前に、サーバーがどんなアクセスを求めているかを確認し、必要な権限だけを持つキーを使ってください。
レジストリには必須のキーは載っていません。ただし、最初に使うときにサインインを求めるサーバーもあります。
作者のクラウドで動きます。インストール不要でインターネット経由でつながりますが、送った内容は作者のサーバーを通ります。
GitHubリポジトリの最終更新は–、最新バージョン(0.1.1)がレジストリに届いたのは17 日前です。
Claude Desktop、Claude Code、Cursor、VS CodeなどのMCP対応アプリで使えます。URLでつながるので、リモートMCPサーバーに対応したアプリ(開発者モードのChatGPTなど)でも使えます。
同じカテゴリには:Spec Driven Development, Remote Desktop Commander, AvaHR
同じカテゴリで、ほかの作者が作ったサーバー。スターの多い順。
カードの見方:★ GitHubスターi3つの柱:レビュー · チェック · 利用状況i更新=最新バージョンをレジストリに公開した日i
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.
Read hiring data and create inactive assessment and questionnaire drafts for human review.
作者のリポジトリから書かれたとおりにコピーしたものです。PopNx MCPは内容を確認・推奨していません。HTML、画像、スクリプトは取り除いています。リンクはこのサイトの外へ移動します。
A public, read-only MCP server for The Roofing List. AI assistants use it to find checked US roofers, siding and gutter contractors by city.
https://mcp.theroofinglist.com/mcp (Streamable HTTP). No login, no API key.Claude Code:
claude mcp add --transport http the-roofing-list https://mcp.theroofinglist.com/mcp
Claude Desktop: add this to claude_desktop_config.json. It uses mcp-remote, because the config file starts local servers only. Or add the URL as a custom connector in Settings > Connectors.
{
"mcpServers": { "the-roofing-list": { "command": "npx", "args": ["-y", "mcp-remote", "https://mcp.theroofinglist.com/mcp"] } } }
Any other MCP client: connect to https://mcp.theroofinglist.com/mcp with Streamable HTTP.
Connect from any agent: .mcp.json at the root of this repo holds the server entry. Claude Code reads it when you open this repo. For any other client, copy the entry into that client's MCP config.
limit.The rules live in src/present.ts. The tests in test/tools.test.ts prove them against a deliberately leaky stub.
theroofinglist-mcpPOST /mcp (Streamable HTTP). No login. GET / sends a 301 to https://theroofinglist.com/mcp/.createMcpHandler from agents/mcp/server builds a new McpServer for each request. No Durable Objects. Cloudflare marks McpAgent as the older path for new stateless servers.The same Worker also serves a small REST API, for RapidAPI and for people who do not use MCP. It is read-only, free and needs no key. It calls the same lookups as the MCP tools (src/lookup.ts), so both return the same records.
| Route | Returns |
|---|---|
GET /v1/contractors?trade=&city=&state=&limit= | { "contractors": Contractor[] }. Same inputs and limits as search_contractors. |
GET /v1/contractors/{id} | Contractor, or 404 for a closed, unlisted or unknown id |
GET /openapi.json | The OpenAPI 3.1 document (openapi.json in this folder) |
curl 'https://mcp.theroofinglist.com/v1/contractors?trade=roofing&city=Austin&state=TX&limit=5'
curl 'https://mcp.theroofinglist.com/v1/contractors/101'
{ "error": "..." }: 400 bad input (same messages as the tools), 404, 405 for any method but GET, 429 over the rate limit (with Retry-After: 60), 503 when the web Worker fails.access-control-allow-origin: *. OPTIONS answers the CORS preflight.public, max-age=300 on 200, 400, 404 and 405. no-store on 429 and 503, so no cache keeps a short-lived error. /openapi.json caches for 1 hour.openapi.json is the one source for the document. src/openapi.ts imports it. When you raise SERVER_VERSION, raise info.version too; a test checks that they match.All RapidAPI calls come from RapidAPI's servers. A per-IP limit would count all RapidAPI users as one caller. So:
pnpm exec wrangler secret put RAPIDAPI_PROXY_SECRET. It is optional. Locally, leave it empty in .dev.vars.x-rapidapi-proxy-secret, the key is rapidapi: . Without the user header, the key falls back to the IP.x-rapidapi-user. The compare is constant-time.rest: or mcp:. Each gets 60 calls a minute. /openapi.json and OPTIONS do not count.| Tool | Input | Returns |
|---|---|---|
search_contractors | trade (roofing, siding, gutters), city, state (code or name), limit (1–25, default 10) | { contractors: Contractor[] } |
get_contractor | id (integer from search) | Contractor, or an error for a closed, unlisted or unknown id |
Contractor: id, name, trades, city, state, phone, profileUrl, claimed, website (claimed only), rating ({ value, count }, published reviews on our site only; absent when there are none).
See "The data rules" above for what may leave this Worker.
You need Node 22+ (Wrangler 4) and pnpm. You do not need a Cloudflare login.
pnpm install
pnpm dev # MCP Worker on :8787 plus the stub web Worker pnpm smoke # in a second shell: official MCP client lists and calls both tools pnpm smoke --burst # also checks the rate limit (uses up this minute's budget) pnpm test pnpm typecheck
pnpm dev copies .dev.vars.example to .dev.vars the first time. Both hold a fake local token.
The real data route lives in the private web app (theroofinglist-web). src/contract.ts describes it, and stub/ copies its shape with fake rows. If you have the web app, run it on port 8790 and point this Worker at it over the WEB service binding:
pnpm exec wrangler dev -c wrangler.jsonc --local --port 8792
MCP_URL=http://localhost:8792/mcp pnpm smoke
Both Workers must hold the same INTERNAL_API_TOKEN in .dev.vars.
pnpm smoke takes its ids from a search for roofers in Austin, Texas, so it runs on the stub and on real data. SMOKE_CITY and SMOKE_STATE change the search. SMOKE_CLOSED_ID names an id that must not come back: SMOKE_CLOSED_ID=103 pnpm smoke checks the stub's closed row.
Inspector: npx @modelcontextprotocol/inspector and connect to http://localhost:8787/mcp with Streamable HTTP.
The MCP Worker calls theroofinglist-web over a service binding (WEB). The web Worker reads through Payload, the same as the public pages. In local dev, stub/ runs under the name theroofinglist-web and serves fake rows. The stub is loose on purpose: it sends closed rows, a free website and Google fields, so the tests prove this Worker filters them.
The private web app serves this route. src/contract.ts defines it. The path sits outside /api, so Payload's /api/[...slug] catch-all does not take it.
GET /internal/mcp/contractors?trade=<slug>&state=<USPS>&city=<city-slug>&limit=<1..25>
200 { "contractors": Contractor[] }
GET /internal/mcp/contractors/ 200 { "contractor": Contractor } 404 { "error": "not_found" } // also for closed or unlisted
Header on every request: x-internal-token: 401 { "error": "unauthorized" } // missing or wrong token
Contractor = { id: number, // Businesses.id name: string, trades: string[], // Trades slugs, TRADE_PATHS order city: string, // city name, e.g. "Austin" state: string, // USPS code, e.g. "TX" phone: string | null, // E.164 tier: "free" | "claimed", website: string | null, // as stored; the MCP Worker drops it for free status: "active" | "closed", listed: boolean, path: string, // profilePath(), e.g. "/roofers/texas/austin/lone-star-roofing" rating: { value: number, count: number } | null // getRatings(): published reviews only }
RATE_LIMITER is a Workers rate limiting binding: 60 requests per IP per 60 seconds, keyed on cf-connecting-ip. Over the limit, /mcp returns 429 with Retry-After: 60 and a JSON-RPC error. For RapidAPI traffic the key is the RapidAPI user; see "RapidAPI and the rate limit" above. The binding counts per Cloudflare location and is eventually consistent, so it stops abuse, not exact overuse.
Live at https://mcp.theroofinglist.com/mcp (custom domain) since 4 Oct 2026. Deploy with pnpm exec wrangler deploy.
INTERNAL_API_TOKEN is a secret on both Workers, with the same value. To rotate it, put a new value on both.ALLOWED_HOSTNAMES in wrangler.jsonc lists the custom domain, the workers.dev name and the local names.theroofinglist-web first when the contract changes. Never deploy stub/.MCP_URL=https://mcp.theroofinglist.com/mcp pnpm smoke./internal/mcp/contractors/ (with a slash). A call without the slash gets a 308, which the service binding follows. One extra hop; it works.Listed as io.github.redpath1/the-roofing-list since 5 Oct 2026. server.json in this folder is the entry. Check it:
curl -s 'https://registry.modelcontextprotocol.io/v0.1/servers?search=redpath1'
The name uses the GitHub namespace. The domain namespace (com.theroofinglist/...) needs a TXT record on the apex or a /.well-known/mcp-registry-auth file on theroofinglist.com. The Wrangler login cannot edit DNS, and the file means a web deploy, so we chose GitHub. server.json names this repository in its repository field from version 0.1.1. The registry shows that field only after 0.1.1 is published (see below). Publish it after the repository is public.
The registry keeps every version for good. You cannot change or reuse a version string.
brew install mcp-publisher (1.8.1 or later).server.json, raise version (semver, e.g. 0.1.1). Keep it the same as SERVER_VERSION in src/server.ts.mcp-publisher validate server.json.redpath1, who owns the namespace. Run mcp-publisher login github and enter the device code. Or reuse the gh login, without showing the token: gh auth token | xargs -I{} mcp-publisher login github --token={}.mcp-publisher publish server.json.curl above. The new version shows "isLatest": true.The directory page on theroofinglist.com already marks this server as in the official registry. A new version does not change that.
https://github.com/redpath1/the-roofing-list-mcp is the published copy of the mcp/ folder in the private monorepo of The Roofing List. Develop in the monorepo. The public repo has its own short history, so do not use git subtree push: that would push the monorepo's commit history, with its author emails, to the public repo. After a change to mcp/ merges to main, copy the files instead:
git clone https://github.com/redpath1/the-roofing-list-mcp /tmp/trl-mcp
rsync -a --delete --exclude .git --exclude node_modules --exclude .wrangler --exclude .dev.vars mcp/ /tmp/trl-mcp/ cd /tmp/trl-mcp && git add -A && git commit -m " " && git push
Commit as Keith Evans <272994924+redpath1@users.noreply.github.com>. No personal email goes into the public history.
Issues are open. We review pull requests when there is time. We make no roadmap promises.
MIT. See LICENSE.