elemenote-mcp
v0.2.0
Published
MCP server + localhost bridge — connect AI IDEs to Elemenote in the browser. Stdio MCP + HTTP sync. https://elemenote.io
Maintainers
Readme
elemenote-mcp
Beta — APIs and behavior may change. Pin a version in your MCP config if you need reproducible setups.
Elemenote (elemenote.io) is an in-browser annotation widget. elemenote-mcp is the MCP server plus a localhost HTTP bridge so tools in Cursor (and other MCP clients) can read and update annotations on the tab where the widget runs. The widget’s Ai Settings panel assumes this process is up and the bridge is reachable from the page.
Development workflow — not production infrastructure. Run the CLI on your machine while you work (
npx elemenote-mcp). It listens on 127.0.0.1 and is meant for local dev and internal use, not as a multi-tenant or public backend for your product.
Summary
Run
No global install (typical for MCP):
npx elemenote-mcp
# non-interactive:
npx --yes elemenote-mcp@latestGlobal CLI:
npm install -g elemenote-mcp
elemenote-mcpStdio MCP + local HTTP bridge for the browser.
MCP config
Cursor / Claude Desktop–style (field names vary by host):
{
"mcpServers": {
"elemenote": {
"command": "npx",
"args": ["-y", "elemenote-mcp@latest"]
}
}
}Optional env:
| Variable | Purpose |
|----------|---------|
| ELEMENOTE_MCP_BRIDGE_PORT | One port only (default 7432). |
| ELEMENOTE_MCP_BRIDGE_FALLBACK | 1 or true — try 7432, then 7434, 7436, … (legacy). |
With a global install: "command": "elemenote-mcp", "args": [].
Bridge (short)
- 127.0.0.1, default port 7432 (unless
ELEMENOTE_MCP_BRIDGE_PORTis set). GET /— healthGET /events— SSEPOST /sync— browser posts annotation payload
Keep a tab with the Elemenote widget open while using MCP tools.
License
Released under the MIT License. The full text is included in the tarball.
