Terraform MCP Server

What do you like best about the product?

It’s fast and easy to use, and it saves time when completing tasks.

What do you dislike about the product?

It has complex state management, learning is not easy for beginners, and I see some licences shifting hard.

What problems is the product solving and how is that benefiting you?

It helps me solve manual tasks like creating new VMs, which saves time and lets me focus on other work.

What do you like best about the product?

I like how IBM Terraform makes infrastructure consistent and easy to manage with code. It saves time by reducing manual setup, and version-controlled workflows make changes safer and more reliable. It helps me keep infrastructure reliable and easier to update across environments, while manual mistakes are minimized. Version control also makes changes trackable, safer to review, and simpler to roll back if needed.

What do you dislike about the product?

I find it a bit hard to learn at first, and small configuration mistakes can cause errors. Sometimes, setup and debugging can take more time than expected. It has a steep learning curve initially, and the setup can feel a bit confusing. Better error messages and simpler debugging would make it easier. The initial setup was a bit challenging mainly because the configuration took some time to understand.

What problems is the product solving and how is that benefiting you?

I use IBM Terraform to define, provision, and manage cloud infrastructure as code, making deployments consistent and less error-prone. It solves infrastructure automation issues by reducing manual work, configuration drift, and ensuring version control across environments.

What do you like best about the product?

What I like most is that it’s cloud-agnostic. It makes it easy to work in a multi-cloud environment and use multiple cloud providers without much hassle.

What do you dislike about the product?

Shared module become rigid and hard to update.

What problems is the product solving and how is that benefiting you?

It’s easy to use. It takes a one-time effort to set up, and then you can use it for repetitive workloads.

What do you like best about the product?

What I appreciate most is Terraform’s declarative approach to Infrastructure as Code, which allows me to manage resources across multiple cloud providers smoothly using one unified language. On top of that, the terraform plan command is invaluable because it gives me a clear, safe preview of the infrastructure changes that will be made before I apply anything to production.

What do you dislike about the product?

The biggest challenge I’ve had with IBM Terraform is managing the state file in collaborative environments. It can lead to merge conflicts and, if it isn’t tightly secured, may inadvertently expose sensitive data. On top of that, refactoring code—or even just renaming resources—can become frustratingly complex, and if the state isn’t perfectly synchronized, it can sometimes risk unintended infrastructure destruction.

What problems is the product solving and how is that benefiting you?

IBM Terraform addresses the challenge of manual, error-prone infrastructure provisioning by enabling us to automate and manage deployments using repeatable, versionable code. This consistency has noticeably sped up our deployment cycles, reduced configuration drift between environments, and allowed our engineering team to spend more time on development instead of ongoing operational overhead.

What do you like best about the product?

I like Terraform’s simplicity, flexibility, and ability to manage infrastructure as code. It makes infrastructure provisioning and configuration more consistent, repeatable, and easier to automate. The value is good compared to the overall cost. Terraform helps reduce manual effort, automate infrastructure management, and improve consistency, which makes it worthwhile for our workflow.

What do you dislike about the product?

The learning curve can be a bit steep for beginners, especially when dealing with complex configurations and state management. Troubleshooting errors can also sometimes be challenging and time-consuming.

What problems is the product solving and how is that benefiting you?

Terraform helps automate and standardize infrastructure provisioning and management, reducing manual effort and configuration errors. It also makes deployments more consistent and repeatable, which saves time and improves overall efficiency.

What do you like best about the product?

What I like most about Terraform is that it makes infrastructure management more consistent and repeatable. I can define infrastructure as code instead of creating resources manually, which helps reduce configuration mistakes. I also like the plan and apply workflow because I can review the changes before making them. Terraform works well with cloud platforms and other tools, and the reusable modules make it easier to manage infrastructure across different environments. The value is good compared to the cost. Terraform saves time by reducing manual infrastructure work and making deployments more consistent and repeatable. The benefits of automation, reusable configurations, and easier infrastructure management make it worth the investment for teams using it regularly.

What do you dislike about the product?

Terraform can have a learning curve for people who are new to Infrastructure as Code, especially when working with state files, modules, providers, and complex configurations. Troubleshooting errors can sometimes take time because the error messages are not always easy to understand. Managing state and keeping configurations consistent across multiple environments can also require extra effort. Better error messages and simpler guidance for common issues would make the experience easier.

What problems is the product solving and how is that benefiting you?

Terraform solves the problem of managing infrastructure manually across different environments. Instead of creating cloud resources one by one, I can define the infrastructure as code and use the same configuration whenever needed. This makes deployments more consistent and reduces manual errors. It also helps with managing development, testing, and production environments in a more organized way. Using reusable modules and version-controlled Terraform code makes infrastructure changes easier to review, repeat, and maintain.

What do you like best about the product?

I’ve used IBM Cloud Terraform, and my experience has been very smooth and user experience is great. It’s easy to connect to the services I’ve been creating, and it delivers quick results once we deploy. I also find it straightforward to configure the cloud services we need. The pricing feels very reasonable for what’s provided, and overall it’s cost-effective. If any issues come up, there’s plenty of documentation I can refer to in order to understand and fix them. The chatbot and AI integration support is also very beneficial.

What do you dislike about the product?

The module and structure take time to learn, it there was a tutorial it would be better. Debugging is difficult

What problems is the product solving and how is that benefiting you?

Before using IBM Cloud Terraform, managing and configuring cloud infrastructure manually was more time-consuming and required more effort to keep configurations consistent. With Terraform, we can automate infrastructure provisioning and configuration, making it easier to connect and manage the cloud services we need. This has helped us deploy services faster, reduce manual configuration work, and maintain more consistent infrastructure across environments. It also makes it easier to troubleshoot and update our infrastructure when requirements change.

What do you like best about the product?

They provide a unified interface for lifecycle management and a single workflow for managing multiple systems such as cloud and SaaS. With Terraform, you can manage infrastructure using human-readable config files.

What do you dislike about the product?

It's not beginner-friendly as beginners struggle in debugging and module construction. Another issue is that Python and Ruby support was stopped.

What problems is the product solving and how is that benefiting you?

Terraform has helped me in creating servers and databases as it automatically detects what to build first, such as network before VM. Setting up cloud servers, databases, and networks manually is no longer required; instead, it's done by writing in human-readable config files.

What do you like best about the product?

A reliable tool for teams looking to manage infrastructure efficiently through Infrastructure as Code.

What do you dislike about the product?

Some advanced configurations require a good understanding of Terraform and cloud infrastructure.

What problems is the product solving and how is that benefiting you?

It benefits me by reducing manual effort and making infrastructure changes easier to manage.

What do you like best about the product?

One of the strongest aspects of IBM Terraform is how consistently and repeatably it supports infrastructure as code. I can define infrastructure declaratively, which keeps deployments predictable and straightforward to manage in version control. I also value its multi-cloud flexibility: it works smoothly across different providers, so it fits well in hybrid environments. Reusable modules are another plus, since they help standardize configurations and cut down on duplicated work. On top of that, it integrates nicely with CI/CD pipelines, making automated infrastructure provisioning easier to set up and maintain. Overall, it boosts efficiency, reduces manual errors, and helps keep environments consistent.

What do you dislike about the product?

One of the main challenges I’ve faced with IBM Terraform is handling the state, especially when working in a team. If the backend and locking are not set up properly, it can easily lead to conflicts. It also took me some time to get comfortable with concepts like modules, dependencies, and state management, so the learning curve can feel a bit steep in the beginning. Debugging is another area that could be better, as the error messages are not always clear and sometimes take time to figure out. Also, as the configurations grow, things can get a bit messy without proper structure and best practices in place.
On the positive side, integrations are quite good. I’ve used it with CI/CD tools like Jenkins and GitHub Actions, and it fits well into the pipeline for automating infrastructure deployments. Performance is generally reliable for most use cases, though I have noticed that execution can slow down a bit with larger or more complex setups.
For onboarding, the documentation is helpful, but as a new user, I felt it could use more practical examples or guided steps to make it easier to get started. From an ROI perspective, it definitely helps reduce manual work and keeps environments consistent, which is valuable when managing multiple setups.
In terms of UI/UX, since it is mostly code-driven, it works well for developers but might not feel very intuitive for someone expecting a graphical interface. Better visualization of infrastructure would be a useful improvement.
As for AI features, there isn’t much built-in intelligence right now. It would be helpful if it could suggest fixes, provide smarter error explanations, or give recommendations while writing configurations.

What problems is the product solving and how is that benefiting you?

In my experience, IBM Terraform helps solve the problem of managing infrastructure manually, which can be time-consuming and error-prone. Before using it, setting up environments across dev, QA, and production used to require a lot of manual effort and often led to inconsistencies. With Terraform, we are able to define everything as code, which makes deployments more predictable and repeatable.
It has also helped us handle multi-environment setups more efficiently by reusing configurations and maintaining consistency across environments. Integration with CI/CD pipelines has made it easier to automate infrastructure provisioning along with application deployments, reducing the overall deployment time.
Another key benefit is better version control and tracking of infrastructure changes, which improves visibility and reduces the risk of configuration drift. Overall, it has improved productivity, reduced manual errors, and made it easier for the team to collaborate on infrastructure changes in a structured way.