AI Instructions for MCP

Remote MCP can provide consistent Elasticnote-specific guidance across compatible AI clients.

Context hierarchy

For notebook tools, effective context is built from Account AI Instructions, then Notebook AI Instructions, then relevant document metadata. Notebook guidance can specialize account-level guidance for one workspace.

Examples include preserving citations in a research notebook, keeping generated summaries under a particular folder, or preserving command output in an operations notebook.

Calendar context

Calendar tools expose normalized event/task fields required for the requested operation. Calendar scope does not itself grant notebook content. A Calendar event may contain stable workspace/note identifiers, but a client still needs the corresponding workspace authorization to read notebook content.

Guidance is not authorization

AI Instructions are untrusted guidance for the model. They do not grant permission. OAuth scopes, notebook grants, Calendar scopes, supported operation types and server-side validation remain the security boundary even if a note, event or instruction says otherwise.

Portable notebook guidance

Notebook AI Instructions are stored with portable notebook metadata so they follow the notebook through Elasticnote's normal local-first/backing-provider model. Account instructions are account preferences and are projected to MCP only when the feature is enabled.