Discussed in #118

It seems reasonable to encourage a convention of putting server.json in the root of an MCP package artifact. There are a number of plausible benefits like defining how an MCP server package can be run, without requiring remote context.

There may be edge cases to account for here (for example, a package that is capable of running multiple "different" MCP servers -- do we need to extend into a servers.json concept?), but I think it would be OK to start with loosely documenting this convention for the simple case (1 package - 1 MCP server) and see what needs emerge.