Back to Browse

Tourpro MCP Server

Developer ToolsLow Risk10.0MCP RegistryRemote
Free

Server data from the Official MCP Registry

Tour management for tour managers, production teams, and touring crews. Free for teams up to 5.

About

Tour management for tour managers, production teams, and touring crews. Free for teams up to 5.

Remote endpoints: streamable-http: https://mcp.tourpro.app/mcp

Security Report

10.0
Low Risk10.0Low Risk

Valid MCP server (1 strong, 1 medium validity signals). No known CVEs in dependencies. Imported from the Official MCP Registry. 1 finding(s) downgraded by scanner intelligence.

74 tools verified · Open access · 1 issue found

Security scores are indicators to help you make informed decisions, not guarantees. Always review permissions before connecting any MCP server.

Permissions Found in Source Code

Found by scanning the linked source code. This listing connects to a hosted endpoint, so none of this runs on your machine: it describes what the server software does where it is hosted.

HTTP Network Access

Connects to external APIs or services over the internet.

How to Connect

Remote Plugin

No local installation needed. Your AI client connects to the remote endpoint directly.

Add this to your MCP configuration to connect:

{
  "mcpServers": {
    "app-tourpro-mcp": {
      "url": "https://mcp.tourpro.app/mcp"
    }
  }
}

Documentation

View on GitHub

From the project's GitHub README.

TourPro MCP server

mcptry

TourPro's public MCP server: tour management tools for AI clients over Streamable HTTP at https://mcp.tourpro.app/mcp.

Tour managers, production teams and touring crews can ask an AI assistant about their next show, pull a day sheet, check open advancing items, and manage events, tours and day notes — without opening the TourPro app.

Using it

  • Endpoint: https://mcp.tourpro.app/mcp (stateless Streamable HTTP, POST only)
  • Auth: OAuth 2.1 with PKCE against TourPro's Auth0 tenant. No API keys. Sign in with your own TourPro account; every tool call runs under your role and permissions on each tour.
  • Discovery: initialize, ping and tools/list are answered without a token so clients and directories can inspect the tool set before sign-in. tools/call requires the OAuth token.

Tools

Reads include list_my_tours, get_next_event, get_day_sheet, list_open_items, list_events, list_day_notes and ask_tourpro (grounded Q&A over a tour's data). Writes cover events, tours and day notes with the same permissions the app enforces. The full list: https://www.tourpro.app/docs/integrations/tools

Links

Source lives in TourPro's private monorepo; this repo holds the public registry metadata and docs for the server.

Reviews

No reviews yet

Be the first to review this server!