Opentofu MCP Server

OpenTofu registry research begins with search-opentofu-registry, which covers providers and modules alongside resources and data sources. Search terms stay simple, without repository-style prefixes. Once a component is identified, get-provider-details retrieves provider information using a namespace and name, while get-module-details looks up a module using its namespace, name, and target. Provider lookups omit the terraform-provider- prefix; module lookups use the simple module name rather than a full repository name. This separates broad discovery from requests about a specific registry entry.

Documentation requests use separate tools for resources and data sources. get-resource-docs takes provider identifiers plus a resource name, whereas get-datasource-docs takes provider identifiers plus a data source name. In both cases, the provider is specified by namespace and name. OpenTofu configuration examples are also part of the content the project makes available to assistants. Access can run through a local Node.js server or the hosted Cloudflare Workers deployment, with setup documented for Claude Code and a hosted integration offered for Cursor.