SEAB-7737: Scaffold MCP server - #1
Conversation
denis-yuen
left a comment
denis-yuen
left a comment
There was a problem hiding this comment.
Some minor comments, most can be spun off if needed. Some of the versions will probably trigger dependabot immediately so may as well fix now?
| strategy: | ||
| fail-fast: false | ||
| matrix: | ||
| python-version: ["3.11", "3.12", "3.13"] |
There was a problem hiding this comment.
Testing a few python versions seems like an ok idea, but why these three? They seem kind close together/redundant
There was a problem hiding this comment.
If we add "3.14", this is all of the Python versions that haven't reached end of life, minus 3.10, which EOLs very soon: https://devguide.python.org/versions/
Might as well make sure it works with all of them, easier for devs.
| ) | ||
| parser.add_argument("--host", help="Interface to bind when serving over HTTP.") | ||
| parser.add_argument("--port", type=int, help="Port to bind when serving over HTTP.") | ||
| parser.add_argument("--path", help="HTTP path the MCP endpoint is served from.") |
There was a problem hiding this comment.
may spin off ticket, presumably load balancer handles https like with the webservice, but does this need to say http or https?
There was a problem hiding this comment.
"HTTP" refers to the MCP transport, which can be either "stdio" or "http":
https://modelcontextprotocol.io/specification/2026-07-28/basic/transports
|
|
||
| ## Requirements | ||
|
|
||
| - Python 3.11 or newer (the container image uses 3.13) |
There was a problem hiding this comment.
Why not just standardize on 3.13 from the get-go?
(I don't feel strongly about this, just curious why the extra effort)
There was a problem hiding this comment.
IMHO, might as well make sure it works for the currently-supported Python versions, to make it easier to work on it. Some people don't have the latest installed.
2 participants
Description
This PR populates the mcp repository with a skeleton MCP server and rough implementations of the building/testing/containerization infrastructure. The MCP server implements a
hellotool as well as the four planned Dockstore query tools. The MCP server runs, and thehellotool works as advertised, but the guts of the other tools are not yet implemented.The goal of this PR is to initialize the repository and provide a foundation upon which to perform subsequent work. The interfaces, tools used, build system, testing, flow etc. will likely change, fundamentally, in some cases.
Issues
https://ucsc-cgl.atlassian.net/browse/SEAB-7736
https://ucsc-cgl.atlassian.net/browse/SEAB-7737