CI workflow and associated dependencies for Anthropic MCP Registry publishing #200
Conversation
…on spec for v0.3.0 of mcp server, update dockerfile with package provenance label
|
Great work here @leefowlercu - should we only dispatch it in the release branch? that's where we track our releases. There should also be a smart way to inherit the latest server version I believe, see the version file this is what we use to track the current version being release, if we release a patch version we change this of course before merging into the release branch |
server.json
Outdated
| "$schema": "https://static.modelcontextprotocol.io/schemas/2025-10-17/server.schema.json", | ||
| "name": "io.modelcontextprotocol.anonymous/terraform-mcp-server", | ||
| "title": "Terraform MCP Server", | ||
| "description": "HashiCorp MCP server for executing Terraform Cloud and Enterprise workflows, resources, and tools.", |
There was a problem hiding this comment.
Terraform MCP Server for generating more accurate Terraform configuration and executing Terraform Cloud and Enterprise workflows.
There was a problem hiding this comment.
Updated the description, but the specification enforces a 100 character maximum for that field which the new description comes in just under.
server.json
Outdated
| "url": "https://github.com/hashicorp/terraform-mcp-server", | ||
| "source": "github" | ||
| }, | ||
| "version": "0.3.0", |
There was a problem hiding this comment.
If this workflow is manual then the version needs to be an input from the GHA workflow
There was a problem hiding this comment.
Added a Make Target and associated script to update all version specifiers in the server.json file with the version from the version/VERSION file.
…n server.json from the versionfile
… specifications for k/v environment variables
…rsion of the mcp server package
|
Updated Constrained the value for the |
|
Updated outdated usage of "Terraform Cloud" with "HCP Terraform". |
2 participants
This PR introduces the following:
mcp-publisherCLI to publish this MCP Server's specification to the official Anthropic MCP Server Registry (https://registry.modelcontextprotocol.io). See GHA Registry Publishing documentation here: https://github.com/modelcontextprotocol/registry/blob/main/docs/guides/publishing/github-actions.mdDockerfileto assert package provenance. See https://github.com/modelcontextprotocol/registry/blob/main/docs/guides/publishing/publish-server.md#requirements-3server.jsonfile with the specification of this MCP Server'sv0.3.0version. Seeserver-jsondocumentation here: https://github.com/modelcontextprotocol/registry/tree/main/docs/reference/server-jsonNOTE: I was unable to do a dry-run test of publishing this server using the
server.jsonintroduced in this PR against a local test registry due to me not understanding some of the expectations of themcp-publisherCLI tool in--dry-runmode. I will update this PR when a Dry Run test has been performed and validated. Opening this PR in the meantime to allow Repsitory Maintainers to review the introduced changes.Reason for opening this PR: Introduce an automated mechanism for publishing this MCP Server's specification to the Anthropic MCP Server Registry
How to "undo" this change: Revert the commit that introduces this PR into
main. Alternatively, simply delete the GHA Workflow script, theserver.jsonfile, and remove the LABEL introduced into theDockerfile.Impact on Security Controls: None. This change does not modify the configuration or application logic of this repository's MCP Server. It simply introduces a new discovery channel.
PCI review checklist
[✅] I have documented a clear reason for, and description of, the change I am making.
[✅] If applicable, I've documented a plan to revert these changes if they require more than reverting the pull request.
[✅] If applicable, I've documented the impact of any changes to security controls.