Skip to main content
Daysync runs a hosted MCP server. Connect it to an AI client and you can ask questions about your tours — and make changes — in plain language, without writing any code against the Integration API.

Connect Claude

claude.ai, Claude Desktop, and Claude Code.

Connect ChatGPT

ChatGPT developer mode.

Tool catalogue

Every operation, and the scopes that reveal them.

Example prompts

Things worth asking once you’re connected.

​
What you can do with it

The server covers essentially the whole Daysync feature set — tours and days, schedule items, venues, accommodation and rooms, guest lists, bulletins, tags, custom fields, contacts, files, the printable day sheet, and read-only chat history. In practice that means you can ask things like “what’s the load-in time in Melbourne?”, “add a press call at 2pm on the Sydney day”, “print me a day sheet for Friday”, or “which venues still have no capacity set?” and the client will make the calls for you.

​
It knows more than it advertises

The server holds 106 operations and advertises 25 of them as tools by default. That is deliberate: advertising all of them cost about 33,000 tokens of definitions before the client had read a word of your question, and near-neighbours made the choice ambiguous. Everything else is reached on demand through three discovery tools — list_capabilities → describe_operations → invoke_operation — with the same typed schema it would have had as a tool. Nothing was removed, and every tool name that ever existed is still callable by name. So if a capability seems to be missing, ask for it in plain language anyway: the client will find it. See the tool catalogue for the full list and for how to pin the old advertised surface with ?tools=all.

​
How it fits together

The MCP server is a client of the same Integration API documented on this site. It does not have its own data or its own permissions — every tool call becomes a REST call, authenticated as you.
Three separate things decide what a tool call can do:
1

The partner's scopes

What the connecting application is allowed to touch at all. Set on its credential. This is the real access boundary.
2

The scopes you consent to

Chosen by you on the consent screen at connect time. These decide which tools are visible in your client.
3

Your own role and membership

You only ever see and change what your Daysync account could see and change in the app. Connecting an AI client does not widen your access.
So a tool you can see is one you consented to; a tool call that succeeds is one your account was allowed to make.

​
What it will not do

  • Chat is read-only. The server can read channel and group-chat history, but cannot post, edit, or delete. 1:1 direct messages are never exposed — not in lists, not by ID. See Chat.
  • No credentials pass through your AI client. Your Daysync tokens are held server-side; the client only ever holds a token for the MCP server itself.
  • Nothing is shared between users. A connection is bound to one Daysync account, and whoami will tell you which.

​
Before you connect

You need a Daysync account that is a member of at least one tour. Everything else is handled by the OAuth flow — there are no API keys to copy, and nothing to paste into your AI client but the URL above.
Building your own MCP client, or want your own partner credential? See Apply for API Access. The endpoints behind every tool are documented under Endpoints.
Next: Connect Claude or Connect ChatGPT.