git repository as a registry #51
Replies: 2 comments 1 reply
-
This was not an explicit consideration we made, and the extent of the datastore discussion to-date can be found here. I think it's an interesting idea, and no obvious major objections come to mind. I do worry a bit that the tooling around using a git as a datastore may be a little nonstandard, and so just be more of an eng lift than just using Postgres. So then it becomes a question of whether the benefits you listed (easy replication, auditing) are worth the extra lift. Auditing sticks out as a nice benefit, but then again we're thinking of server.json versions as immutable, so that's already something of a built-in audit log. Not comprehensive of course, but most-of-the-way-there for the most critical information. I don't feel strongly on this either way I think. @sridharavinash is this something you thought about? |
Beta Was this translation helpful? Give feedback.
-
@joelverhagen |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Pre-submission Checklist
Your Idea
Seeing as the registry is metadata only and (from the looks of it) meant to be consumed by partner tools not by end users I wonder if your team has considered using a Git repository (perhaps under the modelcontextprotocol organization) to be the data store. This would provide replication and auditing properties and perhaps even early publishing workflow.
Winget and perhaps other use or have used git to be the package metadata storage and I wonder if this option was considered.
Love the project!
Scope
Beta Was this translation helpful? Give feedback.
All reactions