For AI assistants

Engawa MCP server

Connect an MCP-compatible assistant directly to Engawa's Japan property catalogue. Search listings, inspect buyer context, compare homes, estimate closing costs, and hand a shortlisted property to the concierge service without leaving the conversation.

Endpoint

https://engawahomes.com/api/mcp

Transport: Streamable HTTP. The endpoint accepts MCP requests over POST and is stateless between requests.

Authentication

Use an Engawa API key as a bearer token. MCP catalogue access is included with annual Explorer membership.

Create an API key Explorer pricing

Connect a client

Add the remote server URL and send your key in the Authorization header. Exact configuration keys vary by MCP client; this is the common JSON shape.

{
  "mcpServers": {
    "engawa": {
      "type": "http",
      "url": "https://engawahomes.com/api/mcp",
      "headers": {
        "Authorization": "Bearer YOUR_ENGAWA_API_KEY"
      }
    }
  }
}

Treat the API key like a password. Do not commit it to source control or publish it in a directory listing.

Available tools

search_properties

Filter Japanese property listings by location, price, type, size, age, and renovation state.

get_property

Open a full listing record with property facts, hazards, transit context, condition signals, and provenance.

compare_properties

Compare up to five Engawa listings side by side.

estimate_closing_costs

Estimate Japanese purchase closing costs and annual holding costs.

list_prefectures

List prefectures represented in the catalogue and their current listing counts.

concierge_info

Get Engawa concierge pricing and the booking link for a property enquiry.

Data boundaries

Engawa aggregates listing information and buyer-context data for research. It is not a licensed real-estate broker and MCP responses are not legal, tax, structural, or investment advice.

Unresolved hazard or transit lookups are reported as unavailable, not inferred as low risk. Structural condition, surveys, defect disclosures, rail service frequency, and municipal assessed values require separate professional or official checks where applicable.

Discovery metadata

Directory crawlers and MCP clients can discover the public server metadata at either compatibility path below. The registry identifier is io.github.augustin-v/engawa.

/.well-known/mcp/server-card.json /.well-known/mcp.json