FoggyKitchen MCP
Connects Codex to the FoggyKitchen MCP endpoint, enabling use of FoggyKitchen tools within Codex.
README
FoggyKitchen MCP for Codex
Community Codex plugin scaffold for connecting Codex to the FoggyKitchen MCP endpoint.
Status
This repository is an early local scaffold. The stdio bridge and token handling are implemented, but the Codex plugin manifest should be validated against the installed Codex plugin schema before publishing.
Requirements
- Node.js 18 or newer
- A FoggyKitchen personal access token
- Codex with local plugin support
Configuration
Set your token as an environment variable:
export FOGGYKITCHEN_MCP_TOKEN="your_token_here"
Optionally override the endpoint:
export FOGGYKITCHEN_MCP_URL="https://foggykitchen.com/mcp"
Do not commit real tokens. If a token has been pasted into chat, shell history, or source control, rotate it.
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
Restart Codex or start a new thread after installing so the MCP tools are loaded.
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.jsondeclares the Codex plugin metadata..mcp.jsondeclares the local MCP stdio bridge for Codex.mcp/foggykitchen-stdio-bridge.mjsexposes a local stdio MCP bridge and forwards tool requests to FoggyKitchen.skills/foggykitchen/SKILL.mdteaches Codex when and how to use the plugin.scripts/list-tools.mjsis a direct HTTP smoke test.
Publishing Checklist
- Validate
.codex-plugin/plugin.jsonagainst the current Codex plugin schema. - Confirm FoggyKitchen permits public client integrations for this endpoint.
- Replace this status note with installation instructions verified on a clean machine.
- Add a license file.
- Add examples using non-secret placeholder values only.
Recommended Servers
playwright-mcp
A Model Context Protocol server that enables LLMs to interact with web pages through structured accessibility snapshots without requiring vision models or screenshots.
Magic Component Platform (MCP)
An AI-powered tool that generates modern UI components from natural language descriptions, integrating with popular IDEs to streamline UI development workflow.
Audiense Insights MCP Server
Enables interaction with Audiense Insights accounts via the Model Context Protocol, facilitating the extraction and analysis of marketing insights and audience data including demographics, behavior, and influencer engagement.
VeyraX MCP
Single MCP tool to connect all your favorite tools: Gmail, Calendar and 40 more.
graphlit-mcp-server
The Model Context Protocol (MCP) Server enables integration between MCP clients and the Graphlit service. Ingest anything from Slack to Gmail to podcast feeds, in addition to web crawling, into a Graphlit project - and then retrieve relevant contents from the MCP client.
Kagi MCP Server
An MCP server that integrates Kagi search capabilities with Claude AI, enabling Claude to perform real-time web searches when answering questions that require up-to-date information.
E2B
Using MCP to run code via e2b.
Neon Database
MCP server for interacting with Neon Management API and databases
Exa Search
A Model Context Protocol (MCP) server lets AI assistants like Claude use the Exa AI Search API for web searches. This setup allows AI models to get real-time web information in a safe and controlled way.
Qdrant Server
This repository is an example of how to create a MCP server for Qdrant, a vector search engine.