MCP v0.5.2 Update #26
Conversation
| ```shell | ||
| ... | ||
| --env MCP_ENABLE=1 \ | ||
| --env MCP_UPLINK=1 \ |
There was a problem hiding this comment.
In v0.5.2, if a schema isn't provided, it will get fetched from uplink by default.
| | `MCP_LOG_LEVEL` | Change the level at which the MCP Server logs, possible values: `ERROR`, `WARN`, `INFO`, `DEBUG`, `TRACE` | | ||
| | `MCP_SSE` | Use SSE as the transport protocol rather than streamable HTTP | | ||
| | `MCP_UPLINK` | Enable use of Uplink to get the schema and persisted queries (Requires `APOLLO_KEY` and `APOLLO_GRAPH_REF`) | | ||
| | `MCP_UPLINK_MANIFEST` | Enable use of Uplink to get the persisted queries (Requires `APOLLO_KEY` and `APOLLO_GRAPH_REF`) | |
There was a problem hiding this comment.
The MCP server will default to the default MCP tools from operation collections unless this environment variable is set.
Dockerfile
Outdated
| ARG APOLLO_MCP_SERVER_VERSION=0.5.2 | ||
|
|
||
| LABEL org.opencontainers.image.version=0.0.5 | ||
| LABEL org.opencontainers.image.version=0.0.6 |
There was a problem hiding this comment.
You shouldn't need to bump the container version here, as the only changes relate to the MCP Server itself
There was a problem hiding this comment.
Thanks for your review, @jonathanrainer. I restored the version. QQ: When are we supposed to bump this?
There was a problem hiding this comment.
If there are changes made to the actual running of the container itself (OS changes, system dependencies etc.) if we're just changing it so its compatible with the latest version of something inside it we should rely on that version bump instead.
In reality I imagine that version won't change a huge amount
This PR updates Apollo MCP Server to v0.5.2 within AIO Container.