Unofficial Thumbtack MCP — search local service pros, read profiles, ratings and reviews
Unofficial Thumbtack MCP server — search local service pros, and read their profiles, ratings, reviews and credentials.
Read-only and anonymous. Thumbtack's consumer pages and its GraphQL endpoint answer without a login, so this server needs no account, no API key and no browser extension. It also cannot write: Thumbtack's write paths sit behind a reCAPTCHA-gated login that no server-side client can pass.
Thumbtack has no public consumer API. This server reads its server-rendered pages and anonymous GraphQL endpoint, and may break or violate their ToS. Developed and maintained by AI (Claude). Use at your own discretion.
// .mcp.json
{ "mcpServers": { "thumbtack": { "command": "npx", "args": ["-y", "@chrischall/thumbtack-mcp"] } } }
No configuration — there are no environment variables.
| Tool | What it does |
|---|---|
thumbtack_search_pros | Search pros by trade + US ZIP. Returns up to 10 with rating, review count, lifetime hires, mean response time, profile URL. |
thumbtack_resolve_service | Canonicalise a loose service name (plumbing → plumbers) by asking Thumbtack. |
thumbtack_get_pro | A pro's profile: name, description, location, aggregate rating, credentials, section inventory. |
thumbtack_get_pro_reviews | Reviews on a pro's profile — stars, author, date, text. |
thumbtack_graphql | Escape hatch for arbitrary read-only GraphQL. Mutations refused. |
thumbtack_healthcheck | Probes the page and GraphQL surfaces separately and reports the response shape still matches. |
Every read tool takes view: "compact" | "full", and compact is the
default. On thumbtack_search_pros that is a hand-written field projection;
on thumbtack_get_pro, thumbtack_get_pro_reviews and thumbtack_graphql it
strips image URLs, which needs no knowledge of the payload's shape. Pass
view: "full" for the untouched upstream records — they are large and mostly
tracking metadata, which is why the slim shape is what you get without asking.
thumbtack_resolve_service and thumbtack_healthcheck take no view: both
already answer with a handful of scalar fields, and a rung that cannot change
anything is worse than no parameter.
skills/thumbtack/ is a self-contained skill covering the same surface with
plain curl + jq — no server process. Use it for one-shot lookups and
scripts.
Three verified surfaces, all pinned in docs/THUMBTACK-API.md:
__NEXT_DATA__.window.__APOLLO_STATE__ (a bare JS assignment, so it
needs balanced-brace extraction) plus schema.org JSON-LD.app.thumbtack.com/graphql) — accepts ad-hoc anonymous
queries; introspection is disabled.Two things that bite anyone reading these pages:
@type is the trade-specific subtype, not LocalBusiness — a
plumber's node is "@type":"Plumber". Match by shape, not by type name.errors[] body. Status alone is never
sufficient.developers.thumbtack.com) — real and
documented, but gated behind partner credentials ("Request Access"). It is a
seller surface, not a consumer one.npm install
npm run build
npm test # unit + server-boot smoke tests
npm run test:coverage
Coverage is enforced at 100%.
MIT
Source-derived launch command. Check the maintainer’s required arguments and credentials before running:
npx -y @chrischall/thumbtack-mcpMerge this template into ~/Library/Application Support/Claude/claude_desktop_config.json. Keep existing servers. Add any arguments, credentials, and permissions required by the maintainer; this template has not been install-tested.
{
"mcpServers": {
"io-github-chrischall-thumbtack-mcp": {
"command": "npx",
"args": [
"-y",
"@chrischall/thumbtack-mcp"
]
}
}
}Restart Claude Desktop completely for changes to take effect. Confirm the server appears connected in the client’s tool list, then try a read-only example from its documentation.
Claude Desktop setup reference@chrischall/thumbtack-mcpnpmio.github.chrischall/thumbtack-mcp works with any MCP-compatible client. Copy the config snippet from the Configuration section above and add it to the file shown for your client, then restart the application.
~/Library/Application Support/Claude/claude_desktop_config.jsonRestart Claude Desktop completely for changes to take effect.~/.cursor/mcp.jsonRestart Cursor for changes to take effect..vscode/mcp.jsonReload VS Code window for changes to take effect.~/.codeium/windsurf/mcp_config.jsonRestart Windsurf for changes to take effect..mcp.jsonSave at the project root, then start Claude Code in that project and review the MCP server approval prompt. Keep real credentials out of shared files.