← Back to context

Comment by rahimnathwani

3 days ago

If you want people to adopt your tool, you may need to explain any advantage this has over fastmcp.

It's already easy to expose a python function as an MCP server. From the fastmcp docs:

  from fastmcp import FastMCP
  
  mcp = FastMCP("Demo ")
  
  @mcp.tool
  def add(a: int, b: int) -> int:
      """Add two numbers"""
      return a + b
  
  if __name__ == "__main__":
      mcp.run()

3 comments

rahimnathwani

Reply
justvugg  3 days ago

Hi thanks for the comment, I’m not trying to replace FastMCP (or anything else), and I’m not really comparing on the “basic MCP server” use case.

PolyMCP, beyond creating MCP servers over HTTP and stdio, WASM (Pyodide) bundle to run tools in the browser/edge with an “MCP-style” tool interface,provides unified agent/orchestration across multiple MCP servers, plus an Inspector UI and production guardrails (budgets, logging, redaction, allowlists, retries).

The goal is to be a single, end-to-end toolkit for developers: tool exposure + debugging + governance + orchestration.