Uplisting for AI agents
Uplisting manages vacation rental properties, covering availability, bookings, and calendars, used by hosts and property managers running short-term rentals. Connect it once through Arc0, and your agent, or Claude, ChatGPT and Cursor, can use it through one MCP endpoint, limited to what each user approved.
What agents do in Uplisting.
Search availability across properties
Check open dates across listed properties for a given date range, a read-only search.
List upcoming property bookings
Pull upcoming and past bookings as a read-only report.
Confirm before updating a calendar
Check with the user before changing a property's calendar, since it affects what guests can book.
10 Uplisting actions, graded by risk.
Every Uplisting action is tagged read, write or destructive, so one policy covers the whole app and new actions inherit the right default.
read
7Look things up. Allowed by default.
- uplisting.get_calendarGet Calendar
- uplisting.get_propertyGet Property
- uplisting.list_bookingsList Bookings
- uplisting.list_webhooksList Webhooks
- uplisting.list_propertiesList Properties
- uplisting.get_current_accountGet Current Account
- uplisting.search_availabilitySearch Availability
write
2Create and change things. Allow, or ask the user first.
- uplisting.create_webhookCreate Webhook
- uplisting.update_calendarUpdate Calendar
destructive
1Delete, cancel or archive. Ask first, or deny outright.
- uplisting.delete_webhookDelete Webhook
Uplisting in three steps.
- 01Your users connect UplistingThey add their Uplisting api key on Arc0 Connect, under your brand. It goes straight into the vault.
- 02You set the rulesReads run, writes like “create Webhook” can wait for the user, and “delete Webhook” can be denied outright.
- 03Any agent can actYour agent calls Uplisting through the Arc0 SDK or MCP, and so can Claude, ChatGPT and Cursor. Every call lands on the audit log.
await arc0.policies.set('uplisting', { read: 'allow', write: 'ask', // create_webhook destructive: 'deny', // delete_webhook }) # Claude Code: the same connection, one URL $ claude mcp add --transport http arc0 \ https://mcp.arc0.ai/u/u_8f2
How Uplisting connects.
Users add their Uplisting api key on Arc0 Connect. It is encrypted in the vault, never shown to the model, and each user can rotate or revoke it at any time.
The same Uplisting connection serves your agent over MCP and your own backend over REST and the proxy, so a user connects once. How Arc0 handles credentials →
- AUTH
- API key
- CREDENTIALS
- Per-tenant encrypted vault
- MODEL SEES
- Results only, never credentials
- AUDIT LOG
- Every call, on every plan
Use Uplisting from any agent.
Uplisting and Arc0, answered.
Can I use Uplisting with Claude, ChatGPT or Cursor?
Yes. Connect Uplisting to Arc0 once, then add your Arc0 MCP URL to Claude, ChatGPT, Cursor, Claude Code or any other remote-MCP client. Each assistant only gets the Uplisting actions you allow.
How do users connect Uplisting?
Users add their Uplisting api key on Arc0 Connect. It is encrypted in the vault, never shown to the model, and each user can rotate or revoke it at any time.
Which Uplisting actions can my agent take?
10 in total: 7 read, 2 write and 1 destructive, such as “create Webhook”. Your policies decide which of them each agent may call.
Can I stop my agent from deleting things in Uplisting?
Yes. Actions like “delete Webhook” are graded destructive. Set destructive actions to deny, or to ask so the user approves each one, and blocked calls still show up on the audit log.
Can my own backend call Uplisting too?
Yes. The same Uplisting connection is available over REST and through the Arc0 proxy, so your product and your agent share one connection per user.
Plug Uplisting into your agent.
Your users connect Uplisting once, under your brand. Your agent gets 10 actions behind your policies, with every call on the record.
Free to build · MCP + REST · Audit log on every plan