Claude Veltra Activities connectorWhat Claude can find in the Veltra catalog for you.
The Claude Veltra Activities connector exposes 1 tool. It reads the public catalog, 0 tools write, 0 are undocumented, and no Veltra account is involved. Below: what a search returns, where booking really happens, and the limits of the catalog.
Verified Trustpilot reviews · AI, automation & growth agency
What changes when Claude can search Veltra
You describe the trip to Claude and it searches Veltra's catalog of tours, food experiences and cultural activities itself. Each answer carries prices, ratings and links to the activity pages, so a planning chat ends with options you can actually book.
Shortlist experiences by theme. Ask for food tours in one city and searchActivities returns up to 5 best-selling matches, each with its price, rating, location and Veltra link.
Cover several themes in one plan. For a trip mixing food and culture, Veltra recommends one broad search per theme rather than many narrow ones, and Claude can run them back to back while it answers.
Search in English or Japanese. Results follow the language of the query: English searches bring English titles, Japanese searches bring Japanese ones, and Veltra documents no other language.
What the connector does not do matters as much. Booking happens on veltra.com, not inside the conversation, so Claude hands you a link rather than a reservation. Veltra states that no account and no login are needed, so there is no Veltra profile of yours for Claude to read. And the tool only runs while Claude answers you: no alert fires when a new tour appears. Hands-off workflows of that kind belong to automation platforms, gathered in the Integrations hub, which do another job rather than the same one better.
Five terms in one minute
The Claude words used on this page, briefly explained.
- Connector
- A link added once between Claude and an outside service, so Claude can use that service while it replies to you.
- Tool
- A named capability the connector hands to Claude. Claude decides by itself when to call it, and the directory shows each one by name.
- Authorization
- The sign-in screen a service shows when it needs one, where you grant access to Claude. Many connectors have it; this one, per Veltra, does not.
- Approval
- The confirmation Claude asks for before an action that changes an account, displayed right in the conversation when it is needed.
- MCP
- The common standard behind connectors: it is what allows an assistant like Claude to exchange with an outside service such as Veltra.
Add Veltra Activities to Claude in three steps
- 01
Open the connector list
In Claude's settings, go to Customize, then Connectors, and look up Veltra Activities. On a Team or Enterprise workspace, an Owner or Primary Owner has to enable the connector before members can use it.
- 02
Add it from its row
Click Connect on the Veltra Activities row. Veltra states that no account and no login are needed, so there is no Veltra sign-in to complete. If something breaks later, Disconnect and add it again.
- 03
Ask about a destination
Start a conversation about a trip. Claude picks the tools it needs on its own while it answers, so you never call the search by name; phrasing the request with a city and a theme is enough.
The one search tool
Veltra Activities gives Claude 1 tool: 1 that read your account, 0 that change something in it.
A single tool, on the reading side. Its name stays exactly as Claude displays it.
- 1 read
What Claude reads (1)
1 toolOne tool that searches the public Veltra catalog and books nothing.
searchActivities
Looks up Veltra activities from a keyword and returns up to 5 best-selling matches per call, each with its price, rating, location and link to the Veltra page. You get a shortlist to compare, not a booking.
What Claude asks before acting
By default, Claude stops and asks before each action it carries out on an account for someone. The question appears in the conversation at the right moment.
Here there is no Veltra account for Claude to act on: the connector works without login, and the only tool searches a public catalog. The organization rules still apply. On Team and Enterprise workspaces, owners decide whether members may let some actions through without a prompt each time, and they can limit what a connector may do for everyone, a choice no member overrides from a personal account.
Which plans it works on
Not one of the 819 sheets in the official directory states plan availability. Per connector, this information is simply not published.
The rule that is published applies to every connector: remote connectors are open to all users on Claude, Cowork, Claude Desktop and mobile, and on Team and Enterprise an Owner or Primary Owner enables a connector for the organization first. The connector's sheet in the official directory shows its current state. What this page says about Veltra comes from Veltra alone; no Claude help article covers it.
What this connector will not do
A connector is not an automation. Claude runs the search while it answers, so nothing happens when prices change or a new tour is listed.
A tool list showing only reading is an observed floor, never a guarantee: an administrator can open actions that appear on no public sheet. The directory's partner badge is not a security audit, and Anthropic says on every sheet that it neither picks the tools a publisher exposes nor guarantees they behave as described. Add what comes from a publisher you know. For scheduled or event-based flows, the Integrations hub covers the automation route.
Need help connecting Veltra Activities to Claude?
A person reads every message.