add-provider

To add a new storage provider, create a provider file, implement the required interface, register it in the appropriate factory, and update worker lists if needed. This structured approach ensures the new backend integrates correctly into the MCP core system.

Lazy-loading for Tier 3 dependencies defers loading non-critical modules until runtime, reducing initial overhead. When adding a new provider, this technique ensures required runtime registration occurs efficiently without unnecessarily impacting core startup performance.

Registering a new LLM or Speech provider requires implementing the specific provider interface, adding it to the correct factory registration, and running type checks. You must also update worker lists to incorporate the new provider into the active backend workflow.

Yes, adding a new service provider requires a YAML frontmatter containing the name and description fields in SKILL.md. This metadata documents the provider's purpose and integrates it properly into the MCP core architecture.

To verify a new backend provider implementation, run the bun run devcheck command. This validates that interface definitions, factory registrations, and worker list updates are type-safe and correctly integrated into the StorageService architecture.

Yes, this approach applies to implementing new backends for StorageService as well as new providers for LLM or Speech. It defines interfaces, file conventions, and registration steps that standardize adding any provider type to the MCP core.