Skip to main content
Daysync is listed in Claude’s connector directory. There is nothing to install and no URL to paste — find Daysync, click Connect, and sign in.

Open Daysync in the Claude connector directory

Jump straight to the Daysync listing on claude.ai.

​
claude.ai, Claude Desktop, and mobile

1

Open the Daysync listing

Use the direct link above, or in Claude go to Customize → Connectors, browse the directory and search for Daysync.
2

Click Connect

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.
3

Review the consent screen

You will see exactly which scopes Claude 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.
4

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.
Once connected on claude.ai, Daysync is available in Claude Desktop and the Claude mobile apps on the same account — no need to connect again.
Claude Team and Enterprise: an organization owner may need to allow Daysync for your workspace before members can connect it. If you can’t see the Connect button, ask your Claude admin.

​
Turning it on in a chat

Connectors can be toggled per conversation. If Claude doesn’t seem to know about your tours, open the tools / connectors menu in the chat input and make sure Daysync is switched on.

​
Claude Code

Claude Code uses the server URL directly:
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. For more ideas, see Example prompts.

​
Already using the custom connector?

Before the directory listing, Daysync was added as a custom connector pointing at https://mcp.daysync.com/mcp. That still works — it is the same server — but there’s no reason to keep both. To switch: remove the old custom connector under Customize → Connectors, then connect Daysync from the directory as above. Ask Claude to disconnect first if you want the old connection’s access revoked immediately.
Only needed if the directory listing isn’t available to you (for example, a workspace policy restricts it).
  1. In Claude, go to Customize → Connectors and choose Add custom connector.
  2. Paste https://mcp.daysync.com/mcp and name it Daysync. Nothing else needs configuring — the server advertises its own OAuth endpoints.
  3. Sign in and approve the consent screen as above.

​
Disconnecting

There are two ways, and they do slightly different things: Disconnecting Daysync under Customize → Connectors 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