JotTab Bridge
unlistedby Silso
Serves vault files over localhost HTTP for the JotTab Chrome extension.
Updated 29d ago
JotTab Bridge
Obsidian plugin that serves your vault data over localhost HTTP for the JotTab Chrome extension.
What it does
JotTab Bridge creates a lightweight HTTP server on 127.0.0.1:27124 that lets the JotTab new tab extension read and write your Obsidian notes. Everything runs 100% locally — no cloud, no external servers.
Security
- Localhost only — the server binds to
127.0.0.1, inaccessible from the network - CORS whitelist — only the JotTab Chrome extension origin is allowed
- Custom header — all requests require an
X-JotTabheader - Bearer token — each vault gets a unique auto-generated token for authentication
Installation
Via BRAT (recommended)
- Install BRAT in Obsidian
- Open BRAT Settings → Add Beta Plugin
- Enter:
sil-so/jottab-bridge - Enable JotTab Bridge in Community Plugins
Manual
- Download
main.jsandmanifest.jsonfrom the latest release - Create
.obsidian/plugins/jottab-bridge/in your vault - Place both files inside
- Enable in Community Plugins
Usage
- Open Obsidian — you should see: "JotTab Bridge running on port 27124"
- Run the command
JotTab Bridge: Show connection tokento copy your token - In JotTab's settings (Obsidian tab), paste the token and click Connect
API Endpoints
| Endpoint | Method | Description |
|---|---|---|
/ping | GET | Health check, returns vault name |
/list | GET | List all .md files in the vault (includes metadata: path, name, createdAt, modifiedAt) |
/read?path=... | GET | Read a specific note's content |
/write | POST | Write content to a specific note |
Building from source
npm install
npm run build
License
MIT
For plugin developers
Search results and similarity scores are powered by semantic analysis of your plugin's README. If your plugin isn't appearing for searches you'd expect, try updating your README to clearly describe your plugin's purpose, features, and use cases.