MoodMNKY MCP Server Stack

What is MoodMNKY MCP Server Stack?

MoodMNKY MCP Server Stack is a standalone repository that orchestrates a diverse array of Model Context Protocol (MCP) servers—all containerized via Docker—behind a single docker-compose.yml. It enables rapid deployment, unified configuration via a .env file, out‑of‑the‑box integration with OpenAI Agents SDK (via SSE), and optional public exposure using Cloudflare Tunnel.

How to use MoodMNKY MCP Server Stack?

Clone the repository, copy .env.example to .env, fill in all placeholders (API keys, host ports, paths), then run docker-compose up to launch all MCP servers. Verify local /tools endpoints via curl. Optionally expose servers publicly by installing and authenticating cloudflared, creating a tunnel, and configuring DNS. Integrate with OpenAI Agents SDK using MCPServerSse pointing to an SSE endpoint.

Key features of MoodMNKY MCP Server Stack

• Orchestrates 18+ MCP servers in Docker behind one compose file
• Unified environment‑variable configuration for all services
• Out‑of‑the‑box SSE integration for OpenAI Agents SDK
• Optional Cloudflare Tunnel exposure with firewall safety
• Supports servers for Notion, Brave Search, GitHub, Redis, and more
• First‑principles explanations for MCP, SSE, Docker, and tunneling

Use cases of MoodMNKY MCP Server Stack

• Rapidly deploy multiple tool‑providing MCP servers for AI agents
• Centralize API keys and host‑port bindings in a single .env file
• Connect OpenAI Agents SDK agents to MCP tools over SSE
• Securely expose MCP endpoints over the internet without opening ports

FAQ from MoodMNKY MCP Server Stack

What MCP servers are included in this stack?

The stack includes Notion, Sequential Thinking, Brave Search, Tavily, Firecrawl, Fetch, GitHub, Filesystem, Discord, Playwright, Desktop Commander, Redis‑backed Memory, and others—all defined in docker-compose.yml and configured via .env.

What prerequisites are required to run the stack?

You need Docker Engine (20.10+), Docker Compose (v2+), and optionally Cloudflare’s cloudflared for public exposure. A Cloudflare‑managed domain is required for external access.

How do I expose MCP servers publicly?

Install and authenticate cloudflared, create a tunnel, and add CNAME records in Cloudflare DNS pointing to the tunnel’s hostname. The tunnel forwards requests to local MCP ports.

How does SSE differ from streamable HTTP in this stack?

SSE is the recommended transport because it provides standardized event framing, built‑in reconnection, and works through most proxies and firewalls. All reference MCP servers in the stack default to SSE.

Where are secrets and API keys stored?

All secrets (API keys, tokens, host ports) are placed in a .env file that is never committed. The .env.example template uses <PLACEHOLDER> values that must be replaced before launching.