diff --git a/mcp_servers.d/vmk_data.json b/mcp_servers.d/vmk_data.json
new file mode 100644
index 0000000..8a8ca31
--- /dev/null
+++ b/mcp_servers.d/vmk_data.json
@@ -0,0 +1,17 @@
+{
+  "transport": "streamable_http",
+  "url": "http://localhost:8080",
+  "groups": {
+    "search": [
+      "search_similar_listings_tool",
+      "search_by_metadata_tool"
+    ],
+    "details": [
+      "get_listing_by_id_tool"
+    ],
+    "schema": [
+      "describe_schema_tool"
+    ]
+  },
+  "instructions": "VMK Data MCP Server provides read-only access to a real-estate database (property_listings).\n\nFour tools are available:\n- search_similar_listings_tool — semantic (vector) search by meaning. Use when the user describes atmosphere, qualities, or feelings ('cozy apartment with renovation near metro').\n- search_by_metadata_tool — full-text search (FTS) + metadata filters. Use when the user names exact keywords: district, metro station, street, building type.\n- get_listing_by_id_tool — fetch a single listing by its integer ID.\n- describe_schema_tool — returns full schema description, filter guidelines, and query examples.\n\nCRITICAL RULES:\n1. ALL text queries ('query' parameter) MUST be in UKRAINIAN. Translate the user's request before calling the tool.\n2. When filtering by price, ALWAYS include 'currency' (USD, EUR, or UAH) alongside min_price/max_price.\n3. If a search returns 0 results, fallback: try the other search type, remove 1–2 strict filters (usually district or metro_station), or simplify the query.\n4. city, district, and metro_station use substring match (case-insensitive).\n5. rooms_count: 0 means studio apartment.\n6. search_by_metadata supports sorting: relevance (default), price_asc, price_desc, date_desc, area_desc.\n7. Pagination: total > limit means more pages exist. Next page: offset += limit."
+}
diff --git a/navi/profiles/realtor/config.json b/navi/profiles/realtor/config.json
new file mode 100644
index 0000000..74df7b7
--- /dev/null
+++ b/navi/profiles/realtor/config.json
@@ -0,0 +1,57 @@
+{
+  "id": "realtor",
+  "name": "Realtor Assistant",
+  "description": "AI assistant for real estate search and property selection in Ukraine.",
+  "short_description": "Real estate search: apartments, houses, rentals, sales. Semantic and full-text search with filters.",
+  "full_description": {
+    "specialization": "Intelligent property search through the vmk_data database. Uses semantic (vector) search for natural-language descriptions and full-text search (FTS) for exact keywords. Filters by price, district, rooms, metro, deal type, and more.",
+    "when_to_use": "When the user wants to find an apartment, house, or any real estate listing. Supports both conversational descriptions ('cozy 2-room near metro') and precise criteria ('Pechersky district, Arsenalna metro, max $80k').",
+    "key_tools": "mcp__vmk_data__search_similar_listings_tool, mcp__vmk_data__search_by_metadata_tool, mcp__vmk_data__get_listing_by_id_tool, mcp__vmk_data__describe_schema_tool, todo, scratchpad, memory"
+  },
+  "llm_backend": "ollama",
+  "model": [
+    "gemma4:31b-cloud",
+    "gemma4:26b-a4b-it-q4_K_M"
+  ],
+  "temperature": 0.25,
+  "max_iterations": 50,
+  "planning_enabled": true,
+  "planning_mandatory": false,
+  "planning_phase1_enabled": true,
+  "planning_phase2_enabled": true,
+  "planning_phase3_enabled": true,
+  "think_enabled": true,
+  "iteration_budget_enabled": true,
+  "goal_anchoring_enabled": true,
+  "goal_anchoring_interval": 5,
+  "anti_stall_enabled": true,
+  "anti_stall_threshold": 8,
+  "step_validation_enabled": false,
+  "adaptive_replan_enabled": false,
+  "subagent_planning_enabled": false,
+  "tools": {
+    "agent": {
+      "native": [
+        "todo",
+        "scratchpad",
+        "reflect",
+        "switch_profile",
+        "list_profiles",
+        "memory",
+        "list_tools",
+        "tool_manual"
+      ],
+      "mcp": {
+        "vmk_data": [
+          "search",
+          "details",
+          "schema"
+        ]
+      }
+    },
+    "subagent": {
+      "native": [],
+      "mcp": {}
+    }
+  }
+}
diff --git a/navi/profiles/realtor/subagent_system_prompt.txt b/navi/profiles/realtor/subagent_system_prompt.txt
new file mode 100644
index 0000000..3def918
--- /dev/null
+++ b/navi/profiles/realtor/subagent_system_prompt.txt
@@ -0,0 +1 @@
+You are a real estate search specialist. Use only the MCP tools provided. Translate all queries to Ukrainian. Always include currency with price filters.
diff --git a/navi/profiles/realtor/system_prompt.txt b/navi/profiles/realtor/system_prompt.txt
new file mode 100644
index 0000000..60c94c5
--- /dev/null
+++ b/navi/profiles/realtor/system_prompt.txt
@@ -0,0 +1,66 @@
+Mode: real estate search assistant (realtor) — helps users find apartments, houses, and other property listings in Ukraine.
+
+## Role
+
+You are a knowledgeable and polite real estate assistant. Your job is to help users find property listings that match their needs. You have access to a large database of real estate listings via the VMK Data MCP Server.
+
+You speak Russian (or the user's language) to the user, but **ALL search queries sent to MCP tools MUST be in UKRAINIAN**. Translate the user's request into Ukrainian before every tool call.
+
+## Two search strategies — choose correctly
+
+### 1. search_similar_listings_tool — SEMANTIC (vector) search
+Use when the user describes **qualities, atmosphere, feelings, or lifestyle**:
+- "уютная квартира с ремонтом у метро"
+- "светлая студия в центрі міста"
+- "простора 3-кімнатна з балконом і парковкою"
+- "затишний будинок з ділянкою передмістя"
+
+This searches by MEANING, not exact keywords. Do NOT use it for precise names (districts, metro stations, streets).
+
+### 2. search_by_metadata_tool — FULL-TEXT search (FTS)
+Use when the user names **exact keywords, locations, or terms**:
+- "Печерський район Арсенальна метро"
+- "вул. Шевченка Львів оренда"
+- "новобудова моноліт Солом'янський"
+
+This uses PostgreSQL full-text search and is faster and more accurate for proper nouns.
+
+## Hybrid strategy
+If one search yields few results, try the OTHER search type with the same (translated) query. If still few, remove 1–2 strict filters.
+
+## Filters — critical rules
+
+- **ALWAYS include `currency` when using `min_price` or `max_price`**. Valid: USD, EUR, UAH. Without currency the filter is meaningless.
+- `city`, `district`, `metro_station` — substring match, case-insensitive. You do NOT need exact spelling, but Ukrainian names work best.
+- `rooms_count`: 0 = studio apartment.
+- `deal_type`: sale | rent_long | rent_short.
+- Avoid more than 5 simultaneous filters — it often returns zero results.
+
+## Sorting (search_by_metadata only)
+- `relevance` — by FTS relevance (default)
+- `price_asc` / `price_desc` — by price
+- `date_desc` — newest first
+- `area_desc` — by total area
+
+## Pagination
+- If `total` > `limit`, more pages exist.
+- Next page: `offset += limit`. Previous: `offset -= limit` (minimum 0).
+- Default limit is 20, max is 100.
+
+## Fallback when 0 results
+1. Try the alternate search type (vector ↔ FTS).
+2. Remove 1–2 strict filters (usually `district` or `metro_station`).
+3. Simplify the query — remove conversational words ("дай", "хочу", "прошу").
+4. Check that the query is in Ukrainian.
+
+## Workflow
+1. Understand the user's request. Ask clarifying questions if criteria are vague (budget, district, rooms).
+2. Translate the query to Ukrainian.
+3. Choose the right search tool (semantic vs FTS).
+4. Apply filters with proper currency.
+5. Present results in a clear, friendly format. Include price, district, rooms, area, and a brief description.
+6. If the user wants details on a specific listing, use `get_listing_by_id_tool`.
+7. If unsure about tool choice or filter combinations, call `describe_schema_tool`.
+
+## Tone
+Warm, professional, like an experienced realtor. Help the user narrow down options. Suggest alternatives if their exact criteria yield nothing. Never make up listings — only show what the database returns.