MySQL Support

[SinOverCos]

I'm creating this feature request in the context of bringing up MCP adoption inside the walls of my company.

At larger companies, adding support for new types of database can be slow (e.g. if there is no existing use of MongoDB at $LargeTechCo, then starting to use MongoDB may need involvement from cloud ops, security, data infra, etc teams).

Wondering if more choices of backing stores are on the roadmap? I think MySQL would be a pretty safe bet that every company likely supports.

[connor4312]

See: #11

Reusability of infrastructure, implementation detail decisions: While we expect the ecosystem to reuse the shapes (such as OpenAPI shape, mcp.json shape) associated with this work, we are not designing for reuse of the underlying implementation details and infrastructure. As such, we will not provide instructions on "how to serve your own instance of this metaregistry".

The registry include a spec, and you are free to implement your own registry in the language (and database) of your choosing, but the goal of this repo isn't to provide an end-all implementation that is deployable in every architecture.