places_by_domain
Pack: overture-places · Connect: https://pipeworx.io/mcp (see Connect below for a single-pack URL)
No MCP client? Call it directly: GET https://gateway.pipeworx.io/v1/tools/places_by_domain for the schema, then POST the same URL with its arguments for the data.
List every physical location whose website is on a company domain — the store / office / branch footprint of a business — in the United States and the United Kingdom (Overture Maps places). Give a domain like “starbucks.com” or a full URL; subdomains and paths fold to the registrable domain. Returns the total count, counts by country and by state/region, and the locations with addresses, phones and confidence. Answers “how many locations does acme.com have and where”.
Parameters
| Name | Type | Required | Description |
|---|---|---|---|
domain | string | yes | Company domain or website URL, e.g. “starbucks.com”, “https://www.tesco.com/stores”. |
country | string | no | Optional: only locations in this country (“US” or “GB”). |
region | string | no | Optional: only locations in this state/region, e.g. “TX”. |
limit | number | no | Max locations returned (1–1000, default 100). Counts always cover all matches. |
Example call
Arguments
{
"domain": "starbucks.com",
"limit": 5
}
curl
curl -X POST https://gateway.pipeworx.io/overture-places/mcp \
-H 'Content-Type: application/json' \
-d '{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"places_by_domain","arguments":{"domain":"starbucks.com","limit":5}}}'
TypeScript (@pipeworx/sdk)
import { Pipeworx } from '@pipeworx/sdk';
const pipeworx = new Pipeworx();
const result = await pipeworx.call('places_by_domain', {
"domain": "starbucks.com",
"limit": 5
});
Connect
Add this to your MCP client config — every tool in the catalog, including this one — or use one-click install buttons:
{
"mcpServers": {
"pipeworx": {
"url": "https://pipeworx.io/mcp"
}
}
}
Connect to just the overture-places pack
{
"mcpServers": {
"overture-places": {
"url": "https://gateway.pipeworx.io/overture-places/mcp"
}
}
}
See Getting Started for client-specific install steps.