NuGet Packages
Fig provides several NuGet packages for different integration scenarios.
Core
Fig.Client
The main client library. Add this to applications whose settings Fig should manage.
- Target framework: .NET Standard 2.0
- Documentation: Client Configuration
Fig.Client.Abstractions
Attributes and contracts so third-party libraries can declare Fig settings without taking a dependency on the full client.
- Target framework: .NET Standard 2.0
Fig.Client.Contracts
Internal contracts, including IClientSecretProvider. Most applications do not reference this directly unless they write a custom secret provider.
Fig.WebHooks.Contracts
Data contracts for webhook payloads. Use this when building a webhook integration.
Secret providers
Each provider is a separate package. See Client Secrets.
Azure Key Vault can also store setting values on the API (a different feature). See Azure Key Vault Integration.
Testing and hosting
Fig.Client.Testing
Reloadable configuration for integration tests, plus display-script testing helpers. See Integration Testing and Settings Binding Verification.
Fig.Aspire
AppHost extension methods (AddFigApi, AddFigWeb). See .NET Aspire Integration.
Not a NuGet package
Fig MCP is a standalone application / container that proxies MCP tools to the Fig API. See Fig MCP Server.
Installation examples
dotnet add package Fig.Client
dotnet add package Fig.Client.SecretProvider.Azure
dotnet add package Fig.Client.Testing