MCP troubleshooting
Find the failed boundary before repeating the setup.
The endpoint returns 405
Nestlybot uses stateless Streamable HTTP. An authenticated GET can return 405 because the endpoint does not open an SSE channel. Opening the URL in a browser is not an MCP connection test. Use a client to initialize and invoke the server.
Authorization succeeds but tools are missing
Check that the client supports this transport and authorization flow. Refresh its server metadata and test a new chat or session. Verify the tools discovered by tools/list. A saved grant alone does not prove tool availability.
A read is refused
Check the current account and granted scopes with get_capabilities. A Thing reference does not confer access. Test list_spaces before a write; an empty real list is valid. Reauthorize only when the grant or scopes actually need changing.
A prepared plan did not create anything
A prepared plan is a preview. Review it and execute only the authorized steps. Inspect the run and its receipts. A proposed schedule is not proof that background execution is active, and an accepted request is not proof of a completed outcome.
Ask for help safely
Email [email protected] with the client, the failed stage and the non-secret Nestlybot request reference. Omit credentials, access tokens, private URLs and document content. Return to MCP setup for the verification sequence.