FoggyKitchen MCP server

FoggyKitchen MCP for Codex & Claude Code

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.

Explore FoggyKitchen MCP ->

Membership / Professional+ ->

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.

What can FoggyKitchen MCP do?

Find the right Terraform/OpenTofu module

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.

Resolve architecture patterns

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.

Bring implementation examples into the coding loop

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.

Use architecture context while coding

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.

Keep access entitlement-aware

FoggyKitchen MCP returns only assets and capabilities available to the authenticated FoggyKitchen workspace. Professional+ is currently the entry point for technical catalog MCP access.

Try these prompts

Azure hub-and-spoke

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.

OCI private OKE

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.

Architecture review

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.

Landing zone discovery

Use FoggyKitchen MCP.

Resolve the architecture for an Azure firewall transit landing zone.

Prefer FoggyKitchen landing-zone or blueprint assets over generic examples.

OCI / Azure multicloud

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.

How it works

Shortened. The full README is on GitHub.