> ## Documentation Index
> Fetch the complete documentation index at: https://docs.daysync.com/llms.txt
> Use this file to discover all available pages before exploring further.

# MCP Troubleshooting

> Fixes for the problems people actually hit with the Daysync MCP server.

<AccordionGroup>
  <Accordion title="A tool I expect isn't there" icon="magnifying-glass">
    Almost always one of three things.

    **You didn't consent to its scope.** Tool visibility is decided by what you approved at connect time. Disconnect and reconnect, and approve the scope you need. [More on consent](/mcp/authentication).

    **Your session predates the tool.** AI clients cache the tool list from the moment a session starts. If Daysync shipped new tools after you opened the chat, start a **new** chat or session. Your existing calls still reach the current server — you just can't see the new tools.

    **The application doesn't hold that scope.** The partner credential bounds everything; consenting to a scope it doesn't have grants nothing. You'll see `403 INSUFFICIENT_SCOPE` if a call gets through. Nothing to fix client-side.
  </Accordion>

  <Accordion title="It's connected to the wrong Daysync account" icon="user-xmark">
    Ask **"which Daysync account am I connected as?"** to confirm — that runs `whoami`.

    If it's wrong, ask the client to **disconnect**, then reconnect. You'll be asked to sign in, and that's where you pick the right account. The consent screen also has a **Switch account** link.

    This happens because the sign-in used for connecting is a separate session from app.daysync.com — being signed in to the web app doesn't decide which account the connector binds to.

    <Note>
      **Settings → Integrations** in the web app only lists connections bound to **your** account. A connection on the wrong account won't appear there, which is exactly why the in-client `disconnect` tool exists.
    </Note>
  </Accordion>

  <Accordion title="It keeps asking me to sign in" icon="arrow-rotate-right">
    Being asked once **per connect** is normal and deliberate — it makes the bound account unambiguous.

    Being asked repeatedly during normal use is not. That means the stored session could not be refreshed. Reconnecting resolves it. If it recurs within the same day, [get in touch](https://help.daysync.com) with the rough time it happened.
  </Accordion>

  <Accordion title="A call fails with 403" icon="ban">
    Two different 403s, with different fixes:

    `INSUFFICIENT_SCOPE` — the **application** lacks the scope. The message names what's missing. For the whole-tour read this is common, because it needs the read scope for all six resources it returns; see [Scopes](/scopes#endpoints-that-need-more-than-one-scope).

    Any other 403 — **your Daysync account** lacks access to that tour or organization, or your role doesn't allow the change. The MCP server never widens what your account can do. Check your role in the app.
  </Accordion>

  <Accordion title="A chat request returns 404" icon="comment-slash">
    If you asked for a **direct message**, that's expected and final. 1:1 DMs are never exposed — they're filtered from every list and refused by ID. Channels and group chats work normally. See [Chat](/endpoints/chat).

    Otherwise, check chat is enabled for the tour (`is_chat_enabled`) and that you're a member of the conversation.
  </Accordion>

  <Accordion title="Responses are truncated, or it gives up on a big tour" icon="scissors">
    Large reads can exceed what a client will hold. Narrow the request:

    * Ask for a single day or a date range rather than the whole tour.
    * For the whole-tour read, the client can pass `dayIds` and per-resource limits.
    * Chat messages are capped at 100 per call and page by cursor — ask for "the next page" to continue.
  </Accordion>

  <Accordion title="A write says it worked but I can't see the change" icon="eye-slash">
    Check the **visibility** of what was created. Items created through the MCP default to visible to everyone on the tour; if the request specified a restricted audience, only those people (and admins) see it.

    Also confirm you're looking at the same tour and day — with similar day names it's easy to check the wrong one. Ask the client to read the item back by ID.
  </Accordion>

  <Accordion title="The connector won't add at all" icon="plug-circle-xmark">
    Check the URL is exactly `https://mcp.daysync.com/mcp` — including the `/mcp` path.

    Custom connectors are a paid-plan feature in both Claude and ChatGPT, and in ChatGPT they need developer mode enabled. If the option isn't there, that's the reason.

    In Claude Code, remember connectors are enumerated at session start — run `/mcp` in a **new** session after adding.
  </Accordion>
</AccordionGroup>

## Still stuck

[Contact support](https://help.daysync.com) with:

* which client (claude.ai, Claude Code, ChatGPT, other)
* the output of `whoami`
* roughly when it happened, and what you asked
* the exact error text if there was one

***

See also: [Authentication](/mcp/authentication) · [Tool catalogue](/mcp/tools) · [Errors](/errors)