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
When I start a server with fastmcp run server.py:mcp it starts an instance of the MCP server with stdio transport by default. What's the use case for this? If I write a client with client = fastmcp.Client("server.py") it will automatically start a new instance of the server, instead of using the server that's running in the first process. I don't understand why I would ever use the fastmcp cli to start a stdio transport server. Is it to connect from clients that do not use the fastmcp ecosystem of tools?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
-
When I start a server with
fastmcp run server.py:mcp
it starts an instance of the MCP server with stdio transport by default. What's the use case for this? If I write a client withclient = fastmcp.Client("server.py")
it will automatically start a new instance of the server, instead of using the server that's running in the first process. I don't understand why I would ever use thefastmcp
cli to start astdio
transport server. Is it to connect from clients that do not use thefastmcp
ecosystem of tools?Beta Was this translation helpful? Give feedback.
All reactions