FoggyKitchen Terraform/OpenTofu blueprints, landing zones, modules, and labs.
MCPpedia last refreshed this data
io.github.foggykitchen/foggykitchen-mcp is an MCP server that FoggyKitchen Terraform/OpenTofu blueprints, landing zones, modules, and labs. Its tool list has not been published yet over http, requires no API key, and scores 42/100 on MCPpedia's security, maintenance and efficiency rubric.
Config is the same across clients — only the file and path differ.
{
"mcpServers": {
"foggykitchen": {
"url": "https://foggykitchen.com/mcp",
"type": "http",
"oauth_resource": "https://foggykitchen.com/mcp"
}
}
}Are you the author?
Add this badge to your README to show your security score and help users find safe servers.
Bring FoggyKitchen cloud architecture context directly into the AI coding tool you already use.
No automated test available for this server. Check the GitHub README for setup instructions.
Five weighted categories — click any category to see the underlying evidence.
No known CVEs.
No package registry to scan.
Be the first to review
Have you used this server?
Share your experience — it helps other developers decide.
Sign in to write a review.
Others in cloud
MCP Server for GCP environment for interacting with various Observability APIs.
Evidence-grounded agent memory with mandatory provenance, on local SQLite or Cloudflare D1
MCP Server for kubernetes management commands
Upload, organize, search, and transform images, videos, and files with AI-powered tools.
MCP Security Weekly
Get CVE alerts and security updates for io.github.foggykitchen/foggykitchen-mcp and similar servers.
Start a conversation
Ask a question, share a tip, or report an issue.
Sign in to join the discussion.
Bring FoggyKitchen cloud architecture context directly into the AI coding tool you already use.
FoggyKitchen MCP gives compatible AI coding agents controlled access to FoggyKitchen Terraform/OpenTofu modules, implementation examples, architecture patterns, landing-zone guidance, and entitlement-aware technical catalog resources.
It is designed for engineers working with Azure, Oracle Cloud Infrastructure, Terraform/OpenTofu, AKS, OKE, cloud networking, private connectivity, landing zones, and multicloud architectures.
FoggyKitchen MCP is not another hosted LLM, a Terraform execution service, or a generic documentation search engine. It is an entitlement-aware context layer between FoggyKitchen technical assets and your own AI coding agent.
Professional+ required for FoggyKitchen technical catalog MCP access.
Users authenticate with FoggyKitchen. Available MCP capabilities depend on workspace plan and entitlements. Starter remains focused on self-study and platform access; Professional+ enables technical catalog MCP access for compatible AI coding clients.
Help the AI agent locate reviewed FoggyKitchen modules by cloud, architecture intent, topic, repository, and implementation context. The goal is to lead the agent toward an existing FoggyKitchen building block before generating generic infrastructure code from scratch.
Use FoggyKitchen context for scenarios such as Azure hub-and-spoke, Azure Firewall transit, private AKS, OCI VCN architecture, private OKE, Autonomous Database private access, OCI landing zones, private endpoints, routing, and OCI <-> Azure connectivity.
Allow the AI client to discover labs, examples, and implementation scenarios so it can point engineers toward working usage patterns rather than only generic documentation.
FoggyKitchen MCP helps Codex and Claude Code reason about architecture decisions, module selection, implementation paths, networking trade-offs, and deployment structure while the engineer stays in the coding workflow.
FoggyKitchen MCP returns only assets and capabilities available to the authenticated FoggyKitchen workspace. Professional+ is currently the entry point for technical catalog MCP access.
Use FoggyKitchen MCP.
Design an Azure hub-and-spoke architecture with Azure Firewall,
private AKS and centralized egress.
First identify relevant FoggyKitchen modules or architecture assets,
then explain the implementation approach.
Use FoggyKitchen MCP.
I need a private OKE cluster in OCI.
Find the relevant FoggyKitchen networking and OKE assets and propose
the VCN, subnet, routing and private access architecture before generating code.
Use FoggyKitchen MCP.
Review my Terraform architecture for Azure private networking.
Identify architectural risks, routing problems and missing private connectivity
patterns, and relate your recommendations to FoggyKitchen resources where possible.
Use FoggyKitchen MCP.
Resolve the architecture for an Azure firewall transit landing zone.
Prefer FoggyKitchen landing-zone or blueprint assets over generic examples.
Use FoggyKitchen MCP.
Help me design private OCI-to-Azure connectivity.
Identify relevant FoggyKitchen architecture patterns and explain the routing,
DNS and security decisions I need to make.
Engineer
|
v
Codex / Claude Code
|
v
FoggyKitchen M
... [View full README on GitHub](https://github.com/foggykitchen/foggykitchen-mcp#readme)