Texas Estate Records is available as a Model Context Protocol (MCP) server through the RapidAPI Hub gateway. RapidAPI turns every endpoint of the API into a tool an AI agent can call, and serves them from a single host at mcp.rapidapi.com. Your RapidAPI subscription governs access, so the same free browsing and metered parsing rules apply (see Pricing).
Connect
Add the block below to your MCP client config. It uses mcp-remote to bridge your client to the RapidAPI gateway and authenticates with your own RapidAPI key. Set your key and the snippet becomes ready to paste.
{
"mcpServers": {
"texas-estate-records": {
"command": "npx",
"args": [
"mcp-remote",
"https://mcp.rapidapi.com",
"--header",
"x-api-host: texas-estate-records.p.rapidapi.com",
"--header",
"x-api-key: YOUR_RAPIDAPI_KEY"
]
}
}
}Copying now drops YOUR_RAPIDAPI_KEY into the config. Set your key above to get a ready-to-paste version.
Don't have a key yet? Subscribe to any plan (including the free one) on the RapidAPI listing, then copy your key from the listing's Endpoints tab.
Where the config goes
- Claude Desktop- Settings → Developer → Edit Config, or edit
claude_desktop_config.jsondirectly, then restart Claude. - Cursor- Settings → MCP → Add new server, or add it to
.cursor/mcp.json. - Other clients - any client that supports custom MCP servers can run the same
npx mcp-remotecommand.
The bridge needs Node.js on your machine (it runs npx). No other install is required.
Tools exposed
Each API endpoint shows up as a callable tool:
listRecords- search and filter the index by county, document type, and recorded-date range. Free.getRecord- fetch the summary for a single record by county and document number. Free.getRecordDetails- run the AI parse over the original images and return structured fields. Metered.listCounties- current coverage and record counts. Free.listDocumentTypes- the document categories we track. Free.
So you can ask things like “find affidavits of heirship recorded in Tarrant County last month” and the agent will call listRecords for you, then getRecordDetails on the ones you want parsed.
Billing
MCP calls bill exactly like REST calls: searching and listing are free on every plan, and only getRecordDetails counts against your quota. Because the gateway meters by your key header, every call bills your own RapidAPI subscription. Usage is subject to our Acceptable Use Policy.
About your key
Your API key is never stored on our servers.The config above is assembled entirely in your browser, your key is kept only in this browser's local storage, and your MCP client sends it directly to RapidAPI to authenticate. It never passes through texasestaterecords.com.