Does time_server Support MCP Protocol (STDIO)? Is HTTP-Only Expected? #476
Unanswered
michaelbev
asked this question in
Q&A
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
Pre-submission Checklist
Question Category
Your Question
Hi all,
I’m working with the modelcontextprotocol/servers project and using Cursor as my development environment. I noticed that most MCP servers like the Go-based toolbox server can be started in either STDIO (MCP protocol) or HTTP mode, depending on the flags you use.
However, when I use the Python-based time_server (from src/time), it appears to only support HTTP mode (serving a FastAPI/OpenAPI interface). I don’t see any option to start it in STDIO mode or to have it speak the MCP protocol over STDIO, as Cursor expects for some integrations.
My questions for the community:
Additional Context
I noticed that Cursor is able to use time_server even though it only exposes an HTTP API and does not support STDIO/MCP protocol. It seems that Cursor is smart enough to use HTTP for servers that do not specify --stdio in .cursor/mcp.json. If you start a server without --stdio, Cursor will use HTTP if the server exposes an HTTP API. This works well for time_server, but I want to confirm if this is the recommended approach for integrating HTTP-only MCP servers with Cursor, and if there are any best practices or caveats I should be aware of.
Any insights or pointers to documentation would be greatly appreciated!
Thanks in advance!
Beta Was this translation helpful? Give feedback.
All reactions