Skip to main content
The Daysync MCP server is a remote server, so there is nothing to install — you add a URL and sign in.

​
claude.ai and Claude Desktop

1

Open connector settings

In claude.ai, go to Settings → Connectors and choose Add custom connector.
2

Enter the URL

Paste https://mcp.daysync.com/mcp. Give it a name like Daysync. Nothing else needs configuring — the server advertises its own OAuth endpoints, so Claude discovers them automatically.
3

Sign in to Daysync

Claude opens the Daysync sign-in page. Sign in with the account whose tours you want to work with.You are asked to sign in every time you connect, even if you already have a Daysync session in that browser. That is deliberate: it makes it unambiguous which account the connection is bound to.
4

Review the consent screen

You will see exactly which scopes the application is asking for, in plain language — Tours · Read, Schedule · Write, and so on. Approve to finish.The scopes you approve decide which tools appear. See Authentication.
5

Confirm the account

Start a new chat and ask “which Daysync account am I connected as?”. The whoami tool answers with the email. Worth doing once — people with several Daysync accounts do occasionally bind the wrong one.

​
Claude Code

Add it as a remote MCP server:
Then run /mcp inside Claude Code and follow the authentication prompt. The same browser sign-in and consent screen applies.
Claude Code enumerates MCP servers at session start. If you add the connector while a session is already running it will not appear — start a new session.The same applies after Daysync ships new tools: a running session keeps the tool list it loaded at start. Your calls still reach the current server, but you will not see new tools until you begin a fresh session.

​
Checking it works

Ask for something small and read-only first:
List my Daysync organizations.
If that returns your orgs, the connection, consent, and your account access are all working.

​
Disconnecting

There are two ways, and they do slightly different things: Removing the connector in Claude stops Claude using it, but asking Claude to disconnect — or revoking in Daysync — is what actually invalidates the stored access.
Next: Authentication · Tool catalogue · Troubleshooting