Connect Remote MCP

Connect a compatible AI client to Elasticnote without creating an Elasticnote API key.

1. Enable Remote MCP

Sign in to an eligible Pro account and open Settings → AI & MCP. Enable Remote MCP. Select notebooks only when you want notebook tools; Calendar can be authorized independently.

2. Synchronize

Keep Elasticnote open long enough for the enabled MCP projections to report a current synchronization state. Notebook content is projected only from selected notebooks. Local Calendar events/tasks are projected separately from the browser/.calendar model. Only real Elasticnote browser synchronization refreshes the projection lifetime.

3. Add the server to your client

Use:

https://www.elasticnote.com/mcp

Choose OAuth when your MCP client asks how to authenticate. Elasticnote uses PKCE.

4. Review consent

Confirm the client name and redirect destination, then approve only the scopes you need. Notebook permissions and notebook selection are separate from calendar.read / calendar.write. Calendar write automatically depends on Calendar read.

5. Verify

For notebooks, ask the client to list or search an approved notebook. For Calendar, ask it to list events in a bounded date range. Local Calendar results can carry Elasticnote deep links.

Calendar write behavior

Calendar MCP writes target local Elasticnote events only. They become pending mutations until an Elasticnote client validates and applies them to canonical browser/.calendar storage. Google and Microsoft Calendar entries visible through the provider cache remain read-only through MCP, even if two-way provider sync is enabled elsewhere in Elasticnote.

Disconnect

Open Settings → AI & MCP to revoke a client, disable Remote MCP or purge the temporary projections. Revoking MCP does not delete your canonical browser workspace, .calendar data or normal backing-provider data.