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/documentation (the earlier /mcp/docs address has been removed). Correct the endpoint and reconnect; expect docs_list, docs_read and docs_search.

Check that your client sends Authorization: Bearer <access token> to the same channel's /mcp/documentation address; a token from another channel is rejected. Read the response error: add a missing header, copy a wrong-channel or incomplete value again from that channel’s Account, Access tokens page, or renew an expired/revoked token. Replace the saved value in every affected client; in Claude Code, remove the mait-docs entry and add it again with the correct header.

Check that you intended the fixed-header connection from Ask from your agent. Remove the connector and add it again: choose No sign in, and set the Authorization request header to Bearer, a space and the complete access token copied from the same channel. If browser sign-in is intended instead, use the separate sign-in address in the next section; do not combine that method with a fixed header.

Select Sign in in the portal’s Ask from your agent panel and use its channel-specific URL: https://connect.edge.mait.sh/mcp/documentation for Edge, https://connect.beta.mait.sh/mcp/documentation for Beta, or https://connect.mait.sh/mcp/documentation for Stable. Add the entry without a fixed Authorization header, choose Connect or Authenticate, then complete sign-in and consent. Return to the client and verify docs_list, docs_read and docs_search. If a fresh connection still fails, use the header method while reporting the channel, client and time without tokens or browser return URLs.

Read the response error: account_disabled needs support, feature_off means Docs access for your agent is turned off in Account, Features, and wrong_feature requires the docs access token. Correct the indicated condition before retrying; do not assume every 403 can be fixed by enabling a feature.

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.