Remote MCP Overview

Elasticnote Remote MCP connects compatible AI clients to explicitly scoped Elasticnote data while your local-first workspace and Calendar remain canonical.

MCP endpoint

Use https://www.elasticnote.com/mcp as the remote MCP server URL. The protocol endpoint is not a web page; use Connect AI with MCP for the guided setup experience.

Local first architecture

Remote MCP is an optional Pro feature. Notebook access uses a temporary encrypted server projection of the notebooks you select. Calendar access uses a separate encrypted projection of your local Elasticnote Calendar plus normalized provider-cache entries. Remote MCP does not turn the Elasticnote account database into normal notebook or Calendar storage.

When backing storage is connected, local Calendar data remains canonical in the provider-neutral .calendar folder. Without backing storage, Calendar remains canonical in the browser. MCP never receives Dropbox, Google Drive, OneDrive, GitHub, Google Calendar or Microsoft Calendar credentials.

The projection expires after the configured inactivity window measured from the latest successful Elasticnote browser synchronization. MCP reads do not extend that lifetime.

Scopes

Notebook and Calendar permissions are independent. Notebook tools use workspace:search, workspace:read, workspace:create and workspace:write. Calendar tools use calendar.read and calendar.write. A Calendar-only grant does not require granting any notebook.

Tools

Notebook tools are listnotebooks, resolvenotebook, searchworkspace, getdocument, createdocument, updatedocument, appenddocument, movedocument, renamedocument and deletedocument. Kanban task tools are listtasks, createtask, updatetask and deletetask; task writes update the canonical .kanban.json board through the same conflict-safe document mutation path.

Calendar tools are listcalendarevents, createcalendarevent, updatecalendarevent and deletecalendarevent. Calendar writes currently target local Elasticnote Calendar events. They enter a pending mutation queue and are applied by an Elasticnote client to canonical browser/.calendar storage with conflict checks. Cached Google and Microsoft Calendar events are normalized for MCP reads but remain provider-managed and read-only through MCP.

Stable links

Notebook/item IDs and local Calendar event IDs are stable across ordinary Elasticnote operations. Results can include deep links that reopen the relevant notebook/item or /calendar?event=... location in Elasticnote.

Related guides

Continue with Connect Remote MCP, MCP Clients, AI Instructions for MCP, MCP Security & Privacy and MCP Troubleshooting.