MCP Troubleshooting

Use this guide when a Remote MCP client cannot connect, search, read Calendar data or write.

Projection expired

Open Elasticnote while signed in and allow MCP synchronization to complete. MCP traffic by itself cannot keep an old projection alive.

Notebook missing

Open Settings → AI & MCP and confirm the notebook is selected for Remote MCP. Also confirm the OAuth grant itself includes that notebook.

Calendar is empty

Confirm the client was granted calendar.read and open Elasticnote so the local Calendar projection can synchronize. Cached Google/Microsoft entries also depend on a current Calendar provider cache.

Calendar only client asks for a notebook

A Calendar-only grant does not require a notebook. Reconnect and approve Calendar scopes without workspace scopes if notebook access is not needed.

Read works but write does not

Notebook Create/Edit and calendar.write require explicit OAuth scopes plus an eligible MCP write entitlement. calendar.write also requires calendar.read.

Calendar provider event cannot be edited through MCP

This is intentional. Calendar MCP writes currently target local Elasticnote Calendar events. Provider-managed Google/Microsoft events are normalized read-only MCP context and use the Calendar UI's separate provider write authorization.

Update conflict

Elasticnote uses optimistic content/event hashes. Re-read the current document or local Calendar event before retrying. The server will not silently overwrite a newer canonical version.

OAuth client rejected

Use a current standards-compliant MCP client and HTTPS client metadata/redirect URLs. Elasticnote rejects insecure or private-network Client ID Metadata Documents.

Still stuck

Revoke the client and reconnect, or purge/resynchronize MCP projections. Your canonical browser workspace and .calendar data are not deleted by either action.