
Tixxly
io.github.TeamTixxlyPublished by GitHub account TeamTixxlyv1.0.7Updated Oct 24, 2026
Tixxly MCP server — connect AI agents to tours, experiences, and activities
Overview
Connects an AI assistant to Tixxly tours, experiences, and activities through a local MCP server.
- What you can do
- Tixxly is a local MCP server that links an AI assistant to the Tixxly platform for tours, experiences, and activities. It runs as a local process over stdio and is distributed as the npm package @tixxly-ai/travel-mcp. The registry description states it connects AI agents to tours, experiences, and activities, but no individual tools are listed in the available information.
- When to use it
- Consider it when you want an assistant to work with Tixxly tour, experience, and activity data as part of a travel-related workflow. It is a desktop-only local server, so it suits users running an MCP client on their own machine rather than a hosted environment.
- Requirements
- A local runtime able to run the npm package @tixxly-ai/travel-mcp over stdio, plus a Tixxly vendor API key supplied through the TIXXLY_API_KEY environment variable. The key is described as created from an admin dashboard with an mcp group. Desktop only; no web executable.
Installation
In SourceWeft
- Open Tixxly in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
This repository has no README.
Tools
0Version history
1- v1.0.7LatestSep 16, 2026
Score
25% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.
- License10 pts
Declare a license in the repository or the registry entry.