Connector cannot discover Tidyboard
- Confirm the MCP URL ends in /mcp and uses HTTPS.
- Open the protected-resource metadata URL on the same API host.
- Confirm metadata resource and authorization-server URLs are public and correct.
- Check server logs for status codes without logging authorization headers.
Sign-in or callback fails
- Confirm the Cognito issuer and hosted domain.
- Compare the client's callback URL with the exact registered value.
- Confirm authorization code with PKCE is enabled.
- Check the audience/resource and requested scopes.
- Retry with a fresh sign-in instead of reusing an expired token.
Tool returns forbidden or not found
Confirm the signed-in Tidyboard user belongs to the expected household and has permission for the requested record. A connector cannot elevate a user's normal Tidyboard access.