PeopleLikeUs MCP Server
The PeopleLikeUs MCP Server lets you interact with the PeopleLikeUs home exchange platform via an AI assistant, covering authentication, property browsing, calendar management, messaging, exchange tracking, and search.
Authentication
Check login status, log in with email/password, or inject browser cookies
Automatically handles CSRF protection and session caching
Properties
Get details for any property by ID
List your own properties
(Property creation/editing is not supported)
Calendar Management
Add or delete availability periods (simultaneous, non-simultaneous, non-reciprocal, or hospitality types)
Add or delete unavailability periods
View existing availability and unavailability periods
Conversations & Messaging
List conversations with filters (unread, exchanges, flagged, sent, received, trash)
Read messages in a conversation thread
Send, delete messages, or delete/trash entire conversations
Exchange Management
List and view details for exchanges
Propose new exchanges
Update exchange dates or type (simultaneous, non-reciprocal, etc.)
Cancel exchanges
Search
Search homes by location, country, dates, or number of guests
Quick search by listing number
User Info & Notifications
Retrieve authenticated user information
Get notifications
Technical notes: Supports automatic retry/backoff for rate limiting (HTTP 429/503) and uses both JSON API and HTML parsing for data.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@PeopleLikeUs MCP Server find homes in Paris for July"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
PeopleLikeUs MCP
MCP server for the PeopleLikeUs home-exchange platform — search homes, message members, manage your calendar and exchanges from your AI assistant.
Installation · Tools · Examples · Limitations · 🇫🇷 Français
Overview
This MCP server exposes PeopleLikeUs as 26 tools your assistant can call. Login is automatic from your email/password — no manual token extraction (no CAPTCHA, no Auth0). Ask in natural language:
You: Search homes in Portugal, then add availability on my property 40646 from July 4 to August 29.
Assistant: (calls
plu_search_homes, thenplu_add_availability) 12 homes in Portugal (Lisbon, Porto, Algarve…). Availability added on property 40646 for Jul 4 → Aug 29. ✅
Related MCP server: toolhouse-mcp
Requirements
Node.js ≥ 18
A PeopleLikeUs account (Premium recommended)
Any MCP client — Claude Code, Claude Desktop, Cursor…
Installation
git clone https://github.com/manganate006/peoplelikeus-mcp
cd peoplelikeus-mcp
npm install && npm run buildClaude Code
claude mcp add peoplelikeus \
--env PLU_EMAIL=your@email.com \
--env PLU_PASSWORD=yourpassword \
-- node /absolute/path/to/peoplelikeus-mcp/dist/index.jsClaude Desktop / Cursor
Add to claude_desktop_config.json (or your client's MCP config):
{
"mcpServers": {
"peoplelikeus": {
"command": "node",
"args": ["/absolute/path/to/peoplelikeus-mcp/dist/index.js"],
"env": {
"PLU_EMAIL": "your@email.com",
"PLU_PASSWORD": "yourpassword"
}
}
}
}Authentication
Set PLU_EMAIL + PLU_PASSWORD — the server handles login, CSRF and session automatically (cached at ~/.peoplelikeus-mcp-session.json, 1 h TTL). Alternatives (browser cookies via PLU_COOKIES, runtime plu_login), rate-limit tuning and the full auth priority: docs/TOOLS.md.
Tools
26 tools, plu_ prefix. Summary by domain — full parameters in docs/TOOLS.md.
Domain | Tools | Examples |
🔐 Auth | 3 |
|
🏠 Properties | 2 |
|
📅 Calendar | 6 |
|
💬 Conversations & messages | 5 |
|
🔄 Exchanges | 6 |
|
🔍 Search | 2 |
|
🔔 Misc | 2 |
|
Examples
"Search for homes in Portugal"
"Show my conversations"
"Message user 12345 about property 67890: "Hello, we love your place…""
"Add availability for my property 40646 from July 4 to August 29"
"Show my exchanges, then cancel exchange 22076"
Limitations
HTML parsing — some pages are Laravel Blade server-rendered; extraction depends on the HTML structure and can break if the site changes
No image upload for property photos (multipart not implemented)
Read-only listings — no property creation/editing
Search uses
country_long; location search needs coordinates (no server-side Google Places)Rate limiting — 1500 ms between requests by default (
PLU_REQUEST_DELAY); auto retry/backoff on HTTP 429/503
Development
npm run dev # tsc watch
npm run build # compile TypeScriptFull tool reference, configuration and architecture: docs/TOOLS.md.
License
Available Tools
26 toolsplu_add_availabilityA
Add an availability period. IMPORTANT: ask user confirmation.
Inputs: endDate (required), startDate (required), propertyId (required), sim, +3 more.
plu_auth_statusC
Check authentication status
Inputs: no named parameters.
plu_cancel_exchangeC
Cancel an exchange. IMPORTANT: ask user confirmation.
Inputs: exchangeId (required).
plu_create_exchangeB
Create/propose a new exchange. IMPORTANT: ask user confirmation.
Inputs: userId (required), propertyId (required).
plu_delete_availabilityC
Delete an availability period. IMPORTANT: ask user confirmation.
Inputs: availabilityId (required).
plu_delete_conversationC
Delete/trash a conversation. IMPORTANT: ask user confirmation.
Inputs: chatId (required).
plu_delete_messageC
Delete a message. IMPORTANT: ask user confirmation.
Inputs: messageId (required).
plu_get_auth_userB
Get authenticated user info
Inputs: no named parameters.
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.
Inputs: propertyId (required).
plu_get_conversationsC
Get conversation list. Filters: 'unread', 'exchanges', 'action_needed', 'flagged', 'received', 'sent', 'trash'
Inputs: page, filter.
plu_get_exchangeC
Get exchange details
Inputs: exchangeId (required).
plu_get_exchangesB
Get my exchanges list
Inputs: no named parameters.
plu_get_messagesA
Get messages in a conversation thread. Note: PeopleLikeUs rate-limits requests; prefer sequential calls over firing many in tight succession.
Inputs: userId (required), propertyId (required).
plu_get_my_propertiesA
Get my properties list
Inputs: no named parameters.
plu_get_notificationsB
Get notifications (JSON)
Inputs: no named parameters.
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.
Inputs: propertyId (required).
plu_loginA
Login with email and password. IMPORTANT: ask user confirmation before sending credentials.
Inputs: email (required), password (required).
plu_quick_searchC
Search by listing number
Inputs: listingNumber (required).
plu_search_homesC
Search homes with filters
Inputs: page, guests, country, endDate, +2 more.
plu_send_messageA
Send a message to a user. IMPORTANT: ask user confirmation before sending.
Inputs: body (required), toUserId (required), propertyId (required), chatId, +1 more.
plu_set_cookiesA
Inject raw browser cookies for authentication. Get from DevTools → Application → Cookies → document.cookie
Inputs: cookies (required).
plu_update_exchange_datesB
Update exchange dates. IMPORTANT: ask user confirmation.
Inputs: endDate (required), startDate (required), exchangeId (required).
plu_update_exchange_typeC
Update exchange type. IMPORTANT: ask user confirmation.
Inputs: swapType (required), exchangeId (required).
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
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.
Maintenance
Related MCP Connectors
Connect any AI agent to 1,000+ apps and 27,000+ actions through one remote MCP server (OAuth).
Automate 1,000+ services from any MCP-compatible AI agent: build Applets, run actions and queries.
Zero-setup MCP gateway securely connecting AI to your tools with authentication and workflows
MCP server for your apps' tools and custom tools, plus hosted AI agents and approval-gated workflows
Related MCP Servers
- FlicenseNot gradedqualityNot gradedmaintenanceEnables AI assistants to interact with Hostaway's property management platform through standardized MCP tools. Provides access to listings, bookings, guest communication, and availability checking for vacation rental management.-

toolhouse-mcpofficial
AlicenseNot gradedqualityDmaintenanceEnables MCP clients to access Toolhouse's extensive library of tools, allowing AI assistants to perform actions like web scraping, memory management, and email sending through natural language commands.5MIT- AlicenseNot gradedqualityDmaintenanceMCP server for Airbnb — lets AI agents search listings, check availability, manage reservations, and book stays via browser automation.14 npmMIT
- AlicenseNot gradedqualityBmaintenanceEnables searching homes, reading messages, and managing favourites on HomeExchange via an AI client.3ISC