Koskamo

Yatmo MCP MCP server

A read-only Model Context Protocol server operated by Yatmo that allows AI agents and real-estate copilots to query neighbourhood intelligence data. It exposes tools to retrieve location summaries, nearby points of interest, and accessibility profiles for properties across 25 countries, using the same licence key as the standard Yatmo REST API.

Endpoint and access

OAuth sign-in: the first time you connect, your client opens the vendor's own authorization prompt in a browser.

OAuth sign-inEndpoint checked 2026-10-05Operated by Yatmo SRL
MCP endpoint (Streamable HTTP)
https://mcp.yatmo.com/mcp/v1
Vendor documentation

What you can do with it

  • Retrieve human-readable neighbourhood summaries and structured facts for a property location
  • Find nearby points of interest like schools, supermarkets, and transport stops within a radius
  • Get the nearest specific POI category with distance and travel time details
  • Check public transport accessibility profiles including nearest stops and stations

Connect from your client

Each snippet registers the same endpoint; pick the client you use.

This server is operated by the named third party. Listing and endpoint checks are not an endorsement or a security audit. Review the operator's permissions, terms, and data handling before connecting. How listings are checked and corrected.

Claude Code

Run this once in a terminal. It registers a Streamable HTTP server. Use --scope project to write .mcp.json for the repo.
Claude Code configuration
claude mcp add --transport http yatmo-mcp https://mcp.yatmo.com/mcp/v1

Codex

Run this once. Codex stores MCP servers in ~/.codex/config.toml (or .codex/config.toml in a trusted project).
Codex configuration
codex mcp add yatmo-mcp --url https://mcp.yatmo.com/mcp/v1

Cursor

Merge this server into .cursor/mcp.json in your project, then enable yatmo-mcp in your MCP settings.
Cursor configuration
{
  "mcpServers": {
    "yatmo-mcp": {
      "url": "https://mcp.yatmo.com/mcp/v1"
    }
  }
}

Cline

Merge this into cline_mcp_settings.json (Cline → MCP Servers → Configure). The type must be streamableHttp for a remote HTTP server.
Cline configuration
{
  "mcpServers": {
    "yatmo-mcp": {
      "type": "streamableHttp",
      "url": "https://mcp.yatmo.com/mcp/v1",
      "disabled": false
    }
  }
}

VS Code

Merge this server into .vscode/mcp.json. Use MCP: List Servers to start yatmo-mcp and inspect its tools.
VS Code configuration
{
  "servers": {
    "yatmo-mcp": {
      "type": "http",
      "url": "https://mcp.yatmo.com/mcp/v1"
    }
  }
}

Gemini CLI

Run this once. It writes .gemini/settings.json in the current project; pass --scope user for ~/.gemini/settings.json.
Gemini CLI configuration
gemini mcp add --transport http yatmo-mcp https://mcp.yatmo.com/mcp/v1

Claude Desktop

Merge this into claude_desktop_config.json (macOS: ~/Library/Application Support/Claude/, Windows: %APPDATA%\Claude\), then restart Claude Desktop.
Claude Desktop configuration
{
  "mcpServers": {
    "yatmo-mcp": {
      "url": "https://mcp.yatmo.com/mcp/v1"
    }
  }
}

Windsurf

Merge this into ~/.codeium/windsurf/mcp_config.json, then refresh MCP in Cascade. Windsurf remote servers use serverUrl, not url.
Windsurf configuration
{
  "mcpServers": {
    "yatmo-mcp": {
      "serverUrl": "https://mcp.yatmo.com/mcp/v1"
    }
  }
}

Do you run Yatmo MCP?

Prove ownership with a DNS record, a well-known file, or your Official MCP Registry entry, and your edits publish immediately. Proofs are re-checked weekly; admins can still hide or remove a listing.

Claim this listing