- Home
- Resources
- Integrations
- Novasol
Claude Novasol connectorWhat Claude can find on Novasol for your next trip.
The Claude Novasol connector exposes 1 tool. It reads the rental catalogue, 0 tools write, 0 stay undocumented. Below: what Claude searches for you across Europe, how to narrow a search, and why no booking ever happens inside the chat.
Verified Trustpilot reviews · AI, automation & growth agency
What changes when you plan a self-catering trip
You describe the trip the way you would to a friend: where, when, how many people, the budget, the sauna you refuse to skip. With the Novasol connector, Claude searches the publisher's holiday-home catalogue across 18 European countries and answers with a ranked carousel, right in the chat.
A shortlist from one message. search-properties returns individual bookable homes with name, location, price, review score, bedroom count and pet policy.
Adjust without starting over. Cheaper, closer to the coast, a different week, two more guests, more options, better rated: Novasol tells Claude to run the search again for each change like that, and the list refreshes. The tool handles stays of one night or more, and standout homes are highlighted so you can open their card straight away.
Start from a vague idea. Asking for "Scandinavia" mixes results badly, the publisher warns. The publisher's advice is to search one fitting country instead.
What Claude won't do here: book, pay, look for hotels, flights, car hire or package deals. It doesn't produce average prices either. Nothing runs by itself: no ping when a cottage frees up, Claude only searches while it is answering you. Scheduled monitoring belongs to an automation platform, covered in the Integrations hub.
The vocabulary, in one minute
Five words you will run into when you add Novasol to Claude.
- Connector
- The link you set up once between Claude and an outside service, so Claude can use it while it answers you.
- Tool
- One named capability a connector gives Claude. Claude decides on its own when to call it; the directory lists it by name.
- Authorization
- The service's own sign-in screen, where you grant the access Claude will use. Given once per person, and revocable.
- Approval
- The confirmation Claude waits for in the chat before an action that would change an account on your behalf.
- MCP
- The shared standard connectors are built on: it is what lets an assistant talk to a service outside itself.
Add the Claude Novasol connector in three steps
- 01
Find Novasol
In Claude's settings, open Customize, then Connectors, and look for Novasol in the list. On a Team or Enterprise workspace, an Owner or Primary Owner has to switch it on for the organization before members can connect.
- 02
Start the connection
Click Connect on its row and follow the window the service opens itself. If the link ever breaks, use Disconnect and connect it again. Access can also be withdrawn from the service's side.
- 03
Confirm the access
Read the authorization screen before you accept. The service shows it and decides what the access covers, not Claude. You can take that access back later the same way.
The Claude Novasol connector's single tool
Novasol gives Claude 1 tool: 1 that read your account, 0 that change something in it.
One card, on the read side: it queries the rental catalogue. The name stays exactly as Claude shows it.
- 1 read
What Claude reads (1)
1 toolOne tool that looks at listings and books nothing.
search-properties
Queries the Novasol catalogue for one destination and returns individual homes you could book, laid out as a ranked carousel. No averages, no price history: listings only.
What Claude asks before it acts
By default, Claude stops and asks for your go-ahead before every action it takes on an account for you, right when it matters.
No source describes a confirmation specific to search-properties, so the general rule applies as is. Claude works with your rights and nothing beyond them: what you can't reach in the service yourself, it can't reach either. On Team and Enterprise, workspace owners decide whether a member may let some actions through without being asked each time, and they can limit a connector for the whole organization, for instance keeping reads open and shutting writes.
Which plans include it
None of the 819 sheets in the official directory shows availability by plan. For Novasol, as for every other connector, that answer isn't published anywhere.
The general rule is public: remote connectors are open to all users on Claude, Cowork, Claude Desktop and mobile. On Team and Enterprise, an Owner or Primary Owner first enables the connector for the organization. For the current state, check the Novasol sheet in the official directory: it is the only place that shows it.
Where the Novasol connector stops
A connector isn't an automation: Claude calls the tool while it is answering you, and nothing runs while you're away.
By default, the sheet only exposes reading, which is an observed floor rather than a promise: an admin can open actions that appear on no public sheet. The partner badge is not a security audit, and Anthropic states on every sheet that it neither picks a publisher's tools nor vouches for how they behave. Only the publisher documents this connector; Claude's help center has no page on it. Other sheets the team has dug into sit in the Claude connectors hub.
Need help connecting Novasol to Claude?
A person reads every message.