knuckles-team/jellyfin-mcp/jellyfin-mcp-operations

Jellyfin Mcp Operations

Use the provider's governed MCP tools through Arbora delegation.

Workflow

1. Establish the verified GraphSession and tenant before discovery or retrieval.
2. Discover the current condensed tool surface; never assume a stale tool name or schema.
3. Prefer read-only inspection first. For changes, present impact and use the provider's

dry-run or preview mode when available.

1. Execute mutations as fenced WorkItems so retries remain idempotent and auditable.
2. Ingest source data only through the signed connector preset and ChangeEnvelope path.
3. Verify the durable result and its trace/evidence before reporting completion.

Safety contract

• Never persist credentials, endpoints, raw personal identifiers, hostnames, or local paths.
• Resolve TLS trust and verification from environment/configuration; never hardcode bypasses.
• Treat unknown ACL, tenant, schema, or tool-contract state as a hard failure.
• Require explicit approval for destructive, externally visible, or irreversible actions.
• Keep runtime traces policy-scoped and privacy-sanitized.

Specialized workflows

Read the workflow catalog only when the request needs a provider-specific procedure, parameter map, script, or reference asset.