Skip to main content

TourLife MCP Server

TourLife provides a Model Context Protocol (MCP) server that enables AI assistants to interact directly with your tour data. MCP is an open standard that allows AI tools like Claude, ChatGPT, Cursor, VS Code and other MCP-compatible applications to securely access external data sources.

MCP Endpoint​

The MCP server is available at:

https://api.tourlife.rocks/mcp

This URL is all you need to connect. You don't have to create or copy an API token.

Authentication​

The MCP server supports the standard MCP authorization flow, based on OAuth 2.1. When you add TourLife to your AI assistant, it will:

  1. Open a browser window to app.tourlife.rocks. Log in if you aren't already.
  2. Show a Connect to TourLife screen with the name of the application, the account you're signed in with, and what it will be allowed to do:
    • Read: view your projects, events, guests and other tour data
    • Write: create and change events, guests and other tour data
  3. Click Allow to connect, or Deny to cancel. You're then sent back to your AI assistant.
caution

Only click Allow if you started connecting the application yourself. The Connect to TourLife screen shows where you'll be sent after allowing access. Check that it matches the application you're using.

After connecting, your AI assistant stays signed in and renews its access in the background. If it isn't used for 90 days, you'll be asked to sign in again.

Managing Connected Applications​

Each connected application appears as an API token in Settings → API Settings in your personal profile, named after the application. To disconnect an application, delete its token there. The application will ask you to sign in again the next time it tries to access TourLife.

Setting Up Claude​

To connect Claude (claude.ai or Claude Desktop) to TourLife:

  1. Go to Settings → Connectors
  2. Click Add custom connector
  3. Enter the following details:
    • Name: TourLife MCP
    • URL: https://api.tourlife.rocks/mcp
  4. Click Continue, then Connect, and allow access in the browser window that opens
Add custom connector dialog with the name TourLife MCP and the URL https://api.tourlife.rocks/mcp filled in

Setting Up Claude Code​

Run the following command:

claude mcp add --transport http TourLife https://api.tourlife.rocks/mcp

Then run /mcp inside Claude Code, select TourLife and choose Authenticate to sign in.

Setting Up ChatGPT​

To connect ChatGPT to TourLife, use ChatGPT on the web:

  1. Go to Plugins
  2. Click the plus button, then Add custom MCP server
  3. Enter the following details:
    • Name: TourLife
    • Server URL: https://api.tourlife.rocks/mcp
    • Authentication: OAuth
  4. Review the risk warning, select I understand and want to continue, then click Create as a plugin
  5. Find the TourLife plugin in your personal plugins or in the workspace where you created it, install it, and allow access in the browser window that opens

ChatGPT asks you to confirm before it changes anything in TourLife.

note

Custom MCP servers aren't available on every ChatGPT plan, and some plans only allow reading data. If you don't see Add custom MCP server, or can't make changes, check OpenAI's overview of plans or ask your workspace admin.

Setting Up Cursor​

To connect Cursor to TourLife:

  1. Open Cursor and go to Settings → MCP
  2. Click Add new MCP server, which opens your mcp.json file
  3. Add the following configuration:
{
"mcpServers": {
"TourLife": {
"url": "https://api.tourlife.rocks/mcp"
}
}
}
  1. Save the file and click Connect next to the TourLife server to sign in

Setting Up VS Code​

To connect GitHub Copilot in VS Code to TourLife, add the following to .vscode/mcp.json in your workspace, or run MCP: Add Server from the Command Palette:

{
"servers": {
"TourLife": {
"type": "http",
"url": "https://api.tourlife.rocks/mcp"
}
}
}

VS Code will ask you to sign in the first time the server starts.

Other MCP Clients​

Most MCP clients that support remote servers only need the endpoint URL and handle the sign-in automatically.

If your client doesn't support MCP authorization, you can connect with a personal API token instead:

  1. Log into TourLife at app.tourlife.rocks
  2. Navigate to Settings → API Settings in your personal profile
  3. Create a new API token
  4. Configure your client to send the header Authorization: Bearer YOUR_API_TOKEN

For clients that only support local servers, you can use mcp-remote. This requires Node.js on your machine:

{
"mcpServers": {
"TourLife": {
"command": "npx",
"args": ["mcp-remote", "https://api.tourlife.rocks/mcp", "--header", "Authorization:${AUTH_HEADER}"],
"env": {
"AUTH_HEADER": "Bearer YOUR_API_TOKEN"
}
}
}
}

Keep your API token secure. Anyone with the token can access your data.

Available Capabilities​

Once connected, your AI assistant can help you with:

Projects​

  • List all projects you have access to
  • Get details for specific bands or tours

Events​

  • Query upcoming and past events
  • Get detailed event information including venue, times, and status
  • Create new events

Guests​

  • List guests for any event
  • Add new guests to guest lists
  • Update guest details and access types
  • Remove guests from events

Contacts​

  • Access venue and event contacts
  • Add and manage contact information

Roster​

  • View who's attending each event
  • Update attendance status

Flights & Transport​

  • Check flight bookings for events
  • Review ground transportation details

Files​

  • Access event-related documents and files

Example Prompts​

Here are some things you can ask your AI assistant once connected:

  • "What shows do I have coming up this month?"
  • "Add Maria Garcia as a backstage guest for the London show on April 15th"
  • "Who's on the roster for our next festival appearance?"
  • "What are the flight details for the Berlin event?"
  • "Show me the contact information for the Amsterdam venue"

Troubleshooting​

Connection Issues​

  • Ensure you have an active internet connection
  • Check that the URL is exactly https://api.tourlife.rocks/mcp
  • If your AI assistant keeps asking you to sign in, check whether its connection was deleted in Settings → API Settings, then connect again
  • When using an API token, verify it is correct, hasn't expired, and that the header starts with Bearer

Sign-in Issues​

  • "This authorization request has expired": the sign-in has to be finished within 10 minutes. Start connecting again from your AI assistant.
  • No browser window opens: make sure your client supports MCP authorization, or use an API token instead
  • If you clicked Deny by accident, start connecting again from your AI assistant

Permission Errors​

  • Make sure your TourLife account has access to the projects you're trying to query
  • Connected applications and API tokens have the same permissions as the user who created them
  • Some actions need Write access. Check that it was granted when connecting, or that your API token has the write scope.

Need Help?​

If you have questions about the MCP server or need assistance with your setup, reach out to us at info@tourlife.rocks.