joplin-mcp-server

MCPattested
v2.3.3io.github.jordanburkeUnknownUpdated 1mo agonpmGitHub

Search, read, create, edit and sync Joplin notes and notebooks via a headless Joplin sidecar.

Works in
ClaudeCursorCopilotGemini

Inferred from the transports this listing declares (stdio). A client not listed here hasn’t been ruled out — it just isn’t something Forge can confirm.

Attested build
A verified provenance attestation binds this artifact to the listed repository. Nobody has claimed the listing yet — this proves where the code was built, not who stands behind it.
1mo agoLast update
Reads these credentials
  • JOPLIN_TOKENAPI keyoptional

    Joplin API token, for external mode only (see JOPLIN_HOST). Sidecar mode manages its own token and ignores this.

  • JOPLIN_SYNC_PASSWORDAPI keyoptional

    Sync password; the secret key for the s3 target

Declared by the author in the official MCP registry. Forge does not store, broker, or ever see these values — the config below is scaffolded with placeholders you fill in locally.

Package
Authorio.github.jordanburke
LicenseUnknown
Version2.3.3
Sourcenpm+mcp-registry
Trust Status
A
85/100Trusted
✓Listed in Forge index+10/10
✓Identity verified · attested build+20/20
—Ed25519 publish signature+0/5
→ Included automatically when the publisher runs `forge publish`
—Domain verification+0/5
→ Publisher: host /.well-known/forge.json on the package homepage with { "publisher": "<github-login>" }
✓npm Trusted Publishing (Sigstore)+5/5
—npm maintainer match+0/5
→ Publisher: add the verified GitHub login to the npm package's maintainers (npm owner add <login>)
✓CVE scan · clean+30/30
✓Static analysis · clean+20/20
Paste into Claude Code, Cursor, or any AI assistant to fix all gaps
StatusIdentity verified
PublisherUnverified
SignatureUnsigned
Domain—
Provenance✓ Sigstore-verified · 4017d3b
Dependencies60 resolved · 3 with advisories
Tool surface12 tools · 4 privileged
Security scan⚠ Warnings (4)v2.3.3 · 4d agoHow well does this scan work?
EvalsNone
IndexedAug 31, 2026

Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.

Tools

12 tools · 4 privileged
Statically extracted from the published packagev2.3.3 · 4d ago

Read out of the source npm actually ships, at scan time. The package was never executed. Tools registered dynamically at runtime, or hidden inside bundled or minified code, can be missed — so this is a floor on the tool surface, not a complete census of it.

list_notebooksRetrieve the complete notebook hierarchy from Joplin

Retrieve the complete notebook hierarchy from Joplin

No input schema was published for this tool.

search_notesSearch for notes in Joplin and return matching notebooks

Search for notes in Joplin and return matching notebooks

No input schema was published for this tool.

read_notebookRead the contents of a specific notebook

Read the contents of a specific notebook

No input schema was published for this tool.

read_noteRead the full content of a specific note

Read the full content of a specific note

No input schema was published for this tool.

read_multinoteRead the full content of multiple notes at once

Read the full content of multiple notes at once

No input schema was published for this tool.

create_noteCreate a new note in Joplin

Create a new note in Joplin

No input schema was published for this tool.

create_folderCreate a new folder/notebook in Joplin

Create a new folder/notebook in Joplin

No input schema was published for this tool.

edit_noteprivilegedEdit/update an existing note in Joplin

Edit/update an existing note in Joplin

No input schema was published for this tool.

edit_folderprivilegedEdit/update an existing folder/notebook in Joplin

Edit/update an existing folder/notebook in Joplin

No input schema was published for this tool.

delete_noteprivilegedDelete a note from Joplin (requires confirmation)

Delete a note from Joplin (requires confirmation)

No input schema was published for this tool.

delete_folderprivilegedDelete a folder/notebook from Joplin (requires confirmation)

Delete a folder/notebook from Joplin (requires confirmation)

No input schema was published for this tool.

syncTrigger a Joplin sync to push/pull changes with the configured sync target

Trigger a Joplin sync to push/pull changes with the configured sync target

No input schema was published for this tool.

12 of 12 tools published a description.

Tool names and descriptions are written by the publisher and shown verbatim as inert text. They are the strings an MCP client passes to a model, so Forge scans them for prompt-injection patterns — any finding appears with the security scan above. “Privileged” is a keyword match on the tool name, not an audit of what the tool does: a benign-sounding name can still do anything.

About

Search, read, create, edit and sync Joplin notes and notebooks via a headless Joplin sidecar.

Keywords
mcp
Alternatives
Comparing tool surfaces…

Dependency tree

What one Forge scan resolved from npm metadata on 2026-09-30 — observed resolution, not a publisher declaration.

60 packages resolved · 8 direct · 3 carrying advisories Resolution stops at depth 4 and 60 packages.

The crawl stopped at the 60-package limit. The rest of the tree was never resolved.

36 more resolved packages are not drawn here (display cap: 24). Every dependency carrying an advisory is drawn regardless of the cap. Full inventory (CycloneDX SBOM)

Declared but not resolved

248 declared dependencies never landed in the tree. They are missing from Forge's resolution, not from the package.

+236 more not listed. The counts by reason above cover all of them.

Not followed: peerDependencies, optionalDependencies. This tree covers runtime dependencies only, so anything those pull in was never resolved.