MCP Clients and Compatibility

Elasticnote exposes one standards-based Remote MCP endpoint rather than separate backends for individual AI vendors.

Certified vs compatible

Certified means Elasticnote has tested a named product surface and documented its setup. Compatible means a standards-compliant MCP client should be able to use the same endpoint even when Elasticnote has not published a product-specific guide.

Client products change independently. A company logo does not imply that every plan, desktop app, web app, API or agent surface supports the same MCP permissions.

Server URL

https://www.elasticnote.com/mcp

The public MCP Connect page carries the current compatibility notes. Product-specific documentation is published only after that exact surface passes live certification.

Client neutral data model

Elasticnote does not change notebook or Calendar semantics based on the AI vendor. Compatibility workarounds, if required, stay at the protocol boundary. Workspace grants, Calendar scopes, conflict checks and local-first storage rules remain client-neutral.