mcp_server

The peppemas-mcp_server is a C++ implementation of a Model Context Protocol (MCP) server with a pluggable plugin architecture. It loads plugins from a directory specified at runtime and handles client requests via a modular core that can be extended by these plugins. The server exposes resources, prompts, tools, and other capabilities through a plugin system, allowing you to enable or disable features as needed. As described in the repository, available plugin examples include a Weather Plugin, a Sleep Plugin, and a Code Review Plugin, which illustrate how external data fetching, timing controls, and code-analysis functionality can be integrated into the MCP workflow. “Claude Desktop Configuration” examples show how to wire the server into Claude’s MCP client, but the server is usable in any MCP client that follows the protocol.

To use the server, first ensure the executable mcp_server is built on your platform. Run the server with the desired plugin directory and log settings, then connect an MCP client to port 8080 (or your configured port) using the appropriate transport (Stdio, SSE, or HttpStream). The plugin system will dynamically load libraries from the specified plugins directory and register their capabilities with the core, enabling requests and operations defined by each plugin. If you need to customize behavior or add new capabilities, implement a new plugin following the provided examples and place it in the plugins directory so the server can discover and load it at startup.

Prerequisites:\n- A modern C++ toolchain (e.g., g++, clang++) and CMake.\n- Git to clone the repository.\n- Optional: a compatible IDE for easier navigation.\n\nStep-by-step installation:\n1) Clone the repository:\n git clone https://github.com/peppemas/mcp_server.git\n\n2) Build the server:\n mkdir -p mcp_server/build\n cd mcp_server/build\n cmake ..\n make\n\n3) Prepare a plugins directory (optional but recommended):\n mkdir -p mcp_server/plugins\n # place any plugin libraries here (e.g., WeatherPlugin.so, SleepPlugin.so)\n\n4) Run the server:\n # Basic run with a predetermined logs directory (must exist)\n ./mcp_server -l ./logs -p ./plugins\n\n5) If you need a different log path or server name, use the CLI options described in the README (e.g., -n for name, -p for plugins, -l for logs).\n\nPrerequisites recap:\n- C++ compiler and CMake\n- Git\n- Optional: dependencies required by specific plugins (documented with each plugin)\n

Notes and tips:\n- Ensure the logs directory exists before starting the server, or the server will fail to initialize as described in the README.\n- Plugins are loaded dynamically from the plugins directory; to add capabilities, drop your plugin library into that directory and restart the server.\n- The README mentions several example plugins (Weather, Sleep, Code Review) to illustrate how to extend the server; use them as templates for your own functionality.\n- If you encounter build issues on Windows, macOS, or Linux, confirm that the compiler toolchain matches the platform guidelines in the README (e.g., GCC on Linux/macOS, MINGW64 on Windows).\n- When debugging, enable verbose logs if supported by your build to quickly identify plugin load failures or missing symbols.\n- The server supports multiple transports (Stdio, SSE, HttpStream) for client compatibility; ensure your client uses a supported transport.\n