---
title: "Comment by Nabarun Mukherjee on \"I Made My API MCP-Ready Without Writing a Single Tool by Hand\" | Hashnode"
description: "Liked the shared websocket logic here. How are you planning to scale it especially when mcp is horizontally scaled"
url: "https://hashnode.com/posts/i-made-my-api-mcp-ready-without-writing-a-single-tool-by-hand/6a7a107994c7f1135dd7bbbc/comment/6a7a194f992a3ad846f7d6c7"
---

[Discussion](https://hashnode.com/posts/i-made-my-api-mcp-ready-without-writing-a-single-tool-by-hand/6a7a107994c7f1135dd7bbbc)

Comment [I Made My API MCP-Ready Without Writing a Single Tool by Hand](https://hashnode.com/posts/i-made-my-api-mcp-ready-without-writing-a-single-tool-by-hand/6a7a107994c7f1135dd7bbbc)

[Nabarun Mukherjee](https://hashnode.com/@naveroo)

[Aug 10](https://hashnode.com/posts/i-made-my-api-mcp-ready-without-writing-a-single-tool-by-hand/6a7a107994c7f1135dd7bbbc/comment/6a7a194f992a3ad846f7d6c7)

Liked the shared websocket logic here. How are you planning to scale it especially when mcp is horizontally scaled

[Kunal Gupta](https://hashnode.com/@kunalforked)

[Aug 12](https://hashnode.com/posts/i-made-my-api-mcp-ready-without-writing-a-single-tool-by-hand/6a7a107994c7f1135dd7bbbc/comment/6a7a194f992a3ad846f7d6c7#reply-6a7c750de87a1df5c8d2df14)

The version I described only really works in a single instance. The version I described only really works in a single instance. In my current setup, MCP and FastAPI are intentionally mapped 1:1, each MCP instance maintains its own WebSocket connection with its corresponding FastAPI instance. So the Future and request\_id stay local to that pair.
