Skip to content
DiscVaultDiscVault Docs

Integrations: MCP and REST API

Goal and result

Section titled “Goal and result”

Connect an MCP client or REST consumer with a personal, user-scoped API key.

Applies to

Section titled “Applies to”

DiscVault v26 stable and beta expose MCP on the web origin or direct port 6090 and use the same API service. Never place a real key in documentation, logs, or source control.

DiscVault v26 stable

Section titled “DiscVault v26 stable”
  • DiscVault v26 stable · ghcr.io/helmerznl/discvault:latest
  • /mcp on web origin or direct port 6090 · REST API

DiscVault v26 beta

Section titled “DiscVault v26 beta”
  • DiscVault v26 beta · ghcr.io/helmerznl/discvault:beta
  • /mcp on web origin or direct port 6090 · REST API

Prerequisites

Section titled “Prerequisites”
  • personal API key
  • HTTPS DiscVault origin
  • MCP streamable HTTP client

Procedure

Section titled “Procedure”
  1. Create: personal user-scoped API key
  2. Configure: streamable-http · https://discvault.example.com/mcp
  3. Test: tool listing · owner-scoped collection
  4. Revoke: test key · remove client secret

Commands and settings

Section titled “Commands and settings”

Both channels

Section titled “Both channels”
{
  "mcpServers": {
    "discvault": {
      "transport": "streamable-http",
      "url": "https://discvault.example.com/mcp",
      "headers": { "Authorization": "******" }
    }
  }
}
Terminal window
curl --fail https://discvault.example.com/api/next/health

Expected result

Section titled “Expected result”

The client lists DiscVault tools and returns only the key owner’s collection, groups, watchlist, and history.

  • DiscVault · streamable-http · /mcp
  • provider credential stored as a secret · Authorization

Safety and rollback

Section titled “Safety and rollback”

Next step

Section titled “Next step”

Integrations: Plex and Jellyfin

Source and status

Section titled “Source and status”