Veltra Activities
Search Veltra's catalog of tours, food and cultural experiences from inside a chat. One read-only tool, no sign-in, results render as a card grid — and booking happens on veltra.com, not in the connector.
Verified connector
Listed by Anthropic as a partner connector in its Connectors Directory.
Connection checked by Agentman on .
Anthropic states this reflects the level of review a connector received, not a security audit.
Connect Veltra Activities via MCP
https://ai.veltra.com/veltra/mcpWorks in any MCP-compatible client. In Agentman Studio it is one click — no config file to edit.
Veltra Activities Tools & Capabilities (1)
Search Veltra activities by keyword. Returns up to 5 best-selling matches per call, with prices, ratings, locations, and Veltra URLs. Catalog: strongest in Japan, with additional inventory across Southeast Asia, Hawaii, and other destinations. Language: results match the query language. English queries return English titles, Japanese queries return Japanese titles. If the matched language has no inventory for a query, results fall back to the other language so the list isn't empty. Query strategy: for a multi-theme question like 'food tours and cultural experiences in Tokyo', make ONE broad call per major theme — e.g. 'Tokyo food tour' plus 'Tokyo cultural experience' — rather than splitting into many narrow sub-queries. Each call already returns up to 5 best-sellers, so a few broad calls give a fuller, less fragmented set than many narrow ones. If the user asks a single themed question, one well-phrased call is enough. Phrasing: include a city plus a region or specific keyword for precision (e.g. 'Sendai Matsushima cruise', 'Kyoto Higashiyama tea ceremony'). Bare city names may surface popular tours globally if the city has limited Veltra inventory.
Read from the server on 2026-08-18, including each tool's own safety annotations.
Limits
- It cannot book. Search is the entire surface — one read-only tool, no reservation, payment, availability or cancellation call. Booking happens on veltra.com after you follow the link.
- Five results per call, with no pagination. The tool's own description caps each call at five best-selling matches, and no parameter asks for more or for the next page.
- One free-text parameter, no structured filters. There is no date, price, duration, category or destination field. Constraints live inside the query string, and
additionalProperties: falsecloses the input. - Coverage is uneven outside Japan. Veltra states the catalog is strongest in Japan. Its troubleshooting advises broadening a thin-region query to a country, and warns that niche interest queries may return nothing at all.
- A bare city name can mislead. The tool description warns that cities with limited Veltra inventory may surface popular tours from elsewhere instead.
- Language fallback can surprise you. When the matched language has no inventory, Veltra returns results in the other language rather than an empty list — so an English query can come back with Japanese titles.
- No card grid without MCP Apps. In a client that does not implement the widget extension, results degrade to a plain text list of titles, prices and links. Veltra says both presentations carry the same data.
- No prompts. The server neither declares nor implements the capability;
prompts/listreturns "Method not found". - No status page. Veltra states there is no separate status page for the connector at this time.
- No published rate limit. Neither the documentation nor the handshake states a request ceiling, so we make no claim about one.
- Queries reach Veltra's logs. Veltra's connector privacy page says search queries are forwarded to its internal catalog API where they may appear in standard server logs under normal operational logging.
Frequently asked questions
Can you book a Veltra activity through the connector?
No. The server exposes exactly one tool and it only searches. Veltra's own setup pages say you will sign in on veltra.com to book or reserve, and the result card's button is labelled View Activity rather than Book. The connector shortlists real, bookable experiences and hands you a link; the transaction happens on Veltra's website.
Does the Veltra MCP server need an account or a login?
No. We opened an anonymous handshake on 2026-08-18 and the server returned its tool definition with no credential and no authentication challenge. Veltra's setup pages state that no login screen appears and that the connector collects no account information. You only need a Veltra account at the point where you go to veltra.com and book.
What does Veltra receive when you search from a chat?
Your plain-text search query, and Veltra says nothing else. Its connector privacy page states the query is forwarded to Veltra's catalog API and that no account information, no personally identifiable information, no payment, location or device data is collected by the connector. Queries may appear in standard server logs under Veltra's normal operational logging.
Why does a search return only a handful of activities?
Because the server caps each call at five best-selling matches, which its own tool description states plainly. That is a design choice, not an error. The schema tells the model to make one broad call per theme rather than many narrow ones, so a multi-part travel question produces several five-result calls instead of one long list.
Why are results in the wrong language?
Result language follows your query language, not your client's locale. Ask in English for English titles, in Japanese for Japanese titles. Veltra's troubleshooting adds one wrinkle worth knowing: when the matched language has no inventory for a query, results fall back to the other language rather than returning nothing, so an English query can return Japanese titles.
Which destinations does the Veltra connector actually cover well?
Japan first. Both the live tool description and Veltra's own help site say the catalog is strongest in Japan, with additional inventory across Southeast Asia, Hawaii and other destinations. Veltra's troubleshooting advises broadening a query to a country rather than a neighbourhood when a thinner region returns nothing, which is the practical form of the same limit.
Why do Veltra results render as cards in some clients and plain text in others?
Because the card grid is an MCP Apps widget, and not every client implements the extension. The server publishes two HTML widget resources, one for Claude and one for the ChatGPT Apps SDK. Veltra states that older ChatGPT versions fall back to a plain text list of titles, prices and links, and that both presentations carry the same data.
Sources
- Veltra Activities connector help site (fetched 2026-08-18). Six pages: overview, setup for Claude, setup for ChatGPT, examples, troubleshooting, and privacy.
ai.veltra.compublishes norobots.txt(404) and nollms.txt, so no crawl restriction or machine index applied. · retrieved 2026-08-18 - Live MCP handshake against
https://ai.veltra.com/veltra/mcp—initialize,tools/list,resources/list,prompts/list,resources/templates/listandresources/readon both widget URIs, 2026-08-18. Anonymous, read-only; no tool was called. · retrieved 2026-08-18 - Anthropic Connectors Directory entry (snapshot 2026-08-16) · retrieved 2026-08-16
- VELTRA privacy policy (fetched 2026-08-18). The directory lists
https://www.veltra.com/privacy/, which redirects to the/en/path cited here. · retrieved 2026-08-18 - VELTRA terms and conditions (fetched 2026-08-18) · retrieved 2026-08-18
- VELTRA support — . Named by Veltra as the canonical contact point; the host returned 403 to our client on 2026-08-18, so nothing on it is cited here. · retrieved 2026-08-18
Use in Agentman
Connect once and your agents call these tools on their own — on a schedule, in a workflow, with nobody at the keyboard.
Open in Agentman StudioServer Info
- Category
- Travel
- Developer
- Veltra Activities
- Tools
- 1
- Domain
- ai.veltra.com
Using Claude Desktop or another MCP client? Setup docs — the connection URL above works anywhere.