MCP vs REST API
Both use the same key and the same data. The difference is who makes the calls.
Side by side
| MCP server | REST API | |
|---|---|---|
| Who calls it | An AI assistant, when your question needs data. | Your code, on your schedule. |
| Setup | Add the hosted endpoint and your key to the client, or install the server locally. | An HTTP client and your key. |
| Coverage | 8 tools for markets, metrics, trends, pace, events, listings and estimates. | The same data, plus investment inputs on estimates. |
| Output | JSON the assistant reads and summarizes. get_metrics leaves out the nightly series unless asked. | Full JSON for you to store, chart or join with other data. |
| Limits | The same key limits. Each tool call is one request. | Your plan’s limits: 120 a minute and 25,000 a day during the free trial. |
| Best for | Exploration, one-off questions, drafting briefs. | Dashboards, spreadsheets, scheduled reports and products. |
Using both
A common pattern: explore a question with an assistant through MCP, then, once you know which numbers matter, write a small script against the REST API so the report runs every week without anyone asking. The tutorials are a good starting point.