HCP Terraform Registry (BYOK)

HCP Terraform Registry (BYOK) — connector documentation

• MCP endpoint: https://byok-hcp-terraform-registry.connectorbay.com/mcp
• REST API: POST https://byok-hcp-terraform-registry.connectorbay.com/v1/tools/{tool_name}, described by the OpenAPI 3.1 spec at https://byok-hcp-terraform-registry.connectorbay.com/openapi.json
• Transport: Streamable HTTP, stateless, MCP specification 2025-06-18 or later
• Authentication: your own HCP Terraform Registry user, team or organization API token, sent in the X-Upstream-Key header of every request (never stored, logged or cached)
• Health: https://byok-hcp-terraform-registry.connectorbay.com/health · Tool schemas: https://byok-hcp-terraform-registry.connectorbay.com/tools.json
• Publisher: Unify Dynamics LLC · connectorbay.com/byok-hcp-terraform-registry · agent@connectorbay.com

What HCP Terraform Registry (BYOK) is for

HCP Terraform Registry (BYOK) lets an AI assistant read your own HCP Terraform Registry data through the HCP Terraform Registry API with a key you supply (user, team or organization API token). Read-only: 6 tools (list_registry_modules, get_registry_module, list_module_versions, list_registry_providers, get_registry_provider, list_provider_versions). The BYOK key travels with each request, is used for that one call only and is never stored, logged or cached; it is only ever sent to app.terraform.io. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by HCP Terraform Registry. HCP Terraform Registry and its logos are trademarks of their owners and are used only to say which service the connector works with.

Ask your assistant things like:

• "Which private Terraform modules does my organization publish?"
• "Show the vpc module for aws in my HCP Terraform private registry"
• "Which versions of the vpc module exist in my HCP Terraform private registry?"
• "Which providers are in my HCP Terraform private registry?"
• "Show the aws provider in my HCP Terraform private registry"
• "Which versions of the aws provider are in my HCP Terraform private registry?"

What it does

• list_registry_modules: List the modules available to an organization (private modules and curated public ones) with provider, status and version statuses.
• get_registry_module: Get one registry module: status, version statuses, version tags, timestamps and the VCS repository it is published from.
• list_module_versions: List the versions of a registry module with status and tags.
• list_registry_providers: List the providers in an organization's private registry (and any curated public providers) with namespace and registry.
• get_registry_provider: Get one registry provider: name, namespace, registry and timestamps.
• list_provider_versions: List the versions of a registry provider with status and tags.

BYOK key

You bring your own HCP Terraform Registry user, team or organization API token (https://app.terraform.io/app/settings/tokens). Your assistant sends it in the X-Upstream-Key header with each request. ConnectorBay uses it for that one call only: it is never stored, logged or cached, never shown in an answer, and it is only sent to app.terraform.io over https, with no redirects followed. Create a key with the fewest permissions the tools need (read-only if the provider offers it), and revoke it at the provider whenever you like.

Data sources

• https://developer.hashicorp.com/terraform/cloud-docs/api-docs/private-registry/modules (the API this connector calls, with a BYOK key)

Live from the HCP Terraform Registry API (app.terraform.io) with a BYOK key; documentation: https://developer.hashicorp.com/terraform/cloud-docs/api-docs/private-registry/modules. Endpoints checked against that documentation on 2026-10-16.

What it is not

Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by HCP Terraform Registry. HCP Terraform Registry and its logos are trademarks of their owners and are used only to say which service the connector works with. It is read-only: it never creates, changes, sends or deletes anything in your HCP Terraform Registry account.

Built for: Worldwide. Languages: English.

HCP Terraform Registry (BYOK) — Privacy Policy

Effective 24 October 2026. Unify Dynamics LLC ("we", "us"), Menlo Park, California.

What HCP Terraform Registry (BYOK) is. HCP Terraform Registry (BYOK) is a connector (an MCP server and REST API) that an AI assistant calls on your behalf to read your own HCP Terraform Registry data: Read the private registry of your HCP Terraform (Terraform Cloud) organization: modules, providers, their versions and version statuses, with your own API token. You bring your own HCP Terraform Registry user, team or organization API token; the assistant sends it to us with each request.

BYOK key. The key you supply is used to make the one HCP Terraform Registry call you asked for. Our application does not store it, write it to a log, put it in a cache, or share it. It is sent only to app.terraform.io, over https, and is removed from any text we return to you or your assistant. We do not follow redirects with your key. If HCP Terraform Registry rejects it, we say so without repeating it.

What we receive. The arguments of each tool call, the BYOK key (for that call only), the technical headers needed to serve the request (an IP address or a client identifier supplied by the assistant) and standard server logs. What HCP Terraform Registry receives. The request we make on your behalf, including the key and the arguments, under HCP Terraform Registry's own terms and privacy policy. HCP Terraform Registry acts at your direction and is the only recipient of the data of your request besides our hosting provider.

What we return. The answer HCP Terraform Registry gives for your request, trimmed to the fields the tool documents. We do not keep it: it is returned to your assistant and not stored, cached or used to train anything.

What we do not do. We do not build a profile, sell or share personal information, or keep your HCP Terraform Registry data. Rate-limit counters (a client identifier and timestamps) are held in memory for at most 24 hours. Hosting access logs (IP addresses, request paths and status codes) are kept for up to 30 days for security and abuse prevention; our application adds no request headers or bodies to them.

Sub-processors. HCP Terraform Registry (the API you call with a BYOK key, at your direction). Hosting: Vercel (United States regions).

Your rights. Because we store no personal data beyond short-lived logs, requests to access, correct or delete data are usually satisfied automatically; you can still contact agent@connectorbay.com and we will respond within 30 days. Revoke your key at HCP Terraform Registry at any time to end all access.

Children. HCP Terraform Registry (BYOK) is a general-audience service operated by the adult using the assistant, under HCP Terraform Registry's own age rules.

Changes. We will post changes here with a new effective date.

HCP Terraform Registry (BYOK) — Terms of Service

Effective 24 October 2026. These terms govern use of the HCP Terraform Registry (BYOK) connector ("the Service") operated by Unify Dynamics LLC ("we", "us").

1. The Service. HCP Terraform Registry (BYOK) provides: Read the private registry of your HCP Terraform (Terraform Cloud) organization: modules, providers, their versions and version statuses, with your own API token. It is accessed through an AI assistant or directly over MCP or HTTP, and is read-only.
2. Your own key, your own account. You must use your own HCP Terraform Registry credentials and only access data you are allowed to access. HCP Terraform Registry's terms apply to your use of HCP Terraform Registry; you are responsible for complying with them, including any rate limits and permitted uses. Do not share a key you do not own.
3. Independent. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by HCP Terraform Registry. HCP Terraform Registry and its logos are trademarks of their owners and are used only to say which service the connector works with.
4. No advice, no guarantees. Output is the data HCP Terraform Registry returns, lightly trimmed; it may be incomplete, delayed or changed by HCP Terraform Registry. Check important facts at the source.
5. Read-only. The Service does not create, change, send or delete anything in your HCP Terraform Registry account.
6. Acceptable use. Automated use within the published rate limits is welcome. Do not use the Service to access data you are not entitled to, to circumvent HCP Terraform Registry's controls, or to attack any system.
7. Availability. The Service is provided "as is" without warranty. We may change, limit or discontinue it at any time; HCP Terraform Registry may change or end its API at any time.
8. Data. Our Privacy Policy describes what we process. In short: the BYOK key is used for the one call and not stored or logged.
9. Pro keys. Optional ConnectorBay Pro API keys are issued at our discretion and are separate from your HCP Terraform Registry key.
10. Liability. To the fullest extent permitted by law, Unify Dynamics LLC is not liable for any loss arising from use of or reliance on the Service, including any action HCP Terraform Registry takes on your account. Our total liability is limited to US $100.
11. Governing law. California law; venue in San Mateo County, California.
12. Contact. Unify Dynamics LLC · agent@connectorbay.com · https://connectorbay.com/byok-hcp-terraform-registry

HCP Terraform Registry (BYOK) support

Email agent@connectorbay.com. We answer within two business days.

• MCP endpoint: https://byok-hcp-terraform-registry.connectorbay.com/mcp
• REST API: https://byok-hcp-terraform-registry.connectorbay.com/openapi.json
• Live status: https://byok-hcp-terraform-registry.connectorbay.com/health

When you report a problem, include the question you asked your agent, roughly when, and which agent you used (for example Claude, ChatGPT or Gemini). Never send us passwords, account numbers or ID numbers. HCP Terraform Registry (BYOK) never asks for them.