Publish to Official MCP Registry #129
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
nathanjcochran
commented
Dec 15, 2025
Comment on lines
+49
to
+64
| "environmentVariables": [ | ||
| { | ||
| "name": "TIGER_PUBLIC_KEY", | ||
| "description": "Tiger Cloud API public key for authentication", | ||
| "format": "string", | ||
| "isRequired": true, | ||
| "isSecret": false | ||
| }, | ||
| { | ||
| "name": "TIGER_SECRET_KEY", | ||
| "description": "Tiger Cloud API secret key for authentication", | ||
| "format": "string", | ||
| "isRequired": true, | ||
| "isSecret": true | ||
| } | ||
| ] |
Member
Author
There was a problem hiding this comment.
Need to verify that MCP clients actually pass these into the Docker container (e.g. via the -e argument). Otherwise, might need to remove these and add -e arguments to runtimeArguments above.
Askir
approved these changes
Dec 16, 2025
nathanjcochran
force-pushed
the
nathan/publish-mcp-registry
branch
from
375b980 to
a62b59f
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR is branched off of #128.
Wires up GoReleaser to publish a
server.jsonfile to the Official MCP Registry, which makes it possible to install the Tiger MCP server (running via a Docker container) into any MCP client that supports the registry (though I'm not sure any actually exist in the wild yet). Theserver.jsonfile lists the required environment variables (for passing in login credentials) and bind mounts (for syncing the config file(s) and.pgpassfile out of the container to the user's machine). MCP clients that support installing from the registry should (in theory) prompt users for the necessary inputs.Note that I considered using GoReleaser's new built-in support for publishing to the Official MCP Registry (see these docs), but upon trying it, I noticed that it was lacking support for several of the
server.jsonfields we need to supply (such asruntimeArgumentsandenvironmentVariables), and I encountered a few bugs as well. I believe that's just because it's so new. Hopefully we will be able to switch over to using that at some point in the future, once it becomes a bit more mature/stable.Closes AGE-312