What transports does oatpp-mcp support?
STDIO and HTTP SSE.
@oatpp
Basic information
Anthropic’s Model Context Protocol implementation for Oat++
No standard config provided
This server doesn't expose a parseable MCP config block in its README. See the repository for install instructions.
RepositoryTool list not available yet
This listing does not currently have a tool list to display. This does not mean the server has no tools; check its documentation for supported capabilities.
We auto-extract tools from the README. The maintainer can list them under a ## Tools heading to populate this section.
oatpp-mcp is an implementation of Anthropic’s Model Context Protocol (MCP) for the Oat++ C++ web framework. It allows developers to create MCP servers that can automatically generate tools from an ApiController, enabling LLMs to query the API. It is intended for Oat++ users who want to integrate with AI assistants via the MCP standard.
Build and install the module after installing the main oatpp module, then include it in your project. Use the oatpp::mcp::Server class to add prompts, resources, and tools, and serve via STDIO (server.stdioListen()) or HTTP SSE (attach the SSE controller to your HTTP server router). Redirect Oat++ logging to a different stream when using STDIO.
ApiController for LLM querying.STDIO and HTTP SSE.
Yes, `oatpp-mcp` can automatically generate tools from an `ApiController`, as demonstrated in a detailed tutorial and an example project.
The main [oatpp](https://github.com/oatpp/oatpp) module must be installed first.
Yes, the server supports Prompts, Resources, and Tools as defined in the MCP specification.
Use `server.stdioListen()`. Ensure you redirect Oat++ logging to a separate stream (e.g., to a file) to avoid interfering with the MCP STDIO communication.
Hindsight: Agent Memory That Learns
🚀 The fast, Pythonic way to build MCP servers and clients.
YC (S26) | Open Computer History | Continuously record your company computer work, map your workflows, help you find work worth automating, and power your agents' context
Painless E2E Automation for Mobile and Web

A good sequence diagram can solve almost any communication problem in engineering. Volley lets your agent write them as plain text, with the real request and response payloads on every arrow. It checks its own syntax wi
Comments