Support
Troubleshooting
Diagnose authentication, MCP discovery, API retries, uploads, and webhook delivery.
Verified against the implementation ·
MCP connection problems
| Symptom | Likely cause | Fix |
|---|---|---|
| 401 oauth_required | A REST API key was used for MCP | Remove the header and start the client OAuth flow |
| Browser never opens | The client did not follow OAuth discovery | Confirm OAuth support and inspect the WWW-Authenticate resource_metadata challenge |
| Authenticate is missing after reinstalling PrompTessor in Codex | The previous PrompTessor OAuth session is still stored on the shared Codex host | Run codex mcp logout promptessor, then codex mcp login promptessor or restart the client and select Authenticate |
| Tools list is empty | Consent lacks scopes or metadata is stale | Reconnect with required scopes and refresh/restart the client |
| Tools work but prompts/resources are absent | The client does not expose those MCP primitives | Use the equivalent tool directly or test with MCP Inspector |
| Connection times out | Wrong URL or blocked public HTTPS access | Use exactly https://mcp.promptessor.com/mcp and verify it is reachable |
REST API problems
- Use https://api.promptessor.com/v1, not internal /api/v1 routes on the main website.
- Confirm the Authorization header uses Bearer followed by the complete key.
- Call /capabilities and /models before enabling plan- or model-dependent features.
- Add Idempotency-Key to AI requests, but not to ordinary read requests.
- Log X-Request-Id from every response when contacting support.
- On 429, honor Retry-After or RateLimit-Reset and reduce concurrency.
Webhook problems
| Symptom | Fix |
|---|---|
| Signature mismatch | Verify timestamp.rawBody before parsing; remove only the v1= prefix |
| Endpoint rejected | Use a public HTTPS hostname; localhost, private addresses, and redirects are not accepted |
| Repeated deliveries | Return 2xx in under 10 seconds and deduplicate by delivery id |
| Old secret no longer works | A rotation invalidates the previous secret immediately |
| Test button unavailable | The endpoint must be enabled and the account must have an active paid plan |
Contact developer support
If the problem persists, submit the public support form and choose API & MCP. Include the X-Request-Id, UTC timestamp, endpoint or MCP client, HTTP status or error code, and a redacted request example.
Never send secrets
Do not include API keys, OAuth authorization codes, access tokens, refresh tokens, webhook secrets, cookies, or unredacted Authorization headers in a support request.