You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@@ -65,15 +66,7 @@ That's it! Your auto-generated MCP server is now available at `https://app.base.
65
66
66
67
## Documentation, Examples and Advanced Usage
67
68
68
-
FastAPI-MCP provides comprehensive documentation in the `docs` folder:
69
-
-[Best Practices](docs/00_BEST_PRACTICES.md) - Essential guidelines for converting APIs to MCP tools safely and effectively
70
-
-[FAQ](docs/00_FAQ.md) - Frequently asked questions about usage, development and support
71
-
-[Tool Naming](docs/01_tool_naming.md) - Best practices for naming your MCP tools using operation IDs
72
-
-[Connecting to MCP Server](docs/02_connecting_to_the_mcp_server.md) - How to connect various MCP clients like Cursor and Claude Desktop
73
-
-[Authentication and Authorization](docs/03_authentication_and_authorization.md) - How to authenticate and authorize your MCP tools
74
-
-[Advanced Usage](docs/04_advanced_usage.md) - Advanced features like custom schemas, endpoint filtering, and separate deployment
75
-
76
-
Check out the [examples directory](examples) for code samples demonstrating these features in action.
69
+
FastAPI-MCP provides [comprehensive documentation](https://fastapi-mcp.tadata.com/). Additionaly, check out the [examples directory](examples) for code samples demonstrating these features in action.
77
70
78
71
## FastAPI-first Approach
79
72
@@ -83,7 +76,7 @@ FastAPI-MCP is designed as a native extension of FastAPI, not just a converter t
83
76
84
77
-**ASGI transport**: Communicates directly with your FastAPI app using its ASGI interface, eliminating the need for HTTP calls from the MCP to your API
85
78
86
-
-**Unified infrastructure**: Your FastAPI app doesn't need to run separately from the MCP server (though [separate deployment](docs/04_advanced_usage.md#deploying-separately-from-original-fastapi-app) is also supported)
79
+
-**Unified infrastructure**: Your FastAPI app doesn't need to run separately from the MCP server (though [separate deployment](https://fastapi-mcp.tadata.com/advanced/deploy#deploying-separately-from-original-fastapi-app) is also supported)
87
80
88
81
This design philosophy ensures minimum friction when adding MCP capabilities to your existing FastAPI services.
0 commit comments