Skip to documentation
Developer documentation
Get API key
REST API v1

AI agent integration

Use the standalone MCP adapter with your Township America API key.

On this page
MCP Server

AI Agent Integration

Connect Claude Desktop, Cursor, Continue, or Cline directly to the PLSS API using the Model Context Protocol. Let AI agents convert legal land descriptions, look up coordinates, and export GeoJSON boundaries with your Township America API key.

The MCP server uses a standalone Township America API key from your dashboard. The separate remote ChatGPT and Claude connector is included on Pro and above. This SDK-based MCP adapter follows your standalone API subscription tier (Build / Scale / Enterprise).

Available Tools (6)

Tool Description
plss_to_coordinates Convert a PLSS legal land description to GPS coordinates
coordinates_to_plss Find the PLSS description for GPS coordinates
plss_to_geojson Get the GeoJSON boundary polygon for a PLSS description
validate_description Validate and normalize a PLSS description (local, no API call)
batch_convert Convert up to 1,000 PLSS descriptions in one request

Prerequisites

  • , A standalone Township America API key (Build / Scale / Enterprise) from your dashboard. Business includes MCP server access.
  • , Node.js 22+ (for npx)

Connect from Claude Desktop

Edit ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or ~/.config/claude/claude_desktop_config.json (Linux):

claude_desktop_config.json
{
  "mcpServers": {
    "townshipamerica": {
      "command": "npx",
      "args": ["-y", "townshipamerica-mcp"],
      "env": {
        "TOWNSHIP_AMERICA_API_KEY": "your_api_key_here"
      }
    }
  }
}

Replace your_api_key_here with your Township America API key. Restart Claude Desktop after saving.

Connect from Cursor

Open Cursor Settings → MCP, or edit ~/.cursor/mcp.json:

mcp.json
{
  "mcpServers": {
    "townshipamerica": {
      "command": "npx",
      "args": ["-y", "townshipamerica-mcp"],
      "env": {
        "TOWNSHIP_AMERICA_API_KEY": "your_api_key_here"
      }
    }
  }
}

Connect from Continue

Add to ~/.continue/config.json:

config.json
{
  "experimental": {
    "modelContextProtocolServers": [
      {
        "transport": {
          "type": "stdio",
          "command": "npx",
          "args": ["-y", "townshipamerica-mcp"],
          "env": {
            "TOWNSHIP_AMERICA_API_KEY": "your_api_key_here"
          }
        }
      }
    ]
  }
}

Connect from Cline

Open Cline settings, navigate to MCP Servers, and add:

cline_mcp_settings.json
{
  "mcpServers": {
    "townshipamerica": {
      "command": "npx",
      "args": ["-y", "townshipamerica-mcp"],
      "env": {
        "TOWNSHIP_AMERICA_API_KEY": "your_api_key_here"
      }
    }
  }
}

Troubleshooting

"Township America API key is required"

Add TOWNSHIP_AMERICA_API_KEY to the env block in your MCP config file, not as a shell environment variable. The MCP host passes env vars from the config. Older configs that use TA_API_KEY still work.

"Quota exceeded" error

Your quota depends on your standalone API tier. Build = 1,000 calls/month per endpoint; Scale and Enterprise go higher. Upgrade at /app/api or wait for the monthly reset.

Server not appearing in your AI assistant

Restart the AI assistant after editing the config file. Verify your config is valid JSON. Run npx townshipamerica-mcp in a terminal with TOWNSHIP_AMERICA_API_KEY set to check for startup errors.

Tool returns "Not found" for a valid description

PLSS covers 30 US states. Texas uses the TXSS survey system (abstract, block, and survey descriptions) and is fully supported. Alaska, Hawaii, and some eastern states may not resolve. Use the validate_description MCP tool to check your format.