fastapi_mcp vs hwp-mcp
fastapi_mcp: FastAPI-MCP allows you to expose your existing FastAPI endpoints as Model Context Protocol (MCP) tools. It offers native integration with FastAPI, including built-in authentication using existing dependencies, and preserves schemas and documentation.; hwp-mcp: hwp-mcp is an MCP server for reading and writing Korean Hangul (.hwp / .hwpx) documents from Claude, Cursor, ChatGPT and any MCP-compatible client. It supports reading both .hwp and .hwpx formats, and writing (find/replace, template filling, new document creation) for .hwpx. Built on top of the rhwp engine, it provides 34 MCP tools for text manipulation, table editing, image handling, rendering, and document creation.
TL;DR
- You already have a FastAPI application and want to expose its endpoints as MCP tools while reusing your existing FastAPI authentication dependencies and Swagger schemas.
- You want to mount the MCP server directly onto your ASGI app or deploy it separately under an MIT license.
- You are building a standalone MCP server from scratch rather than wrapping a FastAPI app; use FastMCP or the official MCP Python SDK.
- You need an actively updated repository (last push was November 2025).
Automate reading and extracting content from Korean government or business Hangul documents
Side-by-Side Comparison
Features
Use Cases
Best For
FAQ
Deploy on DigitalOcean
Host your MCP servers, Docker containers, and AI agents with $200 free credit over 60 days.