Skip to main content
Glama
Qvakk

Terraform Registry MCP Server

by Qvakk
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
PORTNoHTTP server port (default: 3002)3002
TRANSPORT_MODENoTransport mode: stdio (default) or httpstdio

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
search_modulesA

Search for Terraform modules in the public registry.

Args:
    query: Search query string (module name or keywords)
    provider: Filter by provider (e.g., 'aws', 'azurerm', 'google')
    offset: Pagination offset (default: 0)
    limit: Maximum results to return (default: 20, max: 50)

Returns:
    Dictionary containing search results with module names, providers, descriptions
get_module_detailsB

Get detailed information about a specific Terraform module.

Args:
    namespace: Module namespace/publisher (e.g., 'terraform-aws-modules')
    name: Module name (e.g., 'vpc')
    provider: Provider name (e.g., 'aws')
    version: Module version (default: 'latest')

Returns:
    Dictionary containing detailed module information including inputs, outputs, resources
get_latest_module_versionA

Get the latest version of a Terraform module.

Args:
    namespace: Module namespace/publisher
    name: Module name
    provider: Provider name

Returns:
    Dictionary containing the latest version number and published date
list_module_versionsB

List all available versions of a Terraform module.

Args:
    namespace: Module namespace/publisher
    name: Module name
    provider: Provider name

Returns:
    Dictionary containing all available versions
search_providersB

Search for Terraform providers in the public registry.

Args:
    query: Search query (provider name or keywords, optional)
    tier: Filter by tier ('official', 'partner', 'community', optional)
    offset: Pagination offset (default: 0)
    limit: Maximum results to return (default: 20, max: 100)

Returns:
    Dictionary containing provider search results
get_provider_detailsC

Get detailed information about a specific Terraform provider.

Args:
    namespace: Provider namespace (e.g., 'hashicorp')
    name: Provider name (e.g., 'aws', 'azurerm', 'google')
    version: Provider version (default: 'latest')

Returns:
    Dictionary containing detailed provider information
get_latest_provider_versionB

Get the latest version of a Terraform provider.

Args:
    namespace: Provider namespace (e.g., 'hashicorp')
    name: Provider name (e.g., 'aws')

Returns:
    Dictionary containing the latest version number and metadata
list_provider_versionsA

List all available versions of a Terraform provider.

Args:
    namespace: Provider namespace
    name: Provider name

Returns:
    Dictionary containing all available versions
get_provider_docsA

Get the main documentation page for a Terraform provider.

This fetches the provider's overview documentation from GitHub which typically includes:
- Version information and compatibility notes
- Authentication and configuration
- Example usage
- Important notes about breaking changes
- Upgrade guides between versions

Args:
    namespace: Provider namespace (e.g., 'hashicorp')
    name: Provider name (e.g., 'aws', 'azurerm', 'google')
    version: Provider version (default: 'latest')

Returns:
    Dictionary containing provider documentation content in markdown format
get_provider_resource_docsA

Get detailed documentation for a specific provider resource.

Fetches the full documentation from GitHub including:
- Description and use cases
- Example usage code
- Argument reference (required and optional)
- Attribute reference (exported values)
- Import instructions
- Timeouts configuration

Args:
    namespace: Provider namespace (e.g., 'hashicorp')
    name: Provider name (e.g., 'aws')
    resource_name: Resource name (e.g., 'aws_instance', 'azurerm_virtual_machine')
    version: Provider version (default: 'latest')

Returns:
    Dictionary containing detailed resource documentation in markdown format
get_provider_data_source_docsA

Get detailed documentation for a specific provider data source.

Fetches the full documentation from GitHub including:
- Description and use cases
- Example usage code
- Argument reference
- Attribute reference (exported values)

Args:
    namespace: Provider namespace (e.g., 'hashicorp')
    name: Provider name (e.g., 'aws')
    data_source_name: Data source name (e.g., 'aws_ami', 'azurerm_subscription')
    version: Provider version (default: 'latest')

Returns:
    Dictionary containing detailed data source documentation in markdown format
search_provider_docsA
Search within provider documentation for specific errors, topics, or troubleshooting info.

Useful for questions like:
- "What does error X mean?"
- "How do I configure authentication?"
- "What are the timeout options?"
- "How do I handle rate limiting?"

Args:
    namespace: Provider namespace (e.g., 'hashicorp')
    name: Provider name (e.g., 'aws', 'azurerm')
    query: Search terms or error message to look for
    version: Provider version (default: 'latest')

Returns:
    Dictionary containing search results with matched sections from documentation

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.9/5.0

Scored across 12 tools

Disambiguation5/5

Every tool has a clearly distinct purpose with no ambiguity. The tools are well-organized into modules vs providers, version retrieval vs detailed documentation, and search vs specific lookups. Even tools like get_provider_docs and get_provider_resource_docs target different documentation scopes (overview vs specific resource).

Naming Consistency5/5

All tools follow a consistent verb_noun pattern with perfect regularity. The naming convention uses get_, list_, and search_ prefixes consistently across modules and providers, making the tool set highly predictable and readable.

Tool Count5/5

With 12 tools, this server is well-scoped for the Terraform Registry domain. It provides comprehensive coverage for both modules and providers, including version management, detailed information retrieval, documentation access, and search capabilities. Each tool earns its place without redundancy.

Completeness5/5

The tool surface offers complete coverage for interacting with the Terraform Registry. It supports the full lifecycle from discovery (search_modules, search_providers) to version management (list/get versions) to detailed documentation (provider docs, resource docs, data source docs). There are no obvious gaps for typical agent workflows.

Maintenance

ActivityInactive
ResponsivenessNo issues

Resources