I will add native mcp support inside your backend codebase

I build MCP support directly into your existing FastAPI/Django backend same repo, same deployment, direct database access instead of wrapping your API from the outside. I did exactly this at my job: added an MCP layer inside our production Django/FastAPI microservices so it shares the same models, auth, and deployment as the rest of the system.

The difference from a wrapped MCP server: no extra service calling your API over HTTP. The MCP tools live inside your codebase and can query your database, use your existing business logic, and respect your existing auth directly faster, and one less moving part to deploy.

What I handle:

• Adding MCP tool/resource definitions inside your existing backend project
• Wiring them to your database/ORM and existing auth, not just your public API
• Docker-based deployment so it ships as part of your current service
• Basic error handling so a bad tool call doesn't take down your app

Good fit if: you own the backend codebase (or can share repo access) and want MCP built in natively. If you'd rather keep your codebase untouched and have the MCP server call your API from outside instead, see my other MCP gig that one wraps existing endpoints without any repo