Fixes for common problems connecting or using the Chatofy MCP server in Claude, Cursor, ChatGPT, and command-line clients.
| Error Code | Common Cause | Recommended Fix |
|---|---|---|
| 401 Unauthorized | Missing or expired Bearer token in the Authorization header, or expired browser OAuth session. | In Claude Desktop, click Sign in again. In Cursor or Windsurf, verify your API key in Settings → API Keys. |
| 403 Forbidden | Your organization plan does not include API Access, or you attempted a write action while connected via ?writes=false. | Check with your workspace owner to ensure your plan includes API Access, or remove ?writes=false from your connector URL. |
| 429 Rate Limit | Exceeded the per-minute API request quota allocated to your organization plan. | Wait 60 seconds before issuing more requests. Enterprise organizations can request elevated rate limits through Billing. |
Cause: Make sure you are using the single canonical URL https://app.chatofy.in/api/mcp.
Fix: When adding the custom connector, ensure you select Sign in now and Register automatically. Chatofy natively implements RFC 7591 dynamic client registration.
Cause: Your browser redirected to an unauthorized hostname.
Fix: In Claude Desktop, remove the Chatofy connector from Customize → Connectors and re-add it using URL https://app.chatofy.in/api/mcp.
Run these terminal commands to verify the Chatofy MCP endpoint is healthy and reachable:
curl -i -X POST https://app.chatofy.in/api/mcp -H "Content-Type: application/json" -d '{"jsonrpc":"2.0","id":1,"method":"tools/list"}'curl https://app.chatofy.in/.well-known/oauth-protected-resource/api/mcp
curl https://app.chatofy.in/.well-known/oauth-authorization-server