cli vs fastapi_mcp
cli: Archcore CLI provides a Git-native context layer for AI coding agents, storing project knowledge like architecture decisions and rules within a `.archcore/` directory, versioned with your code. This ensures agents load relevant, structured context at session start, improving their ability to follow conventions and decisions, and enabling new decisions to be recorded as durable context.; 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.
TL;DR
Ensuring AI agents follow established architecture decisions and coding conventions.
- 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).
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.