🔍 Overview
If your ws_bulk_send_message MCP call is consistently returning an HTTP 403 error inside Website Studio — even when all other MCP calls are working correctly — you are likely experiencing a JWT authentication issue that affects how the bulk message tool connects to your project. This article explains what causes the error, how to identify it, and the steps to resolve it.
⚠️ What Triggers This Error
The HTTP 403 error on ws_bulk_send_message is typically caused by one or more of the following:
- Expired or invalid JWT token: The authentication token used by the MCP layer has expired or was not correctly passed to the bulk send endpoint.
- Project-level permission mismatch: The MCP session credentials are not aligned with the specific Website Studio project you are targeting.
- False failure reporting: In some cases, the message delivery may have actually succeeded, but the tool incorrectly reports a 403 failure due to a response-handling bug that has since been resolved.
- Broken MCP tool initialisation: If create_project encountered an error earlier in your session, subsequent tools — including ws_bulk_send_message — can inherit a broken authentication state.
✅ How to Resolve the 403 Error
- Refresh your MCP session. Log out of the Search Atlas platform completely, then log back in. This forces a new JWT token to be issued and clears any stale authentication state tied to your current session.
- Re-open your Website Studio project. Navigate back to your project from the Website Studio dashboard rather than resuming from a cached or bookmarked URL. This ensures the MCP tools reinitialise with the correct project context and fresh credentials.
- Retry the ws_bulk_send_message call. After re-entering the project, trigger the bulk send action again. In many cases, the 403 resolves immediately after the session is refreshed.
- Verify the message was not already delivered. Due to the false-failure reporting bug (now resolved), your messages may have been sent successfully despite the 403 error appearing. Before re-sending, check your project's message history or the destination records to avoid duplicate updates.
- Check for create_project errors earlier in your session. If you attempted to create a new project before the 403 appeared and received an error, start a new session entirely. A failed create_project call can corrupt the authentication context for all MCP tools that follow in the same session.
🔄 What Was Fixed on Our End
Our engineering team has shipped several fixes related to this issue:
- The JWT authentication flow for ws_bulk_send_message and other Website Studio MCP tools has been corrected to prevent token mismatch errors.
- The create_project MCP tool, which was broken and contributing to downstream 403 failures, has been repaired.
- False failure reporting on successful ws_bulk_send_message deliveries has been resolved — the tool now accurately reflects whether a message was sent.
If you encountered this error before these fixes were deployed, refreshing your session as described above should be sufficient to restore full functionality.
🩺 Special Note for Healthcare and Data-Sensitive Projects
If you are using Website Studio to manage critical records — such as physician profiles, patient-facing directories, or clinical data — we recommend confirming delivery success in your project's data view before re-triggering a bulk send. This prevents duplicate entries and ensures data integrity, particularly in cases where the 403 error was a false negative and the update had already been applied.
🚫 Common Mistakes to Avoid
- Do not retry ws_bulk_send_message repeatedly in the same broken session. Multiple retries without refreshing the session will not resolve the 403 and may create duplicate processing attempts.
- Do not assume data was not updated. As noted above, the error may have been cosmetic. Always check your records first.
- Do not use a bookmarked deep link to re-enter a project after a session error. Always navigate from the main dashboard to ensure a clean initialisation.
💬 Still Seeing the Error?
If you have followed all the steps above and the ws_bulk_send_message MCP call is still returning HTTP 403, our team can investigate your specific project and session logs. If you need further assistance, open the chat widget in the bottom-right corner of the platform and type human teammate to be connected with a member of our team.