gongvue — MCP endpoints

Two Model Context Protocol servers over spatial data: a catalogue of building assets, and a graph of modelled buildings. Both speak JSON-RPC 2.0 over HTTP and go into any MCP client.

https://mcp.gongvue.com/dawaOPEN

DAWA asset catalogue — furniture, fixtures, equipment and whole building models, searchable in four languages. No key needed.

dawa_search
Search the catalogue in Korean, English, Japanese or Chinese. A query in any one of them matches assets named in any other — 의자, 椅子 and chair reach the same chairs. Filter by kind, category, licence, building type or floor area.
dawa_similar
Assets like a given one, by shared concepts and — where configured — embedding distance.
dawa_list_tabs
The catalogue’s own shape: tabs, categories, and how many assets are in each.
dawa_get_asset
One asset in full, including its model URL and its licence.
https://mcp.gongvue.com/ontologyKEY REQUIRED

Building ontology — 36 tools over a graph of real buildings: their spaces, circulation, equipment, sensors and events. This one is not open, and will not be. The graph holds clients’ facilities, including where people went in them; an anonymous reader is the wrong default for that, whatever the convenience. Ask us for a key.

Buildings
list_layers, project_stats, project_detail, list_floors — what is modelled and how much of it.
Spaces
find_spaces, get_space, space_properties — search by type, floor or area; occupancy, temperature range and floor loading per room.
Circulation
space_neighbors, shortest_path, path_to_nearest, adjacency_check — routes through a building, and whether the layout obeys the adjacency its typology asks for.
Facilities
find_assets, assets_in_space, rack_devices, device_network — racks, devices and what is connected to what.
Operations
space_occupancy, space_throughput, find_sensors, sensor_history, recent_events, impact_analysis — readings, movement and what a failure would take with it.

Add them to a client

{
  "mcpServers": {
    "dawa":     { "url": "https://mcp.gongvue.com/dawa" },
    "ontology": { "url": "https://mcp.gongvue.com/ontology",
                  "headers": { "Authorization": "Bearer YOUR_KEY" } }
  }
}

Try the open one without a client

curl -s -X POST https://mcp.gongvue.com/dawa \
  -H 'Content-Type: application/json' \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/call",
       "params":{"name":"dawa_search",
                 "arguments":{"query":"사무실 의자","lang":"en","limit":5}}}'

Limits

Both endpoints are rate limited per caller. Tools that write — asset requests, reindexing — need a key and are not listed to anonymous callers.

Assets carry their own licences; dawa_get_asset returns the licence field, and it governs what you may do with the model. The endpoint tells you what exists — it does not grant you rights to it.