* feat(plugins): add public Track and Artist DTOs for host services * feat(plugins): add Matcher host-service interface and MatchSong DTO * feat(plugins): generate Matcher host wrappers, PDK clients, and matcher permission * feat(plugins): implement Matcher host service and MediaFile-to-Track converter Also fixes an ndpgen bug where ParseDirectory parsed each host-service file in isolation, so a service method referencing a struct defined in another file of the same package (host.Track in track.go) could not be resolved. ParseDirectory now collects package-wide structs in a first pass, mirroring ParseCapabilities; PDK clients regenerated cleanly via make gen. * feat(plugins): register Matcher host service in the manager * test(plugins): add Matcher host service integration test plugin * refactor(plugins): simplify matcher converter and parser file collection - toTrack: use gg.V for nil-able field derefs and slice.Map for genres/ participants, removing the repeated nil-guard blocks and inner loop - manager_loader: drop the redundant ds==nil guard (loadEnabledPlugins already gates a nil DataStore), matching the other service entries - ndpgen parser: extract collectGoFiles, shared by ParseDirectory and ParseCapabilities instead of duplicating the file-filter loop * fix(plugins): keep nullable Track numerics as pointers ReplayGain values, BitDepth, and BPM are nullable in model.MediaFile, and 0 is a valid measured ReplayGain value. Flattening them to value types with omitempty made a real 0 indistinguishable from absent. Model them as *float64 /*int32 so plugins can tell 'no data' from a measured 0. Regenerated PDK clients; converter passes the model pointers through (RG) or maps *int->*int32 (BitDepth/BPM). * refactor(plugins): trim redundant pass labels in ndpgen ParseDirectory The function doc already explains the two-pass approach; the inline labels restated it. Reduce to bare waypoints. * fix(plugins): gate Track.Path on library filesystem permission MatchSongs copied mf.Path into every result unconditionally, letting a plugin with only the matcher permission enumerate on-disk file paths by matching known songs. Gate Path behind library.filesystem, matching the Library host service. toTrack is now a method carrying the permission flag. * refactor(plugins): align MatchSong JSON casing and parse Go files once - MatchSong: artistMBID/albumMBID JSON tags -> artistMbid/albumMbid so the Go wire format matches the Rust SDK's camelCase serialization (cross-SDK fix) - MatchSongs doc reworded to language-neutral 'empty (absent)' so generated Rust/Python client docs no longer say Go-specific 'nil' - ndpgen: parse each package file once (parseGoFiles) and reuse the ASTs across both passes in ParseDirectory and ParseCapabilities, instead of re-parsing * refactor(plugins): use shared types for Matcher host service Move the Matcher host service onto the shared plugins/types package instead of the host-local MatchSong and Track structs. MatchSongs now takes []types.SongRef and returns []*types.Track, dropping host.MatchSong and moving host.Track (with its host.Artist dependency collapsed onto types.ArtistRef) into plugins/types. ArtistRef gains SortName and SubRole so it can back a track's Participants. SongRef gains a millisecond-precision DurationMs field that supersedes the now deprecated seconds-based Duration, with DurationInMs() resolving the effective value and SetDurationMs() keeping both fields in sync when populating a SongRef to send to a plugin. The ndpgen host-wrapper template only ever imported context, json and extism, so a host service referencing the shared types package produced uncompilable code. Emit the plugins/types import when the service references shared types directly (gated on the existing Service.ImportsSharedTypes), matching the client template, and cover it with GenerateHost tests. This removes the need for host-local re-export aliases. Regenerated the Go/Rust/Python PDK and capability schemas accordingly. * test(plugins): cover SongRef duration and artist conversion Add unit coverage for the new SongRef behavior: SetDurationMs populating both DurationMs and the deprecated seconds field, and the SongRef-to-agents.Song conversion preferring DurationMs over Duration and the Artists list over the scalar Artist/ArtistMBID. Extract the inline SongRef-to-agents.Song closure in MatchSongs into a named toAgentSong function so the conversion can be asserted directly rather than only through the opaque matcher. The end-to-end wire shape of the moved types is already validated by the existing MatcherService integration test, so no new WASM-boundary test is needed. * fix(plugins): harden and unify SongRef-to-agents.Song duration conversion Address findings from a code review of the matcher host service: - DurationInMs now clamps a negative deprecated-seconds value to 0 instead of converting it through uint32, which previously wrapped a value like -1s into a ~49-day duration that corrupted the matcher's duration-proximity tiebreaker. - Replace the unused SetDurationMs(uint32) with SetDuration(seconds float32), which takes the unit callers actually hold (model.MediaFile.Duration is float32 seconds) and centralizes the seconds-to-ms conversion. Wire it into mediaFileToSongRef so outbound SongRefs carry both duration fields in sync. - Make the metadata-agent path use DurationInMs() so every consumer of the shared SongRef honors the DurationMs-over-Duration precedence contract; a plugin sending only DurationMs no longer loses its duration on that path. - Collapse the matcher's duplicate toAgentSong/agentArtists helpers into the existing songRefToAgentSong converter, so there is a single SongRef-to-Song mapping. Tests narrowed to the duration cases, with artist precedence still covered in metadata_agent_test.go. * feat(plugins): allow Matcher host service to scope a match to a user Add an options struct to the Matcher host service so a plugin can run a match as a specific user. When MatchOptions.Username is set, the match is run in that user's context: their favourites and ratings inform the matcher's tiebreaker, and the returned tracks carry that user's per-user annotations (Starred, StarredAt, Rating, PlayCount, PlayDate, added to types.Track). An empty username preserves the previous unscoped behaviour. Cross-user access is gated by the same allowedUsers/allUsers permission the Users and SubsonicAPI host services use: an unknown username, or one the plugin is not permitted to act as, returns an error. User-library access applies automatically once the user is in context (applyLibraryFilter). Independently, results are now restricted to the libraries the plugin itself may access via the precomputed libraryAccess set, dropping any matched track outside that set (the input index stays unmatched) — this applies even without a username and even for an admin-scoped user. core/matcher is unchanged: it already loads and uses annotations and applies user-library filtering from context, so the feature works by deriving the request context and post-filtering by plugin library access in the host adapter. The new opts parameter and the Track annotation fields are propagated to all PDK clients (Go/Rust/Python) by make gen. * fix(plugins): correct Matcher library scope and unify user-access checks Address findings from a code review of the user-scoped Matcher host service: - The plugin-library post-filter previously dropped every match for a plugin that holds only the matcher permission, because library config is tied to the Library permission and a matcher-only plugin has none (empty allowedLibraries, AllLibraries=false). Gate the filter on whether the plugin actually declared the Library permission: matcher-only plugins are no longer library-restricted, while plugins that opt into a library scope are enforced as before. The per-user library filter (applyLibraryFilter) still applies whenever a non-admin user is scoped. - resolveUser collapsed every FindByUsername error (including transient DB failures) into a misleading "not found". Extract a shared userAccess type (alongside libraryAccess) whose resolve() distinguishes model.ErrNotFound from a real backend error and authorizes the user against the allowed set. The Matcher service now uses it, and host_subsonicapi shares the same userAccess type for its permission check (preserving its existing error messages), removing a third divergent copy of the resolve-and-authorize logic. - Document in the matcher tests that the mock MediaFileRepo returns annotations unconditionally, so the unit tests cover the adapter's scoped-flag gating and access checks but not the SQL per-user join. Add tests for the library-permission gating and for surfacing a backend error instead of masking it as not-found. * fix(plugins): require a library scope for Matcher, fail closed Reverse the permissive default introduced when fixing the library post-filter: a Matcher plugin now must be granted a library scope (all libraries, or at least one specific library) and MatchSongs rejects the request with "no libraries configured" when it has none, instead of either silently matching nothing or defaulting to every library. This mirrors how the SubsonicAPI host service requires a user scope (checkPermissions errors with "no users configured" when none is set): the check is a runtime guard via libraryAccess.configured(), needs no manifest changes, and keeps the failure loud rather than silent. The per-match library post-filter then always applies, and the restrictLibraries flag added in the previous commit is removed. * fix(plugins): require library permission for matcher; guard nil user Close the gap where a plugin declaring only the matcher permission loaded successfully but failed every MatchSongs call with "no libraries configured", with no way for an admin to grant a library scope (the library-config UI is gated on the library permission). Add a cross-field manifest rule, mirroring the existing "subsonicapi requires users" rule, so the matcher permission requires the library permission to be declared. A matcher plugin therefore also surfaces the library-config panel and is subject to the existing load/enable-time library configuration gate, making the fail-closed library check reachable and fixable rather than a silent dead end. The test plugin manifest now declares the library permission accordingly. Also restore a defensive nil-user guard in userAccess.resolve: if a DataStore's FindByUsername ever returns (nil, nil) instead of model.ErrNotFound, return a clean "not found" error rather than dereferencing a nil *model.User. * feat(plugins): expose track AverageRating in Matcher results Add AverageRating to the Matcher's Track DTO. Unlike the per-user annotations (Starred, Rating, PlayCount, ...), AverageRating is an aggregate stored on the track itself and is loaded regardless of the request user, so it is populated unconditionally rather than gated on a scoped username. Propagated to the PDK types by make gen. Signed-off-by: Deluan <deluan@navidrome.org> * style(plugins): trim verbose comments in matcher host service Condense the over-long explanatory comments added across the matcher host service to one-liners that state the why, and simplify the ptrInt32/unixPtr helpers to Go 1.26's new(value). No behavior change. * refactor(plugins): pass userAccess into newSubsonicAPIService Move newUserAccess construction to the loader call site so the SubsonicAPI service constructor takes a userAccess value directly, matching newMatcherService. Pure refactor: the service already stored a userAccess internally, so behavior and error messages are unchanged. * fix(plugins): regenerate PDK and drop omitempty from AverageRating Re-run make gen so the generated PDK doc comments match the source comment trimmed in an earlier commit (the source was simplified but the PDK was not regenerated, leaving the committed files stale — a 'generated files up to date' hazard). Also drop omitempty from Track.AverageRating: it is always set (0 when unrated), so it should be present in the payload like the other always-set fields (BirthTime/CreatedAt/UpdatedAt), not dropped at zero. Tag change propagated to the PDK by the same regeneration. * fix(plugins): reject user-scoped match before lookup when plugin has no user scope A matcher plugin requires the library permission but not the users permission, so a matcher-only plugin always has an empty user scope (allUsers=false, no allowed users). MatchSongs still ran FindByUsername for any opts.Username before checking authorization and returned distinguishable errors ('user X not found' vs 'not allowed to act as user X'), letting such a plugin enumerate account names from the error text. Guard userAccess.resolve to reject with a single fixed error before the lookup when the plugin has no user scope, mirroring how the SubsonicAPI service short-circuits with 'no users configured'. The unscoped match path (no username) is unaffected, so matcher-only plugins still match normally. * fix(plugins): run unscoped matcher as admin, not the inherited request user A matcher host call can arrive on a context that already carries a request user (e.g. a plugin capability invoked while serving that user's request — extism propagates the call context into host functions). With no opts.Username, MatchSongs passed that context straight through, so the media-file repository applied the caller's library filter and per-user annotation ranking to an explicitly unscoped match. Set the user context explicitly: a username scopes to that user (overriding any inherited one), and an unscoped match runs under adminContext so only the plugin's own library scope constrains results. Adds tests using a context-capturing DataStore to assert the user the matcher resolves in both cases. * chore(plugins): drop the generated Python matcher PDK The Python plugin PDK is no longer supported (ndpgen generates only Go and Rust clients), so remove the stale generated nd_host_matcher.py rather than leave a client that drifts from the host interface. * docs(plugins): deprecate SongRef.Artist/ArtistMBID in favor of Artists Mark the scalar single-artist fields deprecated; Artists (the ArtistRef list) is the preferred way to supply artist data and already takes precedence for matching. Propagated to the PDK and capability schemas by make gen. * refactor(plugins): flatten Track.Participants and add Role to ArtistRef Change Track.Participants from map[role][]ArtistRef to a flat []ArtistRef, and give ArtistRef a Role field (the participation category: artist/composer/performer/...) alongside SubRole (a specialization within a role, e.g. the instrument for a performer). In the flat list each entry now self-describes its role rather than relying on a map key, matching how SongRef.Artists is already a flat list; the converter tags each entry with its role and emits them in a stable role order. Propagated to the PDK and capability schemas by make gen. --------- Signed-off-by: Deluan <deluan@navidrome.org>
Navidrome Plugin System
Navidrome supports WebAssembly (Wasm) plugins for extending functionality. Plugins run in a secure sandbox and can provide metadata agents, scrobblers, lyrics providers, audio similarity, and other integrations through host services like scheduling, caching, task queues, WebSockets, and Subsonic API access.
The plugin system is built on Extism, a cross-language framework for building WebAssembly plugins. You can write plugins in any language that Extism supports (Go, Rust, Python, TypeScript, and more) using their Plugin Development Kits (PDKs).
Essential Extism Resources:
- Extism Documentation – Core concepts and architecture
- Plugin Development Kits (PDKs) – Language-specific libraries for writing plugins
- Go PDK – Recommended for Go plugins with TinyGo
- Rust PDK – For Rust plugins
- Python PDK – Experimental Python support
- JavaScript PDK – For TypeScript/JavaScript plugins
Table of Contents
- Quick Start
- Plugin Basics
- Capabilities
- Host Services
- Configuration
- Building Plugins
- Examples
- Security
Quick Start
1. Create a minimal plugin
Create main.go:
package main
import "github.com/extism/go-pdk"
func main() {}
// Implement your capability functions here
Create manifest.json:
{
"name": "My Plugin",
"author": "Your Name",
"version": "1.0.0"
}
2. Build with TinyGo and package as .ndp
# Compile to WebAssembly
tinygo build -o plugin.wasm -target wasip1 -buildmode=c-shared .
# Package as .ndp (zip archive)
zip -j my-plugin.ndp manifest.json plugin.wasm
3. Install
Copy my-plugin.ndp to your Navidrome plugins folder and enable plugins in your config:
[Plugins]
Enabled = true
Folder = "/path/to/plugins"
Plugin Basics
What is a Plugin?
A Navidrome plugin is an .ndp package file (zip archive) containing:
manifest.json– Plugin metadata (name, author, version, permissions)plugin.wasm– Compiled WebAssembly module with capability functions
Plugin Naming
Plugins are identified by their filename (without .ndp extension), not the manifest name field:
my-plugin.ndp→ plugin ID ismy-plugin- The manifest
nameis the display name shown in the UI
This allows users to have multiple instances of the same plugin with different configs by renaming the files.
The Manifest
Every plugin must include a manifest.json file. Example:
{
"name": "My Plugin",
"author": "Author Name",
"version": "1.0.0",
"description": "What this plugin does",
"website": "https://example.com",
"config": {
"schema": { ... },
"uiSchema": { ... }
},
"permissions": {
"http": {
"reason": "Fetch metadata from external API",
"requiredHosts": ["api.example.com", "*.musicbrainz.org"]
}
}
}
Required fields: name, author, version
Optional fields: description, website, config, permissions, experimental
Config Definition
The config field defines the plugin's configuration schema using JSON Schema (draft-07) and an optional JSONForms UI schema for rendering in the Navidrome web UI:
{
"config": {
"schema": {
"type": "object",
"properties": {
"api_key": { "type": "string", "title": "API Key" },
"max_retries": { "type": "integer", "default": 3 }
},
"required": ["api_key"]
},
"uiSchema": {
"api_key": { "ui:widget": "password" }
}
}
}
Experimental Features
Plugins can opt-in to experimental WebAssembly features that may change or be removed in future versions. Currently supported:
threads– Enables WebAssembly threads support (for plugins compiled with multi-threading)
{
"experimental": {
"threads": {
"reason": "Required for concurrent audio processing"
}
}
}
Note: Experimental features may have compatibility or performance implications. Use only when necessary.
Capabilities
Capabilities define what your plugin can do. They're automatically detected based on which functions you export. A plugin can implement multiple capabilities.
MetadataAgent
Provides artist and album metadata. All methods are optional — implement only the ones your data source supports.
| Function | Input | Output | Description |
|---|---|---|---|
nd_get_artist_mbid |
{id, name} |
{mbid} |
Get MusicBrainz ID |
nd_get_artist_url |
{id, name, mbid?} |
{url} |
Get artist URL |
nd_get_artist_biography |
{id, name, mbid?} |
{biography} |
Get artist biography |
nd_get_similar_artists |
{id, name, mbid?, limit} |
{artists: [{name, mbid?}]} |
Get similar artists |
nd_get_artist_images |
{id, name, mbid?} |
{images: [{url, size}]} |
Get artist images |
nd_get_artist_top_songs |
{id, name, mbid?, count} |
{songs: [{name, mbid?}]} |
Get top songs |
nd_get_album_info |
{name, artist, mbid?} |
{name, mbid, description, url} |
Get album info |
nd_get_album_images |
{name, artist, mbid?} |
{images: [{url, size}]} |
Get album images |
nd_get_similar_songs_by_track |
{id, name, artist, ...} |
{songs: [{name, artist}]} |
Similar songs by track |
nd_get_similar_songs_by_album |
{id, name, artist, ...} |
{songs: [{name, artist}]} |
Similar songs by album |
nd_get_similar_songs_by_artist |
{id, name, mbid?, count} |
{songs: [{name, artist}]} |
Similar songs by artist |
To use the plugin as a metadata agent, add it to your config:
Agents = "lastfm,spotify,my-plugin"
Example (using Go PDK package):
package main
import "github.com/navidrome/navidrome/plugins/pdk/go/metadata"
type myPlugin struct{}
func (p *myPlugin) GetArtistBiography(input metadata.ArtistRequest) (*metadata.ArtistBiographyResponse, error) {
return &metadata.ArtistBiographyResponse{Biography: "Biography text..."}, nil
}
func init() { metadata.Register(&myPlugin{}) }
func main() {}
Example (raw wasmexport):
//go:wasmexport nd_get_artist_biography
func ndGetArtistBiography() int32 {
var input ArtistInput
if err := pdk.InputJSON(&input); err != nil {
pdk.SetError(err)
return 1
}
pdk.OutputJSON(BiographyOutput{Biography: "Artist biography..."})
return 0
}
Scrobbler
Integrates with external scrobbling services. All three methods are required.
| Function | Input | Output | Description |
|---|---|---|---|
nd_scrobbler_is_authorized |
{username} |
bool |
Check if user is authorized |
nd_scrobbler_now_playing |
See below | (none) | Send now playing |
nd_scrobbler_scrobble |
See below | (none) | Submit a scrobble |
Important: Scrobbler plugins require the
userspermission in their manifest. Scrobble events are only sent for users assigned to the plugin through Navidrome's configuration.
Manifest permission:
{
"permissions": {
"users": {
"reason": "Receive scrobble events for users assigned to this plugin"
}
}
}
NowPlaying/Scrobble Input:
{
"username": "john",
"track": {
"id": "track-id",
"title": "Song Title",
"album": "Album Name",
"artist": "Artist Name",
"albumArtist": "Album Artist",
"duration": 180.5,
"trackNumber": 1,
"discNumber": 1,
"mbzRecordingId": "...",
"mbzAlbumId": "...",
"mbzArtistId": "..."
},
"timestamp": 1703270400
}
Error Handling:
On success, return 0. On failure, use pdk.SetError() with one of these error types:
scrobbler(not_authorized)– User needs to re-authorizescrobbler(retry_later)– Temporary failure, Navidrome will retryscrobbler(unrecoverable)– Permanent failure, scrobble discarded
import "github.com/navidrome/navidrome/plugins/pdk/go/scrobbler"
return scrobbler.ScrobblerErrorNotAuthorized
return scrobbler.ScrobblerErrorRetryLater
return scrobbler.ScrobblerErrorUnrecoverable
Lyrics
Provides lyrics for tracks. The single method is required.
| Function | Input | Output | Description |
|---|---|---|---|
nd_lyrics_get_lyrics |
{artistName, title, ...} |
{lyrics: [{lang, text}]} |
Get lyrics |
Each returned lyric entry has a lang (language code) and text field. Multiple entries can be returned for different languages.
SonicSimilarity
Audio-similarity discovery based on acoustic features (e.g., embeddings). Both methods are required.
| Function | Input | Output | Description |
|---|---|---|---|
nd_get_sonic_similar_tracks |
{song, count} |
{matches: [{song, similarity}]} |
Find acoustically similar tracks |
nd_find_sonic_path |
{startSong, endSong, count} |
{matches: [{song, similarity}]} |
Find a path between two songs |
Each match contains a song reference and a similarity score (float64, 0.0–1.0).
TaskWorker
Processes tasks from a queue. The method is optional — export it if your plugin uses the Task host service for background work.
| Function | Input | Output | Description |
|---|---|---|---|
nd_task_execute |
{queueName, taskID, payload, attempt} |
string |
Execute a queued task |
The payload is raw bytes (the same bytes passed to TaskEnqueue). The attempt counter starts at 1 and increments on retries. Return a string result on success.
Lifecycle
Optional initialization callback. Called once after the plugin fully loads.
| Function | Input | Output | Description |
|---|---|---|---|
nd_on_init |
{} |
{error?} |
Called once after plugin loads |
Useful for initializing connections, scheduling recurring tasks, etc. Errors are logged but don't prevent the plugin from loading.
SchedulerCallback
Receives scheduled task events. Required if your plugin uses the Scheduler host service.
| Function | Input | Output | Description |
|---|---|---|---|
nd_scheduler_callback |
{scheduleId, payload, isRecurring} |
(none) | Handle scheduled task event |
WebSocketCallback
Receives WebSocket events. Export any subset of these to handle events from the WebSocket host service.
| Function | Input | Description |
|---|---|---|
nd_websocket_on_text_message |
{connectionId, message} |
Text message received |
nd_websocket_on_binary_message |
{connectionId, data} |
Binary message received (base64) |
nd_websocket_on_error |
{connectionId, error} |
Connection error |
nd_websocket_on_close |
{connectionId, code, reason} |
Connection closed |
Host Services
Host services let your plugin call back into Navidrome for advanced functionality. Each service (except Config) requires declaring the corresponding permission in your manifest.
Go PDK Setup
All host service examples below use the generated Go SDK. Add this to your go.mod:
require github.com/navidrome/navidrome/plugins/pdk/go v0.0.0
replace github.com/navidrome/navidrome/plugins/pdk/go => ../../pdk/go
Then import:
import "github.com/navidrome/navidrome/plugins/pdk/go/host"
HTTP
Make HTTP requests to external services. This is a dedicated host service (separate from Extism's built-in HTTP support) with additional features like timeouts and redirect control.
Manifest permission:
{
"permissions": {
"http": {
"reason": "Fetch metadata from external API",
"requiredHosts": ["api.example.com", "*.musicbrainz.org"]
}
}
}
Host functions:
| Function | Parameters | Returns |
|---|---|---|
http_send |
method, url, headers, body, timeoutMs, noFollowRedirects |
statusCode, headers, body |
Usage:
resp, err := host.HTTPSend(host.HTTPRequest{
Method: "GET",
URL: "https://api.example.com/data",
Headers: map[string]string{"Authorization": "Bearer " + apiKey},
})
if resp.StatusCode == 200 {
// Process resp.Body
}
Scheduler
Schedule one-time or recurring tasks. Your plugin must export the nd_scheduler_callback function to receive events.
Manifest permission:
{
"permissions": {
"scheduler": {
"reason": "Schedule periodic metadata refresh"
}
}
}
Host functions:
| Function | Parameters | Description |
|---|---|---|
scheduler_scheduleonetime |
delaySeconds, payload, scheduleId? |
Schedule one-time callback |
scheduler_schedulerecurring |
cronExpression, payload, scheduleId? |
Schedule recurring callback |
scheduler_cancelschedule |
scheduleId |
Cancel a scheduled task |
Usage:
// Schedule one-time task in 60 seconds
scheduleID, err := host.SchedulerScheduleOneTime(60, "my-payload", "")
// Schedule recurring task with cron expression (every hour)
scheduleID, err := host.SchedulerScheduleRecurring("0 * * * *", "hourly-task", "")
// Cancel a task
err := host.SchedulerCancelSchedule(scheduleID)
Cache
In-memory TTL-based cache. Each plugin has its own isolated namespace. Cleared on server restart.
Manifest permission:
{
"permissions": {
"cache": {
"reason": "Cache API responses to reduce external requests"
}
}
}
Host functions:
| Function | Parameters | Description |
|---|---|---|
cache_setstring |
key, value, ttl_seconds |
Store a string |
cache_getstring |
key |
Get a string |
cache_setint |
key, value, ttl_seconds |
Store an integer |
cache_getint |
key |
Get an integer |
cache_setfloat |
key, value, ttl_seconds |
Store a float |
cache_getfloat |
key |
Get a float |
cache_setbytes |
key, value, ttl_seconds |
Store bytes |
cache_getbytes |
key |
Get bytes |
cache_has |
key |
Check if key exists |
cache_remove |
key |
Delete a cached value |
TTL: Pass 0 for the default (24 hours), or specify seconds.
Usage:
// Cache a value for 1 hour
host.CacheSetString("api-response", responseData, 3600)
// Retrieve (returns value, exists, error)
value, exists, err := host.CacheGetString("api-response")
if exists {
// Use value
}
KVStore
Persistent key-value storage backed by SQLite. Survives server restarts. Each plugin has its own isolated database at ${DataFolder}/plugins/${pluginID}/kvstore.db.
Manifest permission:
{
"permissions": {
"kvstore": {
"reason": "Store OAuth tokens and plugin state",
"maxSize": "1MB"
}
}
}
maxSize: Maximum storage size (e.g.,"1MB","500KB"). Default: 1MB
Key constraints: Maximum 256 bytes, must be valid UTF-8.
Host functions:
| Function | Parameters | Description |
|---|---|---|
kvstore_set |
key, value |
Store a byte value |
kvstore_setwithttl |
key, value, ttlSeconds |
Store with auto-expiration |
kvstore_get |
key |
Retrieve a byte value |
kvstore_getmany |
keys |
Retrieve multiple values at once |
kvstore_has |
key |
Check if key exists |
kvstore_list |
prefix |
List keys matching prefix |
kvstore_delete |
key |
Delete a value |
kvstore_deletebyprefix |
prefix |
Delete all keys matching prefix |
kvstore_getstorageused |
– | Get current storage usage (bytes) |
Usage:
// Store a value (as raw bytes)
token := []byte(`{"access_token": "xyz", "refresh_token": "abc"}`)
host.KVStoreSet("oauth:spotify", token)
// Store with TTL (auto-expires after 1 hour)
host.KVStoreSetWithTTL("session:abc", sessionData, 3600)
// Retrieve a value
value, exists, err := host.KVStoreGet("oauth:spotify")
if exists {
var tokenData map[string]string
json.Unmarshal(value, &tokenData)
}
// Batch retrieve
results, err := host.KVStoreGetMany([]string{"key1", "key2", "key3"})
// List and delete by prefix
keys, err := host.KVStoreList("user:")
host.KVStoreDeleteByPrefix("user:")
// Check storage usage
usage, err := host.KVStoreGetStorageUsed()
fmt.Printf("Using %d bytes\n", usage)
Task
Background task queue with retry support. Plugins enqueue tasks and process them by exporting the nd_task_execute capability function.
Manifest permission:
{
"permissions": {
"taskqueue": {
"reason": "Process audio analysis in the background",
"maxConcurrency": 2
}
}
}
Host functions:
| Function | Parameters | Description |
|---|---|---|
task_createqueue |
name, concurrency, maxRetries, backoffMs, ... |
Create a named task queue |
task_enqueue |
queueName, payload |
Add a task to the queue |
task_get |
taskID |
Get task status and result |
task_cancel |
taskID |
Cancel a pending task |
task_clearqueue |
queueName |
Remove all tasks from queue |
Usage:
// Create a queue with retry configuration
host.TaskCreateQueue("analysis", host.QueueConfig{
Concurrency: 2,
MaxRetries: 3,
BackoffMs: 1000,
})
// Enqueue a task
taskID, err := host.TaskEnqueue("analysis", []byte(`{"trackId": "abc"}`))
// Check task status
info, err := host.TaskGet(taskID)
fmt.Printf("Status: %s, Attempt: %d\n", info.Status, info.Attempt)
WebSocket
Establish persistent WebSocket connections to external services. Your plugin must export WebSocketCallback functions to receive events.
Manifest permission:
{
"permissions": {
"websocket": {
"reason": "Real-time connection to service",
"requiredHosts": ["gateway.example.com", "*.discord.gg"]
}
}
}
Host functions:
| Function | Parameters | Description |
|---|---|---|
websocket_connect |
url, headers?, connectionId? |
Open a connection |
websocket_sendtext |
connectionId, message |
Send text message |
websocket_sendbinary |
connectionId, data |
Send binary data |
websocket_closeconnection |
connectionId, code?, reason? |
Close connection |
Usage:
connID, err := host.WebSocketConnect("wss://gateway.example.com", nil, "")
host.WebSocketSendText(connID, `{"op": 1, "d": null}`)
host.WebSocketCloseConnection(connID, 1000, "done")
Library
Access music library metadata and optionally read files from library directories.
Manifest permission:
{
"permissions": {
"library": {
"reason": "Access library metadata for analysis",
"filesystem": false
}
}
}
filesystem– Set totrueto enable read-only access to library directories (default:false)
Host functions:
| Function | Parameters | Returns |
|---|---|---|
library_getlibrary |
id |
Library metadata |
library_getalllibraries |
(none) | Array of library metadata |
Library metadata:
{
"id": 1,
"name": "My Music",
"path": "/music/collection",
"mountPoint": "/libraries/1",
"lastScanAt": 1703270400,
"totalSongs": 5000,
"totalAlbums": 500,
"totalArtists": 200,
"totalSize": 50000000000,
"totalDuration": 1500000.5
}
Note: The
pathandmountPointfields are only included whenfilesystem: trueis set in the permission.
Filesystem access:
When filesystem: true, your plugin can read files from library directories via WASI filesystem APIs. Each library is mounted at /libraries/<id>:
import "os"
content, err := os.ReadFile("/libraries/1/Artist/Album/track.mp3")
entries, err := os.ReadDir("/libraries/1/Artist")
Security: Filesystem access is read-only and restricted to configured library paths only.
Usage:
// Get a specific library
library, err := host.LibraryGetLibrary(1)
fmt.Printf("Library: %s (%d songs)\n", library.Name, library.TotalSongs)
// Get all libraries
libraries, err := host.LibraryGetAllLibraries()
for _, lib := range libraries {
fmt.Printf("Library: %s (%d songs)\n", lib.Name, lib.TotalSongs)
}
Artwork
Generate public URLs for Navidrome artwork (albums, artists, tracks, playlists).
Manifest permission:
{
"permissions": {
"artwork": {
"reason": "Get artwork URLs for display"
}
}
}
Host functions:
| Function | Parameters | Returns |
|---|---|---|
artwork_getartisturl |
id, size |
Artwork URL |
artwork_getalbumurl |
id, size |
Artwork URL |
artwork_gettrackurl |
id, size |
Artwork URL |
artwork_getplaylisturl |
id, size |
Artwork URL |
Usage:
url, err := host.ArtworkGetAlbumUrl("album-id", 300)
SubsonicAPI
Call Navidrome's Subsonic API internally (no network round-trip).
Manifest permission:
{
"permissions": {
"subsonicapi": {
"reason": "Access library data"
},
"users": {
"reason": "Access user information for SubsonicAPI authorization"
}
}
}
Important: The
subsonicapipermission requires theuserspermission. Which users the plugin can act as is controlled through the Navidrome UI.
Host functions:
| Function | Parameters | Returns |
|---|---|---|
subsonicapi_call |
uri |
JSON response string |
subsonicapi_callraw |
uri |
Content type + binary response |
Usage:
// JSON response
response, err := host.SubsonicAPICall("getAlbumList2?type=random&size=10&u=username")
// Binary response (e.g., cover art, streams)
contentType, data, err := host.SubsonicAPICallRaw("getCoverArt?id=al-123&u=username")
Config
Access plugin configuration values. Unlike pdk.GetConfig() which only retrieves individual values, this service can list all available configuration keys — useful for discovering dynamic configuration.
Note: This service is always available and does not require a manifest permission.
Host functions:
| Function | Parameters | Returns |
|---|---|---|
config_get |
key |
value, exists |
config_getint |
key |
value, exists |
config_keys |
prefix |
Array of matching key names |
Usage:
// Get a configuration value
value, exists := host.ConfigGet("api_key")
// Get an integer configuration value
count, exists := host.ConfigGetInt("max_retries")
// List all keys with a prefix (useful for user-specific config)
keys := host.ConfigKeys("user:")
// List all configuration keys
allKeys := host.ConfigKeys("")
Users
Access user information for the users that the plugin has been granted access to.
Manifest permission:
{
"permissions": {
"users": {
"reason": "Display user information in status updates"
}
}
}
Important: Before enabling a plugin that requires the users permission, an administrator must configure which users the plugin can access:
- Allow all users – Enable the "Allow all users" toggle in the plugin settings
- Select specific users – Choose individual users from the user list
If neither option is configured, the plugin cannot be enabled.
Host functions:
| Function | Parameters | Returns |
|---|---|---|
users_getusers |
– | Array of User objects |
users_getadmins |
– | Array of admin Users |
User object fields:
| Field | Type | Description |
|---|---|---|
userName |
string | The user's unique username |
name |
string | The user's display name |
isAdmin |
boolean | Whether the user is an admin |
Security: Sensitive fields like passwords, email addresses, and internal IDs are never exposed to plugins.
Usage:
users, err := host.UsersGetUsers()
for _, user := range users {
pdk.Log(pdk.LogInfo, "User: " + user.UserName + " (" + user.Name + ")")
}
admins, err := host.UsersGetAdmins()
Configuration
Server Configuration
Enable plugins in navidrome.toml:
[Plugins]
Enabled = true
Folder = "/path/to/plugins" # Default: DataFolder/plugins
AutoReload = true # Auto-reload on file changes (dev mode)
LogLevel = "debug" # Plugin-specific log level
CacheSize = "200MB" # Compilation cache size limit
Plugin Configuration
Plugin configuration is managed through the Navidrome web UI. Navigate to the Plugins page, select a plugin, and edit its configuration as key-value pairs.
Access configuration values in your plugin:
apiKey, ok := pdk.GetConfig("api_key")
if !ok {
pdk.SetErrorString("api_key configuration is required")
return 1
}
For more advanced access (listing keys, integer values), use the Config host service.
Building Plugins
Supported Languages
Plugins can be written in any language that Extism supports. We recommend:
- Go – Best overall experience with TinyGo and the Go PDK. Familiar syntax, excellent stdlib support.
- Rust – Best for performance-critical plugins. Smallest binaries, excellent type safety. Uses the Rust PDK.
- Python – Best for rapid prototyping. Experimental support via extism-py. Note some limitations compared to compiled languages.
- TypeScript – Experimental support via extism-js.
Go with TinyGo (Recommended)
# Install TinyGo: https://tinygo.org/getting-started/install/
# Build WebAssembly module
tinygo build -o plugin.wasm -target wasip1 -buildmode=c-shared .
# Package as .ndp
zip -j my-plugin.ndp manifest.json plugin.wasm
Using Go PDK Packages
Navidrome provides type-safe Go packages for each capability and host service in plugins/pdk/go/. Instead of manually exporting functions with //go:wasmexport, use the Register() pattern:
package main
import "github.com/navidrome/navidrome/plugins/pdk/go/metadata"
type myPlugin struct{}
func (p *myPlugin) GetArtistBiography(input metadata.ArtistRequest) (*metadata.ArtistBiographyResponse, error) {
return &metadata.ArtistBiographyResponse{Biography: "Biography text..."}, nil
}
func init() { metadata.Register(&myPlugin{}) }
func main() {}
Add to your go.mod:
require github.com/navidrome/navidrome v0.0.0
replace github.com/navidrome/navidrome => ../../..
Available capability packages:
| Package | Import Path | Description |
|---|---|---|
metadata |
plugins/pdk/go/metadata |
Artist/album metadata providers |
scrobbler |
plugins/pdk/go/scrobbler |
Scrobbling services |
lyrics |
plugins/pdk/go/lyrics |
Lyrics providers |
sonicsimilarity |
plugins/pdk/go/sonicsimilarity |
Audio similarity discovery |
taskworker |
plugins/pdk/go/taskworker |
Background task processing |
lifecycle |
plugins/pdk/go/lifecycle |
Plugin initialization |
scheduler |
plugins/pdk/go/scheduler |
Scheduled task callbacks |
websocket |
plugins/pdk/go/websocket |
WebSocket event handlers |
host |
plugins/pdk/go/host |
Host service SDK (all services) |
See the example plugins in examples/ for complete usage patterns.
Rust
# Build WebAssembly module
cargo build --release --target wasm32-wasip1
# Package as .ndp
zip -j my-plugin.ndp manifest.json target/wasm32-wasip1/release/plugin.wasm
Using Rust PDK
# Cargo.toml
[dependencies]
nd-pdk = { path = "../../pdk/rust/nd-pdk" }
extism-pdk = "1.2"
serde = { version = "1.0", features = ["derive"] }
serde_json = "1.0"
Implementing capabilities with traits and macros:
use nd_pdk::scrobbler::{Scrobbler, IsAuthorizedRequest, Error};
use nd_pdk::register_scrobbler;
#[derive(Default)]
struct MyPlugin;
impl Scrobbler for MyPlugin {
fn is_authorized(&self, req: IsAuthorizedRequest) -> Result<bool, Error> {
Ok(true)
}
fn now_playing(&self, req: NowPlayingRequest) -> Result<(), Error> { Ok(()) }
fn scrobble(&self, req: ScrobbleRequest) -> Result<(), Error> { Ok(()) }
}
register_scrobbler!(MyPlugin); // Generates all WASM exports
Using host services:
use nd_pdk::host::{cache, scheduler, library};
cache::set_string("my_key", "my_value", 3600)?;
scheduler::schedule_recurring("@every 5m", "payload", "task_id")?;
let libs = library::get_all_libraries()?;
See pdk/rust/README.md for detailed documentation.
Python (with extism-py)
# Build WebAssembly module (requires extism-py installed)
extism-py plugin.wasm -o plugin.wasm *.py
# Package as .ndp
zip -j my-plugin.ndp manifest.json plugin.wasm
Using XTP CLI (Scaffolding)
Bootstrap a new plugin from a schema:
# Install XTP CLI: https://docs.xtp.dylibso.com/docs/cli
# Create a metadata agent plugin
xtp plugin init \
--schema-file plugins/capabilities/metadata_agent.yaml \
--template go \
--path ./my-agent \
--name my-agent
# Build and package
cd my-agent && xtp plugin build
zip -j my-agent.ndp manifest.json dist/plugin.wasm
See capabilities/README.md for available schemas and scaffolding examples.
Examples
See examples/ for complete working plugins:
| Plugin | Language | Capabilities | Host Services | Description |
|---|---|---|---|---|
| minimal | Go | MetadataAgent | – | Basic structure example |
| wikimedia | Go | MetadataAgent | HTTP | Wikidata/Wikipedia integration |
| coverartarchive-py | Python | MetadataAgent | HTTP | Cover Art Archive |
| coverartarchive-as | AssemblyScript | MetadataAgent | HTTP | Cover Art Archive |
| webhook-rs | Rust | Scrobbler | HTTP | HTTP webhooks |
| nowplaying-py | Python | Lifecycle | Scheduler, SubsonicAPI | Periodic now-playing logger |
| library-inspector-rs | Rust | Lifecycle | Library, Scheduler | Periodic library stats logging |
| crypto-ticker | Go | Lifecycle | WebSocket, Scheduler | Real-time crypto prices demo |
| discord-rich-presence-rs | Rust | Scrobbler | HTTP, WebSocket, Cache, Scheduler, Artwork | Discord integration |
Security
Plugins run in a secure WebAssembly sandbox provided by Extism and the Wazero runtime:
- Host Allowlisting – Only explicitly allowed hosts are accessible via HTTP/WebSocket
- Limited File System – Read-only access to library directories, only when explicitly granted the
library.filesystempermission - No Network Listeners – Plugins cannot bind ports
- Config Isolation – Plugins only receive their own config section
- Memory Limits – Controlled by the WebAssembly runtime
- User-Scoped Authorization – Plugins with
subsonicapiorscrobblercapabilities can only access/receive events for users assigned to them through Navidrome's configuration - Users Permission – Plugins requesting user access must be explicitly configured with allowed users; sensitive data (passwords, emails) is never exposed
Runtime Management
Auto-Reload
With AutoReload = true, Navidrome watches the plugins folder and automatically detects when .ndp files are added, modified, or removed. When a plugin file changes, the plugin is disabled and its metadata is re-read from the archive.
If AutoReload is disabled, Navidrome needs to be restarted to pick up plugin changes.
Enabling/Disabling Plugins
Plugins can be enabled/disabled via the Navidrome UI. The plugin state is persisted in the database.
Important Notes
- In-flight requests – When reloading, existing requests complete before the new version takes over
- Config changes – Changes to the plugin configuration in the UI are applied immediately
- Cache persistence – The in-memory cache is cleared when a plugin is unloaded