HasData Yellow Pages

Yellow Pages MCP Server

A hosted Yellow Pages MCP server that gives Claude, Cursor, Windsurf and any other MCP client two read-only Yellow Pages tools. Search local businesses by keyword and location, then read one listing in full with its phone, hours, services and photos, both as structured JSON, with nothing to host.

It reads public Yellow Pages listings that a signed-out visitor can see, on yellowpages.com and yellowpages.ca.

1,000 free credits every month, no card required, which is 100 Yellow Pages calls at the 10-credit rate.

https://mcp.hasdata.com/mcp?apis=yellowpages

• Prompts and resources

Contents

• What you need
• Quick start
• Example prompts
• Tools
• Errors and failure paths
• Pricing, free tier and limits
• Tool selection
• How it compares
• FAQ
• HasData links
• Development
• Contributing
• License

What you need

An MCP client and a HasData API key from the dashboard, free to create with no card, and the free tier covers about 100 calls a month at the 10-credit rate. This is a remote server, so the simplest path is a URL and an x-api-key header, with no container to run. A client that only speaks stdio reaches it through a thin launcher, published as @hasdata/yellowpages-mcp on npm and hasdata-yellowpages-mcp on PyPI, shown below.

Quick start

The server URL is the same for every client. We run it hands-on in Claude Code and Claude Desktop. The other blocks follow each client's own documented format for a remote server.

Clients with OAuth support can add the same URL as a connector and sign in without putting a key in a config file.

Claude Code

claude mcp add --transport http yellowpages "https://mcp.hasdata.com/mcp?apis=yellowpages" \

--header "x-api-key: HASDATA_API_KEY"

Claude Desktop

Settings, then Connectors, then Add custom connector, then paste https://mcp.hasdata.com/mcp?apis=yellowpages and sign in.

For the config-file route, Claude Desktop loads only local (stdio) servers, so it reaches a remote server through a stdio launcher. The @hasdata/yellowpages-mcp package is that launcher, and it reads the key from the environment. Add this to claude_desktop_config.json:

{

"mcpServers": { "yellowpages": { "command": "npx", "args": ["-y", "@hasdata/yellowpages-mcp"], "env": { "HASDATA_API_KEY": "YOUR_KEY" } } } }

For Python instead of Node, swap the launcher for the PyPI package, which uvx runs without a manual install:

{

"mcpServers": { "yellowpages": { "command": "uvx", "args": ["hasdata-yellowpages-mcp"], "env": { "HASDATA_API_KEY": "YOUR_KEY" } } } }

Cursor

~/.cursor/mcp.json for every project, or .cursor/mcp.json for one:

{

"mcpServers": { "yellowpages": { "url": "https://mcp.hasdata.com/mcp?apis=yellowpages", "headers": { "x-api-key": "HASDATA_API_KEY" } } } }

Windsurf

~/.codeium/windsurf/mcp_config.json. Windsurf calls the field serverUrl, not url:

{

"mcpServers": { "yellowpages": { "serverUrl": "https://mcp.hasdata.com/mcp?apis=yellowpages", "headers": { "x-api-key": "HASDATA_API_KEY" } } } }

VS Code

.vscode/mcp.json in the workspace:

{

"servers": { "yellowpages": { "type": "http", "url": "https://mcp.hasdata.com/mcp?apis=yellowpages", "headers": { "x-api-key": "HASDATA_API_KEY" } } } }

Example prompts

Each of these lands on one tool, or on two in sequence when the second needs the URL the first returns.

• Find plumbers in Austin, TX and rank them by rating against review count.
• List every HVAC contractor in this zipcode with a phone number and hours.
• Which of these businesses have been trading for more than 20 years?
• Read this Yellow Pages listing and tell me which brands they service.
• Pull page 2 and 3 of roofers in Austin and merge them into one list.
• Sort dentists in this city by average rating rather than by relevance.

A prompt that names a niche and a city goes to the search tool. Reading services, brands and payment methods takes a second call per business, so a prospect list wants the search tool and an enrichment pass wants the place tool.

Tools

Two tools, 10 credits per successful call.

Get Yellow Pages search results

hasdata_yellowpages_search_getSearchResults

A page of businesses for a keyword in a place, 30 to a page.

Returns searchInformation with the echoed query and totalResults, an organicResults array, and pagination with currentPage, totalPages, perPage, nextPageUrl and otherPageUrls.

Almost every field on a result is optional, because Yellow Pages shows what each business paid for or filled in. Across the 30 results in the sample, title, phone, url, categories, country and position arrived on all of them, address on 22, rating and reviews on 11, and contactUs on 5. Read defensively rather than assuming a shape.

{

"position": 2, "title": "Clarke Kent Plumbing", "url": "https://www.yellowpages.com/austin-tx/mip/clarke-kent-plumbing-10674347?lid=1002194068759", "phone": "(512) 766-0970", "address": "1408 W Ben White Blvd", "city": "Austin", "region": "TX", "zipcode": "78704", "country": "US", "website": "http://www.clarkekentplumbing.com", "directions": "https://www.yellowpages.com/listings/1002194068759/directions", "categories": ["Plumbers", "Plumbing-Drain & Sewer Cleaning"], "rating": 2.87, "reviews": 15, "workingHours": ["Mo-Fr 09:00-17:00"], "openState": "open now", "badges": ["40 Years in Business", "1 Year with Yellow Pages"] }

Get Yellow Pages place details

hasdata_yellowpages_place_getPlaceDetails

One listing in full, by its Yellow Pages URL.

Returns four blocks rather than one flat object.

overview repeats the name, location, phone, hours, badges and website, and adds paymentAccepted and a breadcrumbs array showing where the listing sits in the Yellow Pages taxonomy. ratings holds the star rating. details holds the long-form copy the business wrote. images is an array of photo URLs.

The details block is where the enrichment value sits, and it arrives as comma-joined text rather than as arrays. generalInfo is the business description, servicesProducts the service list, brands the brands they carry, paymentMethod the payment types and categories the full category list as one string.

{

"overview": { "title": "ARS Rescue Rooter", "phone": "(833) 947-9225", "city": "Austin", "region": "TX", "zipcode": "78754", "workingHours": ["Mo-Su"], "openState": "Open 24 hours", "paymentAccepted": "visa, amex, master card", "badges": ["1 Year with Yellow Pages"], "breadcrumbs": ["TX", "Austin", "Building Contractors", "Plumbers"] }, "ratings": { "rating": 3.5 }, "details": { "generalInfo": "ARS/Rescue Rooter has a proven track record of providing reliable, long-lasting repair services...", "servicesProducts": "Air Conditioner Repair and Replacement, Air Duct Repair and Replacement, Air Filter Installation...", "brands": "Goodman, Mitsubishi, Bosch, Diakin, Bradford White, April Aire Indoor Air Quality", "paymentMethod": "visa, amex, master card" }, "images": ["https://i4.ypcdn.com/blob/ce73451958465ab47dd7be41922973a98bc847af_640.jpg"] }

Prompts and resources

The server exposes 2 resources, one per parameter whose accepted values are a fixed list. Reading one is cheaper than learning the vocabulary from a rejected call, and it costs no credits. Each URI is hasdata://yellowpages/ .

The list is served without an API key, so a client can read it before a user has signed up.

Errors and failure paths

Plan for these rather than assuming a happy path.

For a review count, read the search result rather than the place detail. On the search tool, rating and reviews are what they look like, such as 2.87 and 15. On the place tool, ratings.reviews comes back equal to ratings.rating on every listing we checked, so it carries no count. Take the number from the search result and enrich from there.

`ratings` can be absent from a place response entirely. One of the four listings we pulled had no block at all rather than an empty one.

`details` fields are comma-joined strings, and `categories` changes type between the tools. In a search result categories is an array. In details it is one string. Split on the comma if you need a list, and expect