FoggyKitchen MCP for Codex & Claude Code

Community plugin scaffold for connecting Codex and Claude Code to the FoggyKitchen MCP endpoint.

Status

This repository packages the FoggyKitchen streamable HTTP MCP endpoint for both Codex and Claude Code. The Claude Code plugin manifest and marketplace files follow the current documented schema; the Codex plugin manifest should still be validated against the installed Codex plugin schema before publishing.

Related MCP server: codex-cli-mcp

Requirements

• Node.js 18 or newer

• A FoggyKitchen Professional+ membership for OAuth access to MCP tools

• Codex with local plugin support, or Claude Code

Install In Codex

Add the FoggyKitchen marketplace:

codex plugin marketplace add https://github.com/foggykitchen/foggykitchen-mcp

Then install the plugin:

codex plugin add foggykitchen-mcp@foggykitchen

Alternatively, configure the MCP server directly in ~/.codex/config.toml:

[mcp_servers.foggykitchen]
url = "https://foggykitchen.com/mcp"
oauth_resource = "https://foggykitchen.com/mcp"

Restart Codex or start a new thread after installing so the MCP tools are loaded.

Install In Claude Code

Register FoggyKitchen as a remote HTTP MCP server:

claude mcp add --transport http foggykitchen https://foggykitchen.com/mcp

You can also use this repository as a project-level MCP configuration. Claude Code auto-detects the .mcp.json at the root of this repo. It connects to https://foggykitchen.com/mcp over HTTP and uses OAuth/PKCE with FoggyKitchen. If you clone the repo and open it as a project, Claude Code will prompt you to approve the foggykitchen MCP server on first use.

Plugin installation is still supported where Claude Code plugin marketplaces are enabled:

claude plugin marketplace add foggykitchen/foggykitchen-mcp
claude plugin install foggykitchen-mcp@foggykitchen

Or from within a Claude Code session:

/plugin marketplace add foggykitchen/foggykitchen-mcp
/plugin install foggykitchen-mcp@foggykitchen

Restart Claude Code or start a new session after adding/installing the server so the MCP tools are loaded.

Quick functional test inside Claude Code:

Use FoggyKitchen MCP. Check my current access and then resolve the architecture for Azure firewall transit landing zone.

Expected result: Claude Code should call FoggyKitchen tools and lead with FoggyKitchen landing-zone/blueprint assets instead of generic vendor documentation.

Sign In With FoggyKitchen

FoggyKitchen MCP supports OAuth/PKCE for Codex and Claude Code. Start the OAuth flow from your AI coding client. FoggyKitchen Settings are used only for manual Personal MCP Tokens.

OAuth is available for Professional+ memberships. Individual Learner and Starter accounts can browse FoggyKitchen, but they cannot authorize MCP access for Codex, Claude Code, or other AI coding clients.

Codex OAuth login

STEP 1. Start login from Codex:

codex mcp login foggykitchen

STEP 2. Your browser opens FoggyKitchen. If you are not signed in, sign in first.

STEP 3. FoggyKitchen shows the OAuth approval screen with Allow access and Deny. Click Allow access.

STEP 4. Codex completes authentication and the FoggyKitchen MCP tools become available.

STEP 5. Run /mcp in Codex to verify the tool list.

Claude Code OAuth login

STEP 1. Start Claude Code, open /mcp, select foggykitchen, and authenticate. Your browser should show FoggyKitchen login if needed, then the OAuth approval screen with Allow access and Deny. After approval, Claude Code should show the server as connected.

STEP 2. Once authenticated, you can close this window:

STEP 3. Claude Code will notify you about being connected to the MCP server:

STEP 4. Review Claude Code MCP connection details:

Manual fallback: Personal MCP Token

Personal MCP Tokens remain available in FoggyKitchen Settings -> AI Developer Tools for legacy clients, smoke tests, and tools that cannot complete OAuth/PKCE yet. OAuth is the recommended flow for Codex and Claude Code.

Configuration

The Codex plugin declares the FoggyKitchen MCP endpoint as an OAuth protected resource:

{
  "mcpServers": {
    "foggykitchen": {
      "type": "http",
      "url": "https://foggykitchen.com/mcp",
      "oauth_resource": "https://foggykitchen.com/mcp"
    }
  }
}

For direct smoke tests or legacy clients that do not support OAuth yet, a Personal MCP Token can still be passed as a Bearer token. Do not commit real tokens. If a token has been pasted into chat, shell history, or source control, rotate it.

Local Smoke Test

List the tools exposed by FoggyKitchen:

npm run list-tools

Test the stdio bridge manually:

printf '%s\n' '{"jsonrpc":"2.0","id":1,"method":"initialize","params":{}}' '{"jsonrpc":"2.0","id":2,"method":"tools/list","params":{}}' | npm run bridge

Files

• .codex-plugin/plugin.json declares the Codex plugin metadata.

• .codex-plugin/mcp.json declares the FoggyKitchen MCP endpoint for Codex using url and oauth_resource.

• .claude-plugin/plugin.json declares the Claude Code plugin metadata.

• .claude-plugin/marketplace.json lists this plugin for claude plugin marketplace add / /plugin marketplace add.

• .agents/plugins/marketplace.json lists this plugin for the Codex plugin marketplace.

• .mcp.json declares the FoggyKitchen HTTP MCP endpoint for Claude Code using oauth_resource. Claude Code auto-detects this file at the project root; it is not read by Codex.

• scripts/mcp-headers.mjs remains available only for legacy Bearer-token smoke tests using FOGGYKITCHEN_MCP_AUTHORIZATION or FOGGYKITCHEN_MCP_TOKEN.

• mcp/foggykitchen-stdio-bridge.mjs remains available as a local stdio bridge fallback and forwards tool requests to FoggyKitchen.

• skills/foggykitchen/SKILL.md teaches Codex or Claude Code when and how to use the plugin.

• scripts/list-tools.mjs is a direct HTTP smoke test using FOGGYKITCHEN_MCP_AUTHORIZATION or FOGGYKITCHEN_MCP_TOKEN.

Troubleshooting

• If Claude Code or Codex reports that the MCP server is not logged in, start the OAuth flow from the client: codex mcp login foggykitchen for Codex, or /mcp authentication for Claude Code.

• If the browser opens FoggyKitchen Settings instead of the OAuth approval screen, restart the client and start login again from the MCP client. Settings are for Personal MCP Tokens, not OAuth consent.

• If a Personal MCP Token was pasted into chat, shell history, logs, or source control, rotate it in FoggyKitchen Settings -> AI Developer Tools.