modelcontextprotocol
Remote-only MCP server cannot be published using mcp-publisher
@rdimitrov Hi!
Describe the bug When attempting to publish a remote-only MCP server (one that only includes a README and server.json file, no full package), mcp-publisher fails. It seems to expect a full package layout, even though our server is a remote endpoint.
To Reproduce Steps to reproduce the behavior:
Create a repository with only a README and a valid server.json referencing a remote MCP endpoint.
Run npx mcp-publisher publish.
Observe the validation failure or rejection.
Expected behavior mcp-publisher should allow publishing of remote-only servers that have a valid server.json and README, without requiring a dummy package.
Logs - message from the developer
Right now I am in the following situation. If I am using schemas/2025-07-09 I get to the end of the process and get rejected them with "deprecated schema detected: https://static.modelcontextprotocol.io/schemas/2025-07-09/server.schema.json." If I am moving to later schemas I get unsupported registry type: github_release 3:30 None of the alternatives registry types fits us.
There seems to be an issue here to discuss with them 3:45 None of the options will work with the new schema (2025-10-17) and the old is deprecated. I will try moving schemas one by one and try to see if something will work but someone to talk with can ease things
Additional context
We already verified the schema is up to date (post–17 Oct version).
Our repo: https://github.com/jfrog/jfrog-mcp-server
The current registry entry mirrors this README: https://github.com/mcp
Hey, @oranmis, thanks for reaching out! 👋
From what I can tell I think it's correct:
- 2025-07-09 is rightfully rejected
- Using 2025-10-17 you get a failure with registry type: github_release which is again rightfully rejected since there's no such registry type supported. It's suggested to use some of the supported registry types, i.e. npm, pypi, nuget, mcpb and oci.
@rdimitrov Thanks for the answer. So waht should we do if we have Remote-only MCP server? Today we have this: https://github.com/jfrog/jfrog-mcp-server?tab=readme-ov-file registered here: https://github.com/mcp?utm_source=blog-source&utm_campaign=mcp-registry-server-launch-2025
And we need to have it in the new registry before deprecation.
How come in the former registry we were able to publish a remote-only MCP server?
What can we do to have it there?
Thank you so much for your answer!:)
Hey, @oranmis! 👋 I am currently updating some of the docs. I put together a remote servers doc. Perhaps it might help? Feedback is welcome!
I also put together a consolidated authentication doc, if it can be of help.
