> For the complete documentation index, see [llms.txt](https://help.supplyd.co/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://help.supplyd.co/mcp/manage-your-connection/troubleshooting.md). # Troubleshooting Resolve common Supply'd MCP connection, sign-in and data-access problems. ## The client says Supply'd does not implement OAuth * Confirm the server URL is exactly `https://mcp.supplyd.co/`. * Choose OAuth or automatic discovery, not an API key. * Remove any manually entered OAuth endpoints or client credentials unless Supply'd provided them. * Delete the incomplete connector and create it again. ## Supply'd keeps returning to the login page Sign in to `https://app.supplyd.co` in the same browser, then restart the connection from the AI client. Check that cookies and pop-ups are not blocked for Supply'd and the AI client. ## The authorisation request is invalid or expired Close the approval window and start again from the AI client. Do not refresh or reuse an old approval URL. Complete the new approval without leaving it open for an extended period. ## Approval succeeds but the client does not finish connecting Allow the browser to return to the AI client's callback page. Temporarily disable pop-up or navigation blocking for the two trusted sites, then retry. If your organisation enforces a browser content-security policy, ask its administrator to allow the client's OAuth return address. ## The connector is present but Supply'd is unavailable in chat * In ChatGPT, install the Supply'd plugin and select it with **@Supply'd** on a message that needs ERP data. * In Claude, enable Supply'd using **+ → Connectors**. * Start a new conversation after connecting. * Check whether your AI workspace administrator restricts custom connectors. * Disconnect and reconnect if the client was open while the connection was created. ## New capabilities are missing or calls fail after an update Some clients save the tool definitions from initial setup. Ask the workspace administrator to refresh or rescan Supply'd's tools and review any updated permissions or definitions. In ChatGPT, this is managed through the workspace's app or plugin controls. Start a new chat after the update. If refreshing is unavailable or does not help, disconnect and reconnect using `https://mcp.supplyd.co/`. Do not reuse an old approval URL. ## A product or other record cannot be found * Use the exact SKU, order number or returned record ID. * Include the product size or variant when names are similar. * Confirm the connection includes the required business area. * Confirm your Supply'd user can view the record in the relevant company and location. If a follow-up loses the earlier product, repeat its name or SKU rather than relying only on “this product”. ## A result is empty or incomplete Add a date range, status, location or exact reference. Large results may be shortened, so ask for a smaller period or a summary report. ## Access worked previously but now fails The connection may have expired or been revoked, or your Supply'd permissions may have changed. Disconnect and reconnect. If the issue remains, sign in to Supply'd directly to confirm your account access. ## Contacting support Provide Supply'd Support with: * the approximate time of the error; * the AI client and browser used; * the MCP server URL; * the safe error message and request ID, if shown; and * the business area and question you were trying to use. Never send passwords, access tokens, refresh tokens or full browser cookies. --- # Agent Instructions This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com. ## Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation by asking a question. Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters: ``` GET https://help.supplyd.co/mcp/manage-your-connection/troubleshooting.md?ask=&goal= ``` `ask` is the immediate question: it should be specific, self-contained, and written in natural language. `goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.