Terraform Ingest
A Terraform RAG ingestion engine that accepts a YAML file of terraform git repository sources, downloads them locally using existing credentials, creates JSON summaries of their purpose, inputs, outputs, and providers for branches or tagged releases you specify and embeds them into a vector database for similarity searches. Includes an easy to use cli, API, or MCP server.
Features
- 📥 Multi-Repository Ingestion: Process multiple Terraform repositories from a single YAML configuration
- 🔄 Auto-Import: Import repositories from GitHub organizations and GitLab groups (Bitbucket support coming soon)
- 🔍 Comprehensive Analysis: Extracts variables, outputs, providers, modules, and descriptions
- 🏷️ Branch & Tag Support: Analyzes both branches and git tags of your choosing
- 🔌 Dual Interface: Use as a CLI tool (Click) or as a REST API service (FastAPI)
- 🤖 MCP Integration: MCP service for AI agent access to ingested modules via STDIO, SSE, or Streamable-http
- 📊 JSON Output: Generates structured JSON summaries ready for RAG ingestion
- 🔐 Credential Support: Uses existing git credentials for private repositories
- 🧠 Vector Database Embeddings: Semantic search with ChromaDB, OpenAI, Claude, or sentence-transformers
Further documentation found here
Or, if you just want the TLDR on using this as an MCP server (along with some examples) check this out.
An example project repo with a large list of custom modules for kicking the tires can be found here
Installation
This application can be run locally using uv or docker.
NOTE
uvis required for lazy-loading some large dependencies.
uv tool install terraform-ingest
# Create a config
uv run terraform-ingest init config.yaml
# Or import repositories from a GitHub organization
uv run terraform-ingest import github --org terraform-aws-modules --terraform-only
# Or import repositories from a GitLab group
uv run terraform-ingest import gitlab --group mygroup --recursive --terraform-only
# Update your config.yaml file to include your terraform module information and mcp config then preform the initial ingestion
uv run terraform-ingest ingest config.yaml
# Run a quick cli search to test things out
uv run terraform-ingest search "vpc module for aws"
## Docker
docker pull ghcr.io/zloeber/terraform-ingest:latest
# Run with volume mount for persistence, ingest modules from local config.yaml file
docker run -v $(pwd)/repos:/app/repos -v $(pwd)/output:/app/output -v $(pwd)/config.yaml:/app/config.yaml ghcr.io/zloeber/terraform-ingest:latest ingest /app/config.yaml
# Run as MCP server
docker run -v $(pwd)/repos:/app/repos -v $(pwd)/output:/app/output -v $(pwd)/config.yaml:/app/config.yaml -p 8000:8000 ghcr.io/zloeber/terraform-ingest:latest mcp -c /app/config.yaml
# Search for modules and get the first result, show all details
terraform-ingest search "vpc module for aws" -l 1 -j | jq -r '.results[0].id' | xargs -I {} terraform-ingest index get {}
License
MIT License
Contributing
Contributions are welcome! Please feel free to submit a Pull Request.
Metadata
Release files for terraform-ingest 0.1.27
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | Actions |
|---|---|---|---|---|
| terraform_ingest-0.1.27.tar.gz | 372.7 kB | With provenance | Details for terraform_ingest-0.1.27.tar.gz |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Actions Reset |
|---|---|---|---|---|
| terraform_ingest-0.1.27-py3-none-any.whl | Python 3 | none | any | Details for terraform_ingest-0.1.27-py3-none-any.whl |
Total release size: 443.4 kB
Release files / terraform_ingest-0.1.27.tar.gz
| Download URL | terraform_ingest-0.1.27.tar.gz |
|---|---|
| Size | 372.7 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
1ace23ca3da5dcc1fa8c8363b81de9668be99385c30860890af07adc7898bd6a
|
|
BLAKE2b-256 checksum How to use checksums |
377989dbba7479814f5604add7ad5aeecffd54f860f6e7579268c3ccedd5384d
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on May 18, 2026.
Transparency logRelease files / terraform_ingest-0.1.27-py3-none-any.whl
| Download URL | terraform_ingest-0.1.27-py3-none-any.whl |
|---|---|
| Size | 70.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
37d716bf64057f6da0c7c1b21a0f0603a129cc1553320a4718089a6fa5097969
|
|
BLAKE2b-256 checksum How to use checksums |
05c31277d2550233566fe883855d313379814a02f34181a40becae1189d735ec
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on May 18, 2026.
Transparency logSecurity for terraform-ingest 0.1.27
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
Full provenance
All 2 files in this release have been uploaded with provenance metadata.
Attestation for terraform_ingest-0.1.27.tar.gz
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on May 18, 2026.
Transparency logA note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.