Evlek — Northern Cyprus Property MCP Server

Evlek MCP Server

Evlek is the Northern Cyprus property portal: Northern Cyprus property listings for sale and long-term rent, an asking-price index by city and district, and this MCP server (see the MCP documentation).

AI-native property discovery for North Cyprus (KKTC). Built on the Model Context Protocol — works in Claude, ChatGPT, Gemini, Cursor, and any MCP-compatible client.

The Evlek MCP server gives AI agents structured, real-time access to North Cyprus property data — search active listings, compare cities and districts, and track the price index. All data is sourced live from evlek.app. Evlek does not offer a rental-yield or investment-return estimate: figures are descriptive asking-price facts only, never a valuation, forecast, or recommendation. Title-deed (koçan) and legal-procedure tools are deliberately not part of the surface: that taxonomy has not passed an independent KKTC legal audit.

License scope

This repository is MIT-licensed for the public manifest, documentation, examples, and reference clients contained here. The hosted Evlek service, evlek.app web app, mobile apps, listing database, AI prompts, business logic, brand assets, name, logo, and trade dress remain proprietary and are not licensed under MIT. See LICENSE for details.

---

Why Evlek MCP

• AI-first. Built for agentic workflows from day one — not retrofitted on a legacy listing API.
• Multilingual. Answers in TR, EN, RU, DE, AR: pass locale (or write the search query in that language) and the text, amenity names, number formats and links follow it. Place names are resolved in any of the five languages.
• Verification-aware listings. Evlek surfaces listing and account verification context where available, and the MCP omits contact fields to preserve Evlek's reveal/contact funnel.
• Built for the region. Optimized for the 6 cities of North Cyprus (Lefkoşa, Girne, Gazimağusa, İskele, Güzelyurt, Lefke) and 100+ districts.
• Production-grade. OWASP MCP Top 10 aligned — Zod input validation, output sanitization, rate limiting (60/min/IP, 500/min global), Sentry observability.

---

Add Evlek to ChatGPT, Claude or your MCP client

The server URL is https://evlek.app/api/mcp. No sign-in, no API key.

ChatGPT

Evlek is in the ChatGPT app directory:

1. ChatGPT → Apps → search for "Evlek" → Connect.
2. In a chat, pick Evlek from the tools menu and ask, for example, *"2-bedroom flats for rent in Girne"*.

To add it by hand instead: Settings → Apps & Connectors → Advanced settings → developer mode on, then Create with the URL https://evlek.app/api/mcp (no authentication).

Claude (web and desktop)

1. Settings → Connectors → Add custom connector.
2. Name: Evlek. URL: https://evlek.app/api/mcp.
3. In a chat, turn Evlek on from the tools menu.

Claude Code

claude mcp add --transport http evlek https://evlek.app/api/mcp

MCP Registry

Evlek is in the official MCP Registry as app.evlek/mcp-server (registry entry). Clients that install from the registry find it under that name; the entry points at the same URL.

More options (Cursor, VS Code, stdio) are under Quick start and on the MCP documentation page.

---

Quick start

Remote-capable clients (preferred)

Most modern MCP clients (Claude, Cursor, VS Code) connect directly to the Streamable HTTP endpoint — no local bridge needed:

{

"mcpServers": { "evlek": { "url": "https://evlek.app/api/mcp" } } }

ChatGPT (connector + Deep Research)

Add https://evlek.app/api/mcp as a custom connector. Evlek exposes OpenAI-compatible search and fetch tools, so it works in ChatGPT connectors and Deep Research in addition to developer mode.

Claude Desktop (legacy stdio bridge)

If your client only supports stdio servers, use the pinned mcp-remote bridge. Add this to ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\Claude\claude_desktop_config.json (Windows):

{

"mcpServers": { "evlek": { "command": "npx", "args": ["-y", "mcp-remote@0.1.16", "https://evlek.app/api/mcp"] } } }

Restart Claude Desktop. The "evlek" server appears in the tools list.

MCP Inspector (test before installing)

npx @modelcontextprotocol/inspector https://evlek.app/api/mcp

Direct API (cURL)

curl -X POST https://evlek.app/api/mcp \

-H "Content-Type: application/json" \ -d '{"jsonrpc":"2.0","id":1,"method":"tools/list"}'

More configs: examples/

---

Local stdio server (this repository)

This repo is also a runnable MCP server. It answers initialize / tools/list entirely locally from the embedded tool contract (tools.json) and fetches live data from the Evlek data API when a tool is called. It only implements tools — it does not declare the resources or prompts capability, so resources/list and prompts/list return a normal MCP "method not found" error on this bridge; those primitives (see below) are hosted-endpoint-only, reachable via the Streamable HTTP URL above. It also speaks whatever MCP protocol version the pinned @modelcontextprotocol/sdk supports during initialize (currently 2025-11-25), not necessarily the hosted endpoint's 2026-07-28 — tool schemas are identical either way.

npx github:Evlek/evlek-mcp        # or: npm install && npm start

{

"mcpServers": { "evlek": { "command": "npx", "args": ["-y", "github:Evlek/evlek-mcp"] } } }

Smoke-test it (spawns the server and speaks real MCP over stdio):

npm test              # live: initialize + tools/list + a real tools/call

OFFLINE=1 npm test # offline: introspection works with zero network

Available tools

8 tools · protocol 2026-07-28 · Streamable HTTP JSON-RPC 2.0

| list_locations | List Evlek locations | List the places Evlek knows in Northern Cyprus (6 ci