DaedalMapHow it works
Search the catalog, select the packs and sources relevant to your question, and confirm the corpus. The Research MCP tools prepare the source boundary, expose each source's query contract, and return evidence rows. Your MCP client uses those rows to write the answer and separates source evidence from outside knowledge.
A missing source stays a visible gap. The corpus does not silently expand to the whole catalog. Check source IDs, versions, provenance, coverage, units, and warnings before relying on a result.
Run it with local data
- An MCP-capable client with model access.
- The MCP Runtime Kit from Downloads.
- A local data root with a catalog and the selected source files.
The kit runs the Research MCP at /mcp/research on your own
machine. The corpus tools are part of that MCP service. You select the
local data to install; the kit does not download every pack automatically.
Hosted access
The hosted Research MCP queries published sources and is shared by access
token. Connect it to an MCP-capable client using
https://app.daedalmap.com/mcp-private/research. Keep the
DaedalMap bearer token in your client's secure configuration. It is
separate from your model-provider subscription.
Typical research flow
- Find relevant packs and sources with the MCP's discovery tools.
- Confirm the corpus and inspect each source's coverage and query contract.
- Ask for evidence rows with a specific geography, period, and metric.
- Have your client synthesize an answer with citations and stated limits.
The local kit queries the sources in its data root. The hosted endpoint queries published sources. In both cases, the MCP tools select and prepare the corpus before evidence queries.
Maps and downloads
Research in the MCP client runs separately from the map. Use Explore to inspect published map layers, or download data and geometry for local maps.