F5 Distributed Cloud Terraform Provider
F5 Distributed Cloud Terraform provider docs, 270+ OpenAPI specs, and subscription info for AI.
Runs on your machine from its package; the steps are below.
What it does
- Reads
- Writes
- High impact
At most: creates or changes data: records, files, settings.
What it costs
FreeOdel charges nothing per call. The publisher may charge for its own service.
Runs locally over stdio
This server isn't hosted — your MCP client launches it from a package registry. Use one of the commands below, or drop the config into your client (e.g. Claude Desktop).
Run
npx -y @robinmordasiewicz/f5xc-terraform-mcp
MCP client config
{
"mcpServers": {
"f5-distributed-cloud-terraform-provider": {
"command": "npx",
"args": [
"-y",
"@robinmordasiewicz/f5xc-terraform-mcp"
]
}
}
}Distributed as an MCP bundle (`https://github.com/robinmordasiewicz/terraform-provider-f5xc/releases/download/v3.24.0/f5xc-terraform-mcp-3.24.0.mcpb`) — download it and import the bundle in your MCP client.
Terraform Provider for F5 Distributed Cloud
Community Terraform provider for F5 Distributed Cloud.
⚠️ Version 3.0.0 Clean Break Release
IMPORTANT: This is a pre-release clean break version that requires recreating all Terraform-managed resources.
- No in-place upgrade: You cannot upgrade from earlier versions without destroying and recreating resources
- API v2 based: Uses F5 Distributed Cloud API v2 specifications (98 resources available)
- No backwards compatibility: All state upgrade infrastructure has been removed
- Import supported: You can still import existing F5XC resources using
terraform import
This is a pre-release project. See CHANGELOG.md for complete details on breaking changes and migration requirements.
Installation
terraform {
required_providers {
f5xc = {
source = "robinmordasiewicz/f5xc"
}
}
}
provider "f5xc" {}
Authentication
Set your API token as an environment variable:
export F5XC_API_TOKEN="your-api-token"
Documentation
Contributing
This provider uses automated workflows for documentation generation and releases:
- Documentation: Auto-generated from OpenAPI specs on merge to main
- Releases: Triggered automatically using semantic versioning based on conventional commits
- Testing: All PRs require passing tests and lint checks
All substantive changes (code, documentation, configuration) automatically trigger a new release with appropriate version bumping.
For detailed contribution guidelines, see CLAUDE.md.
