GoVisit Tools

npx add-mcp 'https://govisit.ai/mcp'

GoVisit Toolkit

[

GoVisit is a travel platform that helps people and AI agents discover destinations, local businesses, and experiences. It brings together published destination and business profiles so travelers can explore what places offer and local businesses can make their services easier to find and understand.

Tools and resources for using GoVisit with AI agents and coding assistants, including Claude Code, Codex, GitHub Copilot, Cursor, and other Agent Skills-compatible tools.

This repository contains open-source tools, 22 portable read skills, native Claude Code/Codex packages, release tooling, and implementation resources for GoVisit. The website documentation explains each tool's inputs and interpretation limits.

Open-source tools

Tool	Purpose	Source and setup
Floating Chat	A floating chatbot optimized for travel and hospitality websites and A2A-compatible agents	tools/floating-chat

Each tool has its own dependencies, build, and deployment instructions. See tools/README.md for the directory conventions. Agent skills and native plugins below are installed separately from these applications.

Choose a package

Audience	Available package	Contents
All	govisit	All 22 public read skills, including documentation and catalog statistics
Travel Planner	govisit-travel-planner	18 destination, place, category, collection, and activity readers/searches
Destination	govisit-destination	13 skills to find and inspect destination profiles and their published inventory; Update destination is planned
Local Business	govisit-local-business	10 skills to find and inspect place profiles and their local context; Update place is planned

Audience packages overlap: the same canonical reader can be useful to a travel planner, a destination manager, and a local business. Choose All or any audience package you need. The current release reads public information without a GoVisit API key; it does not include editing workflows. An AI host may still request network/tool permission. Service limits and the Data Use License apply, and model usage follows your assistant's plan.

Install portable skills

For a three-step setup with one choice of AI assistant, follow the Installation guide. Install once, then use any included skill.

The npx skills installer requires Node.js 22.20 or later and npm. Its GitHub shorthand commands use the repository's default branch, main.

Run in your project and choose the target agent and installation scope:

npx skills add inhotel-io/govisit-toolkit --skill '*'

The portable skills are the shared route for compatible AI tools. For an explicit target, install all 22 skills for GitHub Copilot or Cursor:

npx skills add inhotel-io/govisit-toolkit --skill '*' --agent github-copilot
npx skills add inhotel-io/govisit-toolkit --skill '*' --agent cursor

Install the matching CLI before using those assistants from a terminal.

GitHub Copilot CLI (Node.js 22 or later):

npm install -g @github/copilot

Start it with copilot; on first launch, sign in with /login. Run copilot update to update it. GitHub also documents Homebrew, WinGet, and an install script in its Copilot CLI installation guide.

Cursor CLI (macOS, Linux, or Windows Subsystem for Linux):

curl https://cursor.com/install -fsS | bash
agent --version

On native Windows, run irm 'https://cursor.com/install?win32=true' | iex in PowerShell. Cursor updates automatically; run agent update to update it manually. See Cursor CLI installation.

Choose the command for your assistant; you do not need to install twice. See GitHub's skills guide and Cursor's skills guide for discovery and scope. The installer currently uses the shared project directory .agents/skills/ for both targets; their host-specific directories .github/skills/ and .cursor/skills/ are also options for manual installation.

For another AI tool, select it in the interactive installer or install complete skill directories in its documented Agent Skills location. The host must load SKILL.md and its references/contract.json, and have permission to make HTTPS requests to GoVisit. Model choice alone does not provide those capabilities. See the compatibility and verification record for the difference between installation checks and an exercised model conversation.

For a single skill and an explicit target:

npx skills add inhotel-io/govisit-toolkit --skill govisit-search-places --agent codex

The canonical files live under skills/govisit-*/. Names already include govisit-; keep the directory and SKILL.md name together without rewriting them. Manual downloads use the discovery index, which points to versioned release assets and their SHA-256 digests. Verify the original archive bytes before unpacking the complete package, including LICENSE and references. A collection archive is not a universally supported skill-upload format.

Install native plugins

Claude Code:

Install the Claude Code CLI first. Anthropic recommends the native installer for macOS, Linux, and WSL:

curl -fsSL https://claude.ai/install.sh | bash
claude --version

On Windows, use the official Claude Code installation guide for the PowerShell or Command Prompt installer. Then add the marketplace and install a plugin:

claude plugin marketplace add inhotel-io/govisit-toolkit
claude plugin install govisit-travel-planner@govisit-toolkit --scope project

The marketplace command uses the repository's default main branch.

Codex:

Install or upgrade Codex CLI with Node.js and npm before running these commands:

npm install -g @openai/codex@latest

codex plugin marketplace add inhotel-io/govisit-toolkit --ref main
codex plugin add govisit-travel-planner@govisit-toolkit

Use govisit@govisit-toolkit for All, govisit-destination@govisit-toolkit for Destination, or govisit-local-business@govisit-toolkit for Local Business. Native packages live under plugins/; their included skill files are generated from the canonical skills/ selection, and all resources remain inside the plugin root. A native Claude skill is namespaced, for example /govisit-travel-planner:govisit-search-places; portable skill invocation uses the host's own skill selector.

Codex reads each package's listing and composer icons from its plugin.json; the SVGs live in that package's assets/ directory. The Codex marketplace manifest currently has no marketplace-level icon field. Its GoVisit Toolkit brand SVG is kept at plugins/assets/marketplace.svg for use by surfaces that support one.

For destination and local business managers

Start by finding your own published entry. A destination manager can use govisit-search-destinations, then govisit-get-destination-overview and govisit-get-destination-section. A local business manager can use govisit-search-places, then govisit-get-place-overview, govisit-get-place-section, and govisit-get-place-visit-facts.

These skills are already included in the corresponding audience package and can also be installed individually. The same readers are reused across audiences. The planned govisit-update-destination and govisit-update-place skills will join those packages when their secure authoring workflows are implemented. Reading a public profile does not establish ownership or grant permission to update it.

First task

After installation, start a session if your host needs to refresh discovery:

Search GoVisit for places in Czechia where travelers can actively participate in immersive experiences such as regional festivals, traditional craft workshops, historical preservation sites, and local food traditions. Read the published profiles, explain missing evidence, and link the GoVisit sources.

An empty result does not prove absence, and published discovery facts do not prove live prices or availability. The example performs reads and makes no reservation.

Updates and diagnostics

To move a Codex marketplace from a version tag to the current GoVisit source, remove and re-add it at main, then install the selected package again. Existing plugin snapshots are updated by the final command:

codex plugin marketplace remove govisit-toolkit
codex plugin marketplace add inhotel-io/govisit-toolkit --ref main
codex plugin add govisit-travel-planner@govisit-toolkit

Use your audience package name in the last command. Re-adding an existing marketplace with a different --ref requires removing its old marketplace declaration first. main tracks ongoing changes; use a reviewed release tag when a stable, reproducible version is required.

Installed copies are snapshots. For portable skills, use npx skills check and npx skills update, or reinstall the selected complete package through your installer. Native users update the marketplace/plugin using their client's supported commands. Pin a reviewed release/commit for reproducible automation; GitHub Release archives are versioned, while a checkout of main can change.

Remove portable skills through npx skills remove; native users use claude plugin uninstall or codex plugin remove with the installed package ID. Confirm actual installed paths/versions in your client before removing anything.

If a task fails, check the package version, network access to GitHub release assets and govisit.ai, required arguments, and the response's error/freshness metadata. HTTP 429 requires respecting Retry-After. Never paste credentials or private business/travel data into a public issue.

For maintainers, see release preparation and verification.

Licensing

The GoVisit Toolkit's code, skills, scripts, schemas, documentation, and examples are licensed under the MIT License unless otherwise indicated. You can reuse, modify, redistribute, and commercially use these materials under that license. Preserve the required copyright and license notice when doing so.

Access to GoVisit-hosted search, public read APIs, WebMCP tools, and use of returned GoVisit Data are governed separately by the GoVisit Data Use License. The toolkit license grants no additional service capacity, data rights, or editing permissions. Third-party materials retain their identified licenses and notices.

Material or activity	Applicable terms
Toolkit code, skills, schemas, documentation, and examples	MIT, except explicitly identified third-party or separately licensed material
Hosted search, public read APIs, WebMCP access, and returned GoVisit Data	GoVisit Data Use License and applicable source-specific terms
Submitting recommendations or publishing content updates	Applicable service/submission terms and current account, resource, and role permissions
Third-party content	Its identified source terms; inclusion in a response does not make it MIT-licensed

These are separate scopes. The Data Use License is not an additional restriction on reuse of the MIT-licensed toolkit files. Conversely, including a client or schema here does not make the hosted service or its returned data MIT-licensed.

See Hosted services and data terms for the scope of each set of terms, attribution guidance, and handling of examples and submissions.

Responsible use

• Follow the documented interfaces, request limits, and any account-specific access conditions. Installing a skill does not grant backend permissions.
• Preserve data attribution, provenance, freshness, and source-license notices when using GoVisit responses, as required by the applicable terms.
• Use clearly labeled synthetic data in examples where possible. Identify the source and applicable terms for any separately licensed fixtures or media.
• Keep credentials, personal information, and confidential business data out of public issues, examples, and pull requests.