TourSync MCP Server

Section 01What is MCP?

The Model Context Protocol (MCP) is an open standard for giving AI models a uniform way to reach external data sources and tools. Instead of writing custom integration code, an AI assistant connects to an MCP server and gains a defined set of actions it can call.

The TourSync MCP server exposes your account's data and tools through that standard interface — so any MCP-compatible AI application can read from and act on your account on your behalf, safely scoped to the permissions you grant.

Section 02Server details

There are two ways to connect, depending on your client. Claude connects to a dedicated endpoint over one-click sign-in. Everything else — Cursor, Windsurf, n8n, custom agents — connects to the original endpoint with a token.

• Claude endpoint
  https://services.leadconnectorhq.com/mcp/anthropic/v2
• Token endpoint
  https://services.leadconnectorhq.com/mcp/ — everything else
• Transport
  HTTP Streamable
• Auth — Claude
  One-click sign-in. Nothing to store or rotate; you pick the permissions on the consent screen.
• Auth — token clients
  Bearer token via the Authorization header, plus your account locationId (can also be supplied in a prompt).

Section 03Authentication

Two paths, depending on your client:

• Claude — one-click sign-in (recommended) No token. Add the Claude endpoint as a connector, sign in, and approve the permissions you want to grant. The connection is scoped to one account, respects your user role (Claude can't do anything you couldn't do yourself), and there's nothing to store or rotate. Jump to the Claude walkthrough.
• Cursor, Windsurf, n8n, custom agents — token These authenticate with a Private Integration Token (PIT) you generate inside your account. Create one, grant it the scopes you need, and pass it as a bearer token — steps below.

Generate your token

1. In your TourSync account, go to Settings → Private Integrations.
2. Create a new integration and select the scopes you want the AI assistant to have (see Section 05).
3. Copy the generated token — it starts with pit-. Store it securely; treat it like a password.

Configuration example

Desktop clients like Claude and Cursor connect through the mcp-remote bridge. Here's the config block — paste in your own token and account ID. Full Claude Desktop walkthrough →

{
  "mcpServers": {
    "toursync": {
      "command": "npx",
      "args": [
        "mcp-remote",
        "https://services.leadconnectorhq.com/mcp/",
        "--header",
        "Authorization: Bearer YOUR_TOKEN_HERE",
        "--header",
        "locationId: YOUR_LOCATION_ID_HERE"
      ]
    }
  }
}

Section 04Available tools

The token endpoint exposes the 36 focused tools below — across contacts, conversations, calendars, opportunities, payments, content, and account data. Each maps to a single account action the assistant calls by name, and the Scope column shows the permission it needs (grant these in Section 05).

Section 05Required scopes

The 25 scopes to select when you create your token, grouped to match the tools above. Each matches the picker label exactly — search the identifier (e.g. contacts.readonly) and tick it.

Contacts

• View Contacts — contacts.readonly
• Edit Contacts — contacts.write

Conversations & messages

• View Conversations — conversations.readonly
• View Conversation Messages — conversations/message.readonly
• Edit Conversation Messages — conversations/message.write

Calendars

• View Calendar Events — calendars/events.readonly

Opportunities

• View Opportunities — opportunities.readonly
• Edit Opportunities — opportunities.write

Account

• View Locations — locations.readonly
• View Custom Fields — locations/customFields.readonly

Payments

• View Payment Orders — payments/orders.readonly
• View Payment Transactions — payments/transactions.readonly

Social posts

• View Social Media Posts — socialplanner/post.readonly
• Edit Social Media Posts — socialplanner/post.write
• View Social Media Accounts — socialplanner/account.readonly
• View Social Media Statistics — socialplanner/statistics.readonly

Blogs

• View Blog List — blogs/list.readonly
• View Blog Posts — blogs/posts.readonly
• View Blog Authors — blogs/author.readonly
• View Blog Categories — blogs/category.readonly
• Check Blog Post Slug — blogs/check-slug.readonly
• Create Blog Post — blogs/post.write
• Update Blog Post — blogs/post-update.write

Email templates

• View Email Templates — emails/builder.readonly
• Create, Update & Delete Email Templates — emails/builder.write

Section 06Connecting a client

Claude connects over one-click sign-in and is covered first. Cursor, Windsurf, n8n, and custom agents use the token endpoint — those follow.

Claude — one-click (Claude.ai, Claude Desktop, Claude Code)

No token, no Node.js, no config file. You add the Claude endpoint as a connector and sign in.

1. In Claude, open Settings → Connectors and choose Add custom connector (labels vary slightly by version).
2. Paste the Claude endpoint as the URL: https://services.leadconnectorhq.com/mcp/anthropic/v2
3. Click Connect, then sign in to the account you want to connect — one connection = one account. The sign-in screen is branded LeadConnector, the platform TourSync runs on; that's expected.
4. On the consent screen, tick the permissions to grant. Read-only lets Claude look things up; add write access to let it make changes. Grant less now, come back for more later.
5. Approve, and you're back in Claude with your TourSync tools live under the tools (🔨) icon.

Claude Code (terminal) — add it in one line, then run /mcp and choose Authenticate:

claude mcp add --transport http toursync https://services.leadconnectorhq.com/mcp/anthropic/v2

Cursor, Windsurf & manual setups (token)

Clients that don't use one-click sign-in connect to the token endpoint through a small local bridge, mcp-remote, which runs on Node.js and attaches your token for you.

1. Install Node.js (v18 or newer) from nodejs.org — the LTS build is fine. This gives you npx, which runs the bridge.
2. Open your client's MCP config (Cursor: Settings → MCP; Claude Desktop, if you prefer the manual route: Settings → Developer → Edit Config).
3. Paste in the toursync block below. If you already have other MCP servers, add it inside the existing "mcpServers" object rather than duplicating it.
4. Swap YOUR_TOKEN_HERE and YOUR_LOCATION_ID_HERE for your own (see Where to get these below), then save.
5. Fully restart the client. Your TourSync tools appear under its tools menu.

{
  "mcpServers": {
    "toursync": {
      "command": "npx",
      "args": [
        "mcp-remote",
        "https://services.leadconnectorhq.com/mcp/",
        "--header",
        "Authorization: Bearer YOUR_TOKEN_HERE",
        "--header",
        "locationId: YOUR_LOCATION_ID_HERE"
      ]
    }
  }
}

Where to get these

• Your token
  In your account, go to Settings → Private Integrations, create an integration with the scopes you need (Section 03), and copy the token — it starts with pit-. Paste it after Bearer .
• Your account ID
  This is your locationId. Grab it from your browser's address bar while you're in the account — it's the value right after /location/ in the URL — or find it under Settings → Business Profile.

On Windows, if the token isn't recognised, spaces inside args can get mangled — see the mcp-remote docs for the environment-variable workaround.

If your tools don't appear

• Fully quit and reopen Claude Desktop Press ⌘Q (macOS) or close it from the system tray on Windows — closing just the window won't reload the config. MCP servers only load on a fresh start.
• Check the JSON is valid A single stray comma or brace stops the whole file loading. Paste it into a JSON validator first — the config in Section 03 is a known-good starting point.
• Confirm Node.js is installed Open Terminal (or Command Prompt) and run node -v — you should see v18 or higher. If not, install it from nodejs.org and restart Claude.
• Tools load but calls fail? Your token is probably missing a scope. Regenerate it with the scopes in Section 05, then paste the new token into the config.

n8n

1. Add an MCP Client node and set the URL to https://services.leadconnectorhq.com/mcp/.
2. Select HTTP Streamable transport (requires n8n v1.104+).
3. Configure Header Auth with an Authorization: Bearer pit-… header.
4. Pass your locationId via the system prompt or the user message.
5. Select the TourSync tools you want available in the workflow.

LangGraph agent

Point any MCP adapter at the endpoint with the same two headers. Example using the LangChain MCP adapter:

import asyncio
from langchain_mcp_adapters.client import MultiServerMCPClient
from langgraph.prebuilt import create_react_agent

async def main():
    client = MultiServerMCPClient({
        "toursync": {
            "url": "https://services.leadconnectorhq.com/mcp/",
            "transport": "streamable_http",
            "headers": {
                "Authorization": "Bearer pit-your-token-here",
                "locationId": "your-account-id",
            },
        }
    })
    tools = await client.get_tools()
    agent = create_react_agent("your-model", tools)
    response = await agent.ainvoke({
        "messages": [{"role": "user", "content": "Give me all my contacts"}]
    })
    print(response)

if __name__ == "__main__":
    asyncio.run(main())

Section 07What you can build

• Contact management by chat Retrieve, update, and create contacts from natural language. Tag and segment guests for a campaign without leaving the conversation.
• Conversational messaging Search threads by keyword or status and send replies. Wire it into a chatbot for triage and auto-responses.
• Multi-step automation Chain actions in one instruction — tag a new booking, send a welcome message, and drop them into a pipeline stage.
• Payment intelligence Pull order details and transaction history on demand to feed reporting or reconcile revenue.

Section 08Roadmap

• ✓ One-click sign-in for Claude — shipped
• One-click sign-in for Cursor, Windsurf & more clients
• Expanded tool coverage across the account
• TourSync-native tools (bookings, manifests, platform sync)

Want early access or help wiring the MCP server into your stack? Book a call and we'll get you set up.