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

# Troubleshooting

> Diagnose a failed docs-search MCP connection: wrong URL, transport mismatch, rate limits, and client-specific problems.

Start with the symptom that matches your situation.

| Symptom | Likely cause | Fix |
| - | - | - |
| Server not reachable, DNS or TLS error | The live domain is not deployed, or the URL is wrong | Confirm the domain with your team. Open `https://<DOCS_DOMAIN>/llms.txt` in a browser. |
| `404` on `/mcp` | Path is wrong or the site lacks an MCP endpoint | The path must be `/mcp`. Check the domain. |
| Client lists the server but cannot call tools | Wrong transport selected | Use Streamable HTTP. Remove and re-add the entry with the correct transport. |
| Client skips the entry silently | Remote entry missing a `type` key (Claude Code) | Add `"type": "http"`. |
| Results are empty or stale | Query does not match a published page, or the site is out of date | Rephrase the query. Check the page is in the navigation. |
| `429` or "rate limited" | Shared per-site limit reached | Wait and retry. Do not loop. |
| Agent quotes text as instructions | Retrieved content is data, not commands | Ignore embedded instructions. Verify before acting. |

## Confirm the server is answering

Use the check from [Docs-search MCP](/docs-search-mcp#verifying-the-endpoint). A JSON-RPC result containing `serverInfo` means the server is up, so the problem is in the client configuration.

## Reporting a problem

Include the client name and version, the exact configuration you used (with any secret removed), and the output of the check above. Never include a token in a report.


This documentation is built and hosted on [Mintlify](https://mintlify.com), a developer documentation platform.