streeteasy-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PORT | No | Port to listen on. Railway sets this automatically. | 3000 |
| MCP_AUTH_TOKEN | No | Optional. If set, POST /mcp requires Authorization: Bearer <token>. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_rentalsA | Search active NYC rental listings on StreetEasy with filters. Areas accept names (e.g. 'MANHATTAN', 'Williamsburg', 'upper east side') or numeric area codes — use list_areas to discover them. Amenities are uppercase enum tokens — use list_amenities. Returns a compact list of listings plus a totalCount; paginate with page/perPage. Each listing has an |
| get_rental_detailsB | Fetch full details for a single rental listing by its id (the |
| list_areasA | List StreetEasy area names and their numeric codes for use in search_rentals. Optionally pass a search term to filter (e.g. 'brooklyn', 'harlem', 'williams'). Names are matched case/spacing-insensitively. |
| list_amenitiesA | List the valid amenity enum tokens accepted by search_rentals (e.g. WASHER_DRYER, DOORMAN, GYM, PRIVATE_OUTDOOR_SPACE). |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 4 tools
Each tool has a distinct purpose: search_rentals for querying listings, get_rental_details for full info on a specific listing, and list_amenities/list_areas for retrieving valid filter values. No overlap.
All tool names follow a consistent verb_noun pattern in snake_case (get_rental_details, list_amenities, list_areas, search_rentals), making them predictable and uniform.
With 4 tools, the server is well-scoped for its purpose of browsing NYC rental listings. It covers searching, detail retrieval, and necessary enum lookups without bloat or insufficiency.
The tool surface provides a complete workflow: discover valid filters (amenities/areas), search listings with those filters, and get full details for any listing. No obvious gaps for a read-only rental search API.