Connect ParcelOps in four steps.

Your dashboard gives you the MCP URL. The steps below show where to put it and how to run your first property request.

Your first request.

1
Create your MCP connection
Create a ParcelOps account and open the MCP workspace.
2
Add the URL to your client
Use OAuth when your client supports it. Otherwise, copy the private URL from your dashboard. You can turn that URL off any time.
3
Choose a property source
Search by market or by the property question you need to answer.
4
Run your first request
ParcelOps checks access before it queries the selected source. The result includes its source details.

What comes back

The fields depend on the source you choose. Every result includes the source, request status, and coverage notes.

Endpoint: /api/mcp
Source: Chosen after coverage and access checks
Request: Checked before ParcelOps sends it
Result: Includes source and coverage notes

Add your MCP URL to your client.

Copy the signed-in URL from your dashboard. Clients with OAuth use the shared endpoint. Other clients use a private URL you can turn off any time.

Open CLI setup examples

OAuth endpoint

https://parcelops.ai/api/mcp

// Find the source, inspect its contract, then call it
parcelops_discover({ query: "parcel at a point" })
parcelops_search_tools({ query: "find parcel at a point in Texas" })
parcelops_describe_tool({ name: "texas-parcels.identifyParcel" })
parcelops_callTool({ tool: "texas-parcels.identifyParcel", args: { latitude: 30.2672, longitude: -97.7431 } })

Check coverage before you rely on a field.

See what each source covers

global-geocoderWorldwide addresses and reverse geocodingNo credentials

osm-real-estateWorldwide buildings, addresses, and land useNo credentials

global-markets249 ISO markets plus World Bank contextNo credentials

property-dossierProperty research report with parcel and valuation fields, plus environmental, civic, crime, school, and disclosure contextNo credentials

census-geocoderUS address matching and Census geography identifiersNo credentials

census-acsUS housing estimates with published margins of errorFree Census API key

epa-echoUS regulated facilities, compliance, inspections, and enforcementNo credentials

nasa-powerWorldwide gridded climate context for a property pointNo credentials

usgs-earthquakeWorldwide published earthquake history and recent eventsNo credentials

fws-critical-habitatUS final and proposed federal critical-habitat polygonsNo credentials

us-parcels3,235 US counties checked · 162 verified APIs and layersNo credentials

texas-parcelsTxGIO StratMap 2025 statewide parcelsNo credentials

netherlands-cadastreNationwide Kadaster BRK parcels via PDOKNo credentials

floodzone · wetlands · soilsUS site and hazard contextNo credentials

postgresAuthorized customer property and portfolio dataRead-only credentials

A source marked "Live" has been tested end to end. Coverage still varies by place and by field. Check what a source covers before you rely on title, owner, value, or boundary data.

See what ParcelOps checks before each request.

Every request is checked before it leaves. ParcelOps confirms who is asking, which sources they can reach, the arguments sent, and where the request goes.

OAuth, or a private URL you can turn off
Source permissions for users, organizations, and partners
Connector credentials encrypted and never shown to the model
Checks that limit what each connector can send
Usage limits, caching, response scanning, and audit trails
Only the tools needed for the request are loaded

Connect ParcelOps in four steps.

Your first request.

Create your MCP connection

Add the URL to your client

Choose a property source

Run your first request

What comes back

Add your MCP URL to your client.

Check coverage before you rely on a field.

See what ParcelOps checks before each request.

Choose your next step.

CLI

Partner admin API

SDKs