> For the complete documentation index, see [llms.txt](https://support.sayprimer.com/primer/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://support.sayprimer.com/primer/troubleshooting/mcp-questions.md). # An MCP question won't answer What to do when a Primer MCP request takes long, stops answering, is declined, or works on the wrong organization. ## It's taking several minutes A request runs the same multi-step analysis as [Chat](/primer/chat/using-chat.md), so a few minutes is normal. Primer keeps working if your assistant stops waiting, and asking again picks up the same answer rather than starting over. If several requests in a row stall, wait a few minutes before asking again. ## Answers stopped coming Remove the connector in your assistant and add it again to sign in afresh — see [MCP](/primer/mcp/mcp.md). ## The answer is about the wrong organization A connection is scoped to the organization you signed in to and can't switch between them. Remove the connector and add it again, signing in to the organization you want. ## Primer declined the request Primer says so rather than guessing, and its reply says why — including when it can't run an audience. If it's something you expected Primer to do, email with what you asked. --- # 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://support.sayprimer.com/primer/troubleshooting/mcp-questions.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.