Skip to content

Cursor PortlandMaps (Unofficial) get_permit_data

How to: Cursor PortlandMaps (Unofficial) get_permit_data

client:Cursor transport:streamable-http tool:get_permit_data

Add PortlandMaps (Unofficial) to Cursor

  1. 01

    Open ~/.cursor/mcp.json and merge this in. Keep any servers already there.

{
  "mcpServers": {
    "portlandmaps-mcp": {
      "url": "https://portlandmaps-mcp.vercel.app/mcp/v2"
    }
  }
}
  1. 02

    Save the file and restart Cursor.

  2. 03

    Ask for something get_permit_data does. Cursor lists the server's tools on connect and calls get_permit_data itself — you do not invoke it by name.

  3. 04

    If nothing happens, check the server is running and that PortlandMaps (Unofficial)'s identifier in your config matches the one above exactly.

Use .cursor/mcp.json in a project root instead to scope it to that project. Cursor merges both. Cursor docs

Set these first

PortlandMaps (Unofficial) will not start until these are set, so get_permit_data never becomes available.

  • PORTLANDMAPS_API_KEY
  • PORTLANDMAPS_API_KEY_PARAM
  • PORTLANDMAPS_CACHE_TTL_MS

Same tool, other clients

This list was read from the server itself, by connecting to it and calling tools/list on 24 September 2026. It is what the server actually exposes, not what its listing claims.

Mutating and Read-only are read off each tool's name, not its schema — a hint, not a guarantee. The registry stores tool names only; connect the server for its live schemas.