Skip to main content
Glama
asadongit

Terraform Engine MCP Server

by asadongit
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault

No arguments

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": false
}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}
experimental
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
list_tasksA
List all available Terraform tasks (templates) in the registry.
Args:
    category: Optional category to filter tasks (e.g. database, network, compute).
    provider: Optional cloud provider to filter tasks (e.g. aws, azure, gcp).
Returns:
    JSON string representing the list of tasks and their details.
get_task_schemaA
Get the metadata and input schema (JSON Schema) for a registered task.
Args:
    task_name: The unique alphanumeric name of the task.
provision_taskA
Provision a new deployment for a given task.
Args:
    task_name: The registered task name to deploy.
    deployment_name: A unique name for this deployment instance.
    payload: JSON object/dictionary containing the variables matching the task schema.
get_deployment_statusA
Get the current status, configurations, and outputs of a deployment by its name.
Args:
    deployment_name: The unique name of the deployment to inspect.
destroy_deploymentB
Tear down and delete an existing deployment by its name.
Args:
    deployment_name: The name of the deployment to destroy.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

Deploy Server
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

A3.8/5.0

Scored across 5 tools

Disambiguation5/5

Each tool has a clearly distinct purpose: listing tasks, getting task schema, provisioning deployments, checking deployment status, and destroying deployments. No overlap or ambiguity.

Naming Consistency5/5

All tool names follow a consistent verb_noun pattern with underscores (e.g., list_tasks, provision_task, destroy_deployment), making them predictable and easy to understand.

Tool Count5/5

Five tools is an appropriate scope for managing Terraform tasks and their deployments: sufficient to cover listing, schema retrieval, provisioning, status checking, and destruction without being overwhelming.

Completeness3/5

The set covers the main lifecycle (create, read, delete) but lacks a tool to list existing deployments, which is a notable gap for agents that need to manage multiple deployments. Additionally, there is no update or modification capability.

Maintenance

ActivityMaintained
ResponsivenessNo issues

Resources