Troubleshooting

MCP server won't start

"PROFER_API_URL is required"

The MCP server needs environment variables. Make sure your MCP config includes them:

{
  "env": {
    "PROFER_API_URL": "https://your-project.supabase.co/functions/v1",
    "PROFER_API_KEY": "your-api-key"
  }
}

"Failed to start Profer MCP server"

Check that:

Node.js 18+ is installed
The profer package is accessible (npx profer mcp should work)
Environment variables are set correctly

Publishing fails

"Unauthorized" (401)

Your PROFER_API_KEY doesn't match what's configured in the Supabase edge function secrets. Verify:

The key in your MCP config matches the PROFER_API_KEY secret in Supabase
There are no extra spaces or line breaks in the key

"HTML too large" (413)

HTML content is limited to 5 MB. If your agent generates very large content, ask it to be more concise or split into multiple pages.

"Duplicate question ID"

Each question must have a unique id. If you see this error, the agent generated two questions with the same ID. Ask it to use distinct IDs.

Feedback issues

Feedback not appearing

Check that:

The reviewer actually clicked "Submit feedback"
The page ID is correct when calling get()
The Supabase edge functions are deployed and running

Status not updating

Status only auto-updates when approve-type questions are present. If your questions are all text or choice, the status stays awaiting_feedback.

Invalid answer errors

Answers are validated against the question schema:

approve must be "yes", "no", or "needs_changes"
choice must be one of the defined options
multi must be an array of defined options
text must be a string

Webhook issues

Webhook not firing

Verify webhook_url was set when publishing (include it in the publish() call)
Check that the URL is valid HTTPS
Webhook failures are non-blocking — check your server logs

Webhook fires but nothing happens

Check your webhook endpoint:

Does it accept POST requests?
Does it parse JSON bodies?
Check for the event: "feedback_received" field in the payload

Supabase issues

Edge functions return 500

Check Supabase dashboard → Edge Functions → Logs for error details. Common causes:

Missing SUPABASE_SERVICE_ROLE_KEY (should be auto-set)
Database migration not applied
Table structure mismatch

Page shows "Page not found"

The page ID might not exist. Verify:

The ID format is correct (PF-XXXXX)
The page was successfully published (check the publish() response)
The Supabase project has the correct tables

Troubleshooting

On this page