Data Collection

mapledger.app

Provides Austin and Nashville land zoning, lot development potential, and local business search data.

1 endpoint3 known toolsFirst detected September 29, 2026Last detected September 29, 2026

ENDPOINT 1

https://mapledger.app/mcp

No auth detected

MCP server metadata

Name: mapledger
Version: 1.1.0

Capabilities

tools.listChanged

Server instructions

MapLedger answers what you can do with a piece of land in Austin, Texas and Nashville (Davidson County), Tennessee, from the cities' own records, and finds local businesses in Central Austin. Use land_at for one address or point, find_land to search a whole city for land that fits a need, and search_businesses for Austin businesses. Answers are screening estimates with sources, not zoning letters or legal advice. Coverage is only Austin and Nashville.

Known tools 3

land_at

Use when someone asks what they can do with a specific property or address in Austin, TX or Nashville, TN: what it is zoned and what that means, how many homes the lot can take (Austin HOME rules, Texas SB 840 apartments on commercial land), what the zoning ordinance or Nashville Specific Plan says, whether a short-term rental (Airbnb) is allowed, the property tax and flood risk.

Inferred read-only

find_land

Use when someone wants to find land or lots in Austin or Nashville that fit a need, for example lots where three homes are allowed, commercial land where apartments are allowed without a rezoning, dry industrial land of 5+ acres, zoning where whole-home short-term rentals are permitted, or Specific Plans whose ordinance bans rentals.

Inferred read-only

search_businesses

Use when someone wants a list of local businesses in Central Austin, TX by kind (for example dentists, coffee shops, plumbers), optionally only ones with no website listed or with a phone or email.

Potential side effects

CONNECT WITH APPROVAL

Client installation

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.mapledger]
url = "https://mapledger.app/mcp"
enabled = true

Claude Code

.mcp.json

{
  "mcpServers": {
    "mapledger": {
      "type": "http",
      "url": "https://mapledger.app/mcp"
    }
  }
}

Claude Desktop

Settings → Connectors → Add custom connector

Name: mapledger
Remote MCP URL: https://mapledger.app/mcp

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

{
  "mcpServers": {
    "mapledger": {
      "url": "https://mapledger.app/mcp"
    }
  }
}

Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code

{
  "servers": {
    "mapledger": {
      "type": "http",
      "url": "https://mapledger.app/mcp"
    }
  }
}

Generic MCP

Client-specific MCP configuration

{
  "name": "mapledger",
  "transport": "streamable-http",
  "url": "https://mapledger.app/mcp"
}

MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

TRUST AND VERIFICATION EVIDENCE

Loading Trust v2 evidence…

Checking the associated registrable domain. The BuiltWith key remains server-side.

Indexed

Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.