DaedalMap Administrative Boundaries (loc_id to polygon) MCP Server

What the code does

We read the source, 1 d ago · tools taken from the live server · rules 995398eba69f

A value the model can set ends up inside a file or shell call. That is not a flaw by itself — for a terminal server it is the job — but it is where things go wrong when it is not.

    result = subprocess.run([sys.executable, str(SCRIPTS_DIR / script), *arguments], cwd=ROOT, capture_output=True, text=True, check=False)

What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.

    result = subprocess.run([sys.executable, str(SCRIPTS_DIR / script), *arguments], cwd=ROOT, capture_output=True, text=True, check=False)

    files = sorted(str(p.relative_to(data_dir)) for p in data_dir.rglob("*") if p.is_file())

Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 4 min ago.

claude mcp add boundaries --transport http https://app.daedalmap.com/mcp/boundaries

https://app.daedalmap.com/mcp/boundaries

[mcp_servers.boundaries]
url = "https://app.daedalmap.com/mcp/boundaries"

{
  "mcpServers": {
    "boundaries": {
      "url": "https://app.daedalmap.com/mcp/boundaries"
    }
  }
}

{
  "servers": {
    "boundaries": {
      "type": "http",
      "url": "https://app.daedalmap.com/mcp/boundaries"
    }
  }
}

Available tools 7

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

Tools removed

Tools this server used to expose. Anything built against them stopped working on the day they went.

Endpoints