livesync-workers

MCP server · npm · ★ 16 · graded 2026-10-20Source linked

Self-hosted LiveSync-compatible backend for Obsidian with search and MCP, for Cloudflare Workers

No outside reports on file

livesync-workers reads local files and connects to external service APIs; restrict its folder reach, network access, and credentials before installing.

Based on public adoption and transparency signals as of Oct 19, 2026. Our opinion, not a code audit or security guarantee.

Was this verdict for Livesync Workers helpful?

What it can access

  • Local filesReads & writes local foldersREVIEW
  • Command executionNo shell command runner notedLOW
  • Network reachConnects to outside service APINOTED
  • CredentialsRequires API key or tokenREVIEW
  • Package sourcenpm (livesync-workers)PUBLIC

Inferred from this listing’s public package details and description. Check the project’s source before installing.

Install

npx -y livesync-workers

All setup options ↓

About Livesync Workers

Livesync Workers is an MCP server focused on Web & browsing and Files & documents: Self-hosted LiveSync-compatible backend for Obsidian with search and MCP, for Cloudflare Workers.

It is published on npm as livesync-workers and hosted on GitHub at odiak/livesync-workers (16 GitHub stars, 50 weekly npm downloads, last repository push on 2026-10-13). Based on its public metadata, its operational scope includes: reads local files, connects to outside service api.

Setup

Check these steps against the project’s own instructions before running anything.

Run livesync-workers with --ignore-scripts in claude_desktop_config.json or .cursor/mcp.json:

json
{
  "mcpServers": {
    "livesync-workers": {
      "command": "npx",
      "args": ["-y", "--ignore-scripts", "livesync-workers"]
    }
  }
}

Why this grade

DD — High risk signals

Signal-based grade (1/7 points): public source code. This reflects adoption and transparency, not a code review.

Popularity and upkeep

34/100
GitHub stars
16
Weekly npm downloads
849
Listing last refreshed
2026-10-28

These are public popularity signals, not a maintenance check. Look at the repository’s commit history and open issues.

Security reports

No reports found for this package in our research (last checked 2026-10-29).

Check a specific version →

Risks to watch for

  • Local file read access: Reads local documents or database files. Point it only at the specific files needed for the task so sensitive workspace files remain out of reach.
  • External API & account scope: Connects to third-party service APIs. Use a dedicated, least-privilege token scoped only to the workspaces or repositories this tool needs.
  • Dependency & version pinning: Distributed via npm (livesync-workers). Pin an exact release version or commit SHA rather than floating tags so upstream updates are reviewed first.

How to lower the risk

Least-privilege permissions

  • Give it access only to the specific folders, accounts or projects it needs, never your whole drive or admin account.
  • Use a separate, limited API key or login just for this tool so you can switch it off without affecting anything else.

Network isolation

  • Run it on a work computer or sandbox account, not one holding personal or company-sensitive data.
  • If your IT team can, limit which websites and services it is allowed to contact.

Monitoring

  • Check its activity history or logs weekly at first, and look at what it changed or sent.
  • Turn on alerts for new logins or unusual usage on any account it connects to.

Red flags to watch for

  • It asks for more access than its job requires, or prompts you to paste passwords.
  • It suddenly updates with new owners, or starts contacting unfamiliar websites.

Questions

How do I install Livesync Workers?

Run npx -y livesync-workers in your terminal, or add the server entry to your claude_desktop_config.json or .cursor/mcp.json as shown in the Setup section on this page. Full setup docs and environment variables are in github.com/odiak/livesync-workers.

Are there security reports about Livesync Workers?

No reports found for this package in our research (last checked 2026-10-29). Livesync Workers currently holds Grade D (High risk signals) based on public adoption and transparency signals. Key risk areas to watch include local file read access:, external api & account scope:, dependency & version pinning:.

Is Livesync Workers actively maintained?

Livesync Workers has 16 GitHub stars and 849 weekly npm downloads, with its latest repository commit pushed on 2026-10-13. Our directory data was last refreshed on 2026-10-28. Check recent commit activity, release tags, and open issues at github.com/odiak/livesync-workers before pinning it in production.

What are alternatives to Livesync Workers?

You can compare Livesync Workers side by side with other Search, Obsidian MCP servers in the Related tools section on this page, or use the Compare tool on AgentArmorHQ.

README badge and team notes

Maintain or use Livesync Workers? Show its live grade in your GitHub README, docs site, or run a check from the terminal before you install.

AgentArmorHQ Risk Grade D for Livesync Workers

GitHub README Markdown:

markdown
[![AgentArmorHQ Risk Grade for Livesync Workers](https://agentarmorhq.com/api/badge/odiak-livesync-workers)](https://agentarmorhq.com/skills/odiak-livesync-workers)

HTML embed:

html
<a href="https://agentarmorhq.com/skills/odiak-livesync-workers"><img src="https://agentarmorhq.com/api/badge/odiak-livesync-workers" alt="AgentArmorHQ Risk Grade for Livesync Workers" height="20" /></a>

Terminal check:

terminal
curl -fsSL https://agentarmorhq.com/api/cli | node --input-type=module - check "odiak-livesync-workers"

Share with your security lead

Need sign-off to use livesync-workers? Copy this note for Slack, a ticket or a pull request.

### AgentArmorHQ Security Review Memo: livesync-workers
- **Listing URL:** https://agentarmorhq.com/skills/odiak-livesync-workers
- **Type:** App connector
- **Risk Grade:** Grade D (High risk signals)
- **Outside Security Advisories on File:** 0
- **Public Adoption:** 16 GitHub stars, 849 weekly npm downloads

#### Permission & Blast-Radius Signals
- **Local files:** Reads & writes local folders
- **Command execution:** No shell command runner noted
- **Network reach:** Connects to outside service API
- **Credentials:** Requires API key or token
- **Package source:** npm (livesync-workers)

#### Recommended Hardened Setup
- **Command:** `npx -y --ignore-scripts livesync-workers`
- **Controls:** Pin an exact version in `.mcp.json`, scope access to a single workspace folder, and use a least-privilege read-only token where supported.

_Based on public adoption and transparency signals as of Oct 19, 2026. Our opinion, not a code audit or security guarantee._

Key facts

Type
App connector
Publisher
odiak
Source code
github.com/odiak/livesync-workers
Install command
npm install livesync-workers
Est. context load
~850 tokens / turn (~5 tool schemas, 0.43% of 200k context)
Popularity
16 GitHub stars, 849 weekly npm downloads
Last updated
2026-10-28
Last graded
2026-10-20

Community

Discussions for Livesync Workers

Ask questions or share configuration tips. Governed by our Community Rules & Terms.

No posts match this filter yet.

Be the first to ask a question or share a working tip.

Was this listing for Livesync Workers helpful?

Check before you install, in Claude

Your assistant answers Block, Review or No known issues for any package before it installs it.

Get this check inside Claude