MCP
Use PricePulse from your own AI assistant.
Connect Claude or ChatGPT by adding PricePulse’s server address and signing in, with no key to copy. Cursor and other apps that support MCP servers connect with a key. Your assistant gets live short-term rental market data and read-only access to your own properties and PriceLabs data.
01 What it is
What your assistant can reach.
Live comps on demand
Search a market, price comps for your dates, read reviews and amenities. These tools use PricePulse credits, the same as in Telegram.
Your own portfolio
Properties, calendars and bookings from your connected property manager, plus your PriceLabs rates. Free to read.
It can’t change anything
No price pushes, no proposals, no settings or schedule changes. Those stay in Telegram, where you approve them.
02 Setup
Add the address, then sign in.
New to this? Follow the 4-step walkthrough.
1. Add PricePulse to Claude or ChatGPT as a custom connector, with the server address below.
2. Your app opens PricePulse: sign in, or create a free account there (50 credits, no card), check what the app can do and tap Approve.
Apps that take a key, like Claude Code and Cursor, use one of the snippets below with a key from Account → AI assistant (MCP).
https://agent-api.pricepulse.hatch-capital.com/mcp Paste this address as the server URL, then sign in to PricePulse and approve when your app asks. You need a PricePulse account; you can create a free one in the same window.
- Claude (web or desktop): Customize → Connectors → + Add → Add custom connector. Name it PricePulse, paste the address as the server URL, press Continue, choose Sign in now under Authentication, then Add. Claude sends you to PricePulse to sign in; if it doesn’t, press Connect next to PricePulse. If Claude doesn’t use PricePulse in a chat, open + → Connectors there and turn PricePulse on. It then works in the Claude phone app too. Menus change; Anthropic’s guide has the current steps.
- ChatGPT (web): Plugins → + → Add custom MCP server. Name it PricePulse and paste the address as the server URL. Under Authentication, choose OAuth, then accept the warning. Create as a plugin and install it; when ChatGPT sends you to PricePulse, sign in and approve. In a chat, type @ and pick PricePulse so its tools are used. Menus change and workspaces can turn this off; OpenAI’s guide has the current steps.
- Each app you approve shows in Account → AI assistant (MCP) under Connected apps, with a daily limit of 200 credits. Disconnect it there any time.
https://agent-api.pricepulse.hatch-capital.com/mcp/c/pp_live_YOUR_KEY For an app that can’t sign in, or if you’d rather not: create a key in your account, and it shows your private connector link once, together with the key. Add it the same way, with the link as the server URL: in Claude, choose No sign in under Authentication; in ChatGPT, choose No authentication. The link contains the key, so treat it like a password.
https://agent-api.pricepulse.hatch-capital.com/mcp Streamable HTTP. Every request sends your key as Authorization: Bearer pp_live_….
claude mcp add --transport http pricepulse https://agent-api.pricepulse.hatch-capital.com/mcp \
--header "Authorization: Bearer pp_live_YOUR_KEY"{
"mcpServers": {
"pricepulse": {
"command": "npx",
"args": [
"-y", "mcp-remote", "https://agent-api.pricepulse.hatch-capital.com/mcp",
"--header", "Authorization:${PRICEPULSE_AUTH}"
],
"env": { "PRICEPULSE_AUTH": "Bearer pp_live_YOUR_KEY" }
}
}
}Uses the open-source mcp-remote bridge (needs Node.js). Restart Claude Desktop after saving.
{
"mcpServers": {
"pricepulse": {
"url": "https://agent-api.pricepulse.hatch-capital.com/mcp",
"headers": { "Authorization": "Bearer pp_live_YOUR_KEY" }
}
}
}curl -s https://agent-api.pricepulse.hatch-capital.com/mcp \
-H "Authorization: Bearer pp_live_YOUR_KEY" \
-H "Content-Type: application/json" \
-H "Accept: application/json, text/event-stream" \
-d '{"jsonrpc":"2.0","id":1,"method":"tools/list"}'POST one JSON-RPC message per request. The server is stateless: it issues no session id and offers no server-initiated stream, so a GET returns 405.
03 Tools
The tools, and what they cost.
Each tool costs its price per call, listed below. A few tools split a bigger request into up to four calls and cost that many. A request too big for that, or one your balance or limits can’t cover, is refused before anything is charged.
Market data uses credits
| Tool | What it does | Credits |
|---|---|---|
pp_search_listings | Search live listings in a place (with dates, guests and filters). Returns a ranked page with bedrooms, rating and review count. | 3 a page |
pp_search_listings_by_geo | Find comparable listings around an address. | 3 a page |
pp_get_listing_detail | One listing in depth: title, host, photos and amenities. It carries no stay price; for what a listing charges on your dates, use pp_bulk_price_for_date. | 2 |
pp_get_listings | Several listings in one call: detail, calendar, review pace and live pricing. | 10 a call (up to 20 listings) |
pp_bulk_price_for_date | What each comp charges for a specific stay, including fees. | 10 a call (up to 20 listings); 2 for one listing |
pp_price_matrix | Price a set of listings across several stay windows at once. | 10 a call (up to 10 listings × 4 stays); a bigger grid is split into up to 4 calls |
pp_best_available | For each listing, the first bookable price from a list of candidate dates. | 10 a call (up to 20 listings) |
pp_nightly_snapshot | Night-by-night prices across a date range. | 3 a call (up to 5 listings, 7 nights) |
pp_bulk_listing_open_pricing | What each listing is asking on its open dates over the coming months. | 10 a call (up to 5 listings, 3 months) |
pp_bulk_calendar_summary | How many of each listing's nights are taken or unavailable, month by month. | 10 a call (up to 20 listings) |
pp_bulk_review_summary | Review count, rating and recent review pace. | 10 a call (up to 20 listings) |
pp_bulk_reviews | The full text of recent guest reviews. | 5 a call (up to 20 listings) |
pp_static_profile | Full amenity list, house policies and sleeping arrangements. | 10 a call (up to 20 listings) |
pp_market_cards | Refresh listings in search-result card form: beds, baths, badges, coordinates, photos. | 10 a call (up to 20 listings) |
pp_listing_media | Photos and how many each listing has. | 10 a call (up to 20 listings) |
pp_rank_probe | Where specific listings rank in a market search. | 10 a call (one page of search results) |
pp_rate_band | What open listings near you are asking for one stay: the range of nightly prices guests see and where your price sits in it. | 3 a call (up to 2 pages of search results) |
pp_comp_rate_grid | Your comps priced across several stays and read for you: an event weekend, weekly and monthly discounts, short-stay premiums, your open gaps, a year of weekends. | 10 a call (up to 10 listings × 4 stays); a bigger grid is split into up to 4 calls |
pp_market_pulse_verdict | “Is it me or the market?” How full your next two months are against how much of your comps’ calendars is taken, with one verdict. Needs your calendar connected. | 10 a call (up to 20 comps) |
pp_amenity_value | What an amenity (a hot tub, a pool) is worth per night near you, comparing similar homes with and without it. | 13 a call |
pp_comp_scorecard | How your reviews compare with your comps, category by category, and what guests praise at theirs but not at yours. | 10 a call (up to 20 listings); 20 with occupancy |
pp_rank_check | Where your listing shows up when a guest searches your market. | 10 a call (up to 3 pages of search results) |
pp_top_performers | What the highest-rated listings near you have in common: badges, amenities and minimum stays. | 10 a call (one market) |
Your own data free
| Tool | What it does |
|---|---|
pms_list_properties | Your properties from your connected property manager. |
pms_get_property | One of your properties in detail. |
pms_get_calendar | Availability (and rates, where your property manager provides them) for one of your properties. |
pms_get_bookings | Recent and upcoming bookings for one of your properties. |
pms_portfolio_snapshot | Every property at a glance: reserved, blocked and open nights, occupancy, open gaps and the next arrivals, counted for you. |
pricelabs_list_listings | Your PriceLabs portfolio and its settings. |
pricelabs_get_calendar_rates | PriceLabs recommended rates next to the live rates on your calendar. |
pricelabs_get_neighborhood_data | PriceLabs neighborhood comp data for one of your listings. |
memory_recall | A note you asked the PricePulse agent to remember. |
Your own-data tools need that system connected in your account (Integrations).
04 Spending & security
Spending limits and security.
How spend limits work
- Each app connected by signing in has its own daily limit of 200 credits.
- Each key has its own daily credit limit, set when you create it: 200 unless you choose another number, up to 2,000.
- Your account’s daily spending ceiling still applies on top, across Telegram, every app and every key.
- A request is refused if its price would take the app or key past its limit or the account past its ceiling, or if your balance can’t cover it. Refused requests are never charged.
- Every request is quoted before it runs and never charged more than that quote, so an app or key never goes past its limit or your balance.
- Days reset at midnight in your account’s time zone. Each app’s and key’s spend today is shown in your account.
Security
- Read-only: it can’t change prices, settings or schedules, whatever your assistant is told.
- Signing in happens on PricePulse’s own page, and nothing connects until you approve the app. The app never sees your password.
- It can’t pay for anything: credits are bought on a Stripe checkout page, and only you can pay.
- An app or key only ever sees your own account.
- Disconnect an app any time in your account; it stops working on the next request.
- We show a key once and store only a fingerprint of it. Treat it like a password, and the connector link too, since it contains the key. We keep the link out of our server logs.
- Revoke a key any time in your account; it stops working on the next request.
- Each key is limited to 60 requests a minute. We log which tool ran and what it cost, never what you asked.