MCP Docs problems and fixes

Run mcp-docs version in the environment where your client runs. If it cannot find the command, configure its absolute executable path or install an environment containing MCP Docs; a host installation does not make it available inside a container.

Check the counts with mcp-docs cli info. If there are no documents, install a release containing the collection and repeat the check. Restarting the same empty installation does not fetch pages.

Check that your client selects the docs backend. Local HTTP uses /mcp; channel HTTPS uses /mcp/docs. Correct the endpoint and reconnect; expect docs_list, docs_read and docs_search.

Check that the client sends a valid portal session cookie for the same hostname as the endpoint. Sign in for that channel and reconnect. If the cookie is present and access still fails, ask the portal operator to check authentication.

List the relevant pages and use an exact returned path, including the filename extension. If the page is absent, use a listed alternative or ask the service owner for a release that includes it; a local workspace edit does not change the installed collection.

Check the query and collection counts. Use a nonempty query with the product name or distinctive error phrase, then read the full page. Browse with docs_list when ranking is unhelpful; a high score does not guarantee that the guidance fits your task.

Check whether several clients are sending rapid requests. Reduce their request frequency and wait before retrying; repeated immediate retries increase contention.

Ask the operator to check memory usage and the termination reason. If the larger collection exceeds the service capacity, adjust capacity based on observed use or return to the previous release while investigating.