Skip to content

Conversation

sd2k
Copy link
Collaborator

@sd2k sd2k commented Sep 18, 2025

Addresses #290.

@sd2k sd2k marked this pull request as ready for review September 19, 2025 09:16
@sd2k sd2k requested a review from a team as a code owner September 19, 2025 09:16
@CLAassistant
Copy link

CLAassistant commented Oct 2, 2025

CLA assistant check
All committers have signed the CLA.

This comment has been minimized.

@okianus
Copy link

okianus commented Oct 3, 2025

Some notes from a conversation with @sd2k:

Two separate requirements:

  1. the MCPB manifest, which defines how the server should be packaged up for installation and consumption (independent of Docker)
  2. the server.json manifest, which is required for adding it to the registry (could either add our server as a Docker image or an MCPB package)

If we want to add it as a Docker image we need to build and tag our image, but the problem is that our Docker image isn't built by our repo but by Docker's mcp-registry repo.

We can update our Dockerfile to include the required label (LABEL io.modelcontextprotocol.server.name="io.github.username/server-name") but the issue is that those Docker builds controlled by Docker's mcp-registry repo don't include versioned tags. A better approach is to do the MCPB manifest, then use that manifest in our server.json rather than using a Docker image, so the steps would be:

  1. remove server.json and the docker build GitHub Actions workflow from that PR (for now)
  2. add a separate GitHub action to build the MCPB and add it to the GitHub releases on each tag
  3. make sure we can build the MCPB (and hopefully validate it)

Once that is done & merged, we can add a server.json which uses the MCPB as mentioned in these requirements.

But this approach has an issue that our server is a Go binary so needs the platform specified but that isn't supported by MCPB yet (see this and this). Using Node.js approach sounds like a bad idea, the alternative is to wait for MCPB to support platform-specific builds. Using our own Docker image published to the Docker hub is another option.

@ioanarm ioanarm force-pushed the add-mcpb-manifest.json branch from 97ad92e to ce7a739 Compare October 10, 2025 14:26

This comment has been minimized.

This comment has been minimized.

@ioanarm
Copy link
Contributor

ioanarm commented Oct 10, 2025

@sd2k and @okianus we now have our own docker image with the label required to publish to the mcp registry.
https://hub.docker.com/repository/docker/grafana/mcp-grafana

This should be good to go! Have a look and let me know!

@sd2k
Copy link
Collaborator Author

sd2k commented Oct 10, 2025

Hm I think we can use the custom Docker image for the server.json but not for the MCPB manifest? Let's chat on Monday

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants