PeopleLikeUs MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PLU_EMAIL | No | Login email for PeopleLikeUs | |
| PLU_COOKIES | No | Raw cookie string from browser DevTools | |
| PLU_PASSWORD | No | Login password for PeopleLikeUs | |
| PLU_REQUEST_DELAY | No | Delay between requests in milliseconds | 1000 |
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| plu_auth_statusC | Check authentication status |
| plu_loginA | Login with email and password. IMPORTANT: ask user confirmation before sending credentials. |
| plu_set_cookiesA | Inject raw browser cookies for authentication. Get from DevTools → Application → Cookies → document.cookie |
| plu_get_propertyA | Get property details by ID (public page). Note: PeopleLikeUs rate-limits requests; the server already throttles and retries on 429, so prefer sequential calls over firing many in tight succession. |
| plu_get_my_propertiesA | Get my properties list |
| plu_get_availabilitiesA | Get availability periods for a property (JSON API). Note: PeopleLikeUs rate-limits requests; prefer sequential calls over firing many in tight succession. |
| plu_get_unavailabilitiesA | Get unavailability periods for a property (JSON API). Note: PeopleLikeUs rate-limits requests; prefer sequential calls over firing many in tight succession. |
| plu_add_availabilityA | Add an availability period. IMPORTANT: ask user confirmation. |
| plu_delete_availabilityC | Delete an availability period. IMPORTANT: ask user confirmation. |
| plu_add_unavailabilityA | Add an unavailability period. IMPORTANT: ask user confirmation. |
| plu_delete_unavailabilityC | Delete an unavailability period. IMPORTANT: ask user confirmation. |
| plu_get_conversationsC | Get conversation list. Filters: 'unread', 'exchanges', 'action_needed', 'flagged', 'received', 'sent', 'trash' |
| plu_get_messagesA | Get messages in a conversation thread. Note: PeopleLikeUs rate-limits requests; prefer sequential calls over firing many in tight succession. |
| plu_send_messageA | Send a message to a user. IMPORTANT: ask user confirmation before sending. |
| plu_delete_messageC | Delete a message. IMPORTANT: ask user confirmation. |
| plu_delete_conversationC | Delete/trash a conversation. IMPORTANT: ask user confirmation. |
| plu_get_exchangesB | Get my exchanges list |
| plu_get_exchangeC | Get exchange details |
| plu_create_exchangeB | Create/propose a new exchange. IMPORTANT: ask user confirmation. |
| plu_update_exchange_datesB | Update exchange dates. IMPORTANT: ask user confirmation. |
| plu_update_exchange_typeC | Update exchange type. IMPORTANT: ask user confirmation. |
| plu_cancel_exchangeC | Cancel an exchange. IMPORTANT: ask user confirmation. |
| plu_search_homesC | Search homes with filters |
| plu_quick_searchC | Search by listing number |
| plu_get_notificationsB | Get notifications (JSON) |
| plu_get_auth_userB | Get authenticated user info |
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 26 tools
Each tool has a clearly distinct purpose: authentication, property management, availability/unavailability CRUD, conversation/messaging, exchange lifecycle, search, and notifications. No two tools overlap in functionality.
All tools use the 'plu_' prefix and generally follow a verb_noun pattern (e.g., get_property, add_availability). Minor exceptions like 'login' (single verb) and 'auth_status' (noun_noun) cause slight inconsistency but do not hinder readability.
26 tools is on the high side but appropriate for a feature-rich home exchange platform covering authentication, properties, availability, messaging, exchanges, and search. Each tool serves a specific purpose without redundancy.
The tool set covers the main workflows: authentication, viewing/managing properties, availability CRUD, conversation handling, exchange creation/editing/cancellation, and search. Minor gaps like missing property update or user profile management are acceptable for the domain.