Bright Stats for Claude, ChatGPT, and Codex: The MCP Connection We Are Building
A planned connection for asking your AI assistant about local market data, with exact figures, filters, sources, and reporting dates. Preparation prompts available now.
Ryan Rockwood · 3 min read

On this page
Back to the Bright Stats guide
Coming soon. The Virtual Results Bright Stats MCP server, its sign-in flow, and assistant-specific installation instructions are not available yet. This page explains the intended connection and gives you prompts for preparing source material today.
Ask about the market without reading a chart by eye
The goal is to let a compatible assistant retrieve the same market evidence that supports your website report. Ask, “What changed for Woodbridge sellers compared with last October?” and receive the figures, filters, source references, and the reporting period before an explanation.
MCP provides a standard way for an AI application to access tools and resources. It does not itself grant Bright access or permission to edit your site. Claude, ChatGPT, and Codex would each need their supported connection path tested; a single screenshot from one assistant would not establish all three.
What the intended tools would return
- Available markets: the geographies and report selections the connected account is authorized to use.
- Market snapshot: the latest available complete reporting period, with actual units and property-type filters.
- Historical comparison: comparable periods and the figures behind any change calculation.
- Source context: metric definitions, source references, retrieval time and unavailable data.
- Report preparation: a draft that uses those facts without guessing unsupported values.
These are planned capabilities, not a list of tools already exposed by a running endpoint. We will publish the actual server address and supported authentication instructions here when they work.
How access should work
- Connect through the supported assistant interface using the published Virtual Results server address.
- Sign in through the intended authorization flow and review the requested access.
- Confirm which market reports the connection can read.
- Ask for one known market and reporting period; compare the response with the source chart.
- Connect website editing separately if you want the assistant to save a report draft.
Bright credentials, website credentials, and the assistant’s account are separate. We will explain any provider prerequisites, plan limits, and access restrictions in the working installation guide. You should not need to paste a password into an ordinary conversation to complete a properly implemented authorization flow.
Your first verification question
Copy the connection-verification prompt
Use the connected market-data tools, if available, to list the Bright Stats markets and metrics I am authorized to access. Retrieve the latest complete reporting period for [AREA] and [HOME TYPE], with the same period last year. Return source links, units, exact filters, reporting dates, retrieval time and any unavailable figures. If the connection is missing, tell me rather than inventing a result. Prepare a concise seller briefing from the retrieved evidence. Do not publish or send it.
A useful response identifies the tool it used, the exact area and home types, the month, the figures, and source links. A fluent market summary without those references is not proof of a connected data retrieval.
What you can do before the connection launches
Use a provider export or source figures you are permitted to share. Give the assistant the actual file and ask it to describe the columns before writing the report. Where a chart is inaccessible, provide the export rather than asking the assistant to infer exact values from a picture.
Copy the source-analysis prompt
Read the Bright Stats data or export I provide. Identify the geography, geography level, property types, metric definitions and latest reporting period first. Summarize the main changes against the same period last year. Show the underlying figures and calculations. Separate observations from interpretations. Cite the supplied source. Do not invent missing figures, neighborhood boundaries or a forecast. Ask for a source export if the chart is not readable.
Then ask for a seller briefing, a buyer comparison, or an email draft with a link to the complete report. Keep periods and filters consistent. Review the final language before sending it.
Reading data and publishing are separate actions
The market-data connection answers questions about source material. A website connection can supply a different set of capabilities, such as reading posts or saving a draft. Its permissions determine what is actually possible.
Our default tutorial will prepare a draft, return the actual preview, and ask for publication only after review. Do not treat successful sign-in as evidence that a report was saved or published.
See how the same evidence would appear on the website, or use the browser-assistant preparation workflow.