Created MCP Server Generator!

[Starborn]

Hi MCP Maintaners

I recently forked some files from the MCP Project and created the MCP Server Generator based on the specs to create an MCP server for . I'm excited about the project and wanted to explore how I might contribute it back to the MCP ecosystem. But it may not be a straight PR, because the code I am pushing back to the repo is not the same as the one I pulled from the repo for reference only

I'm a bit new to this, and I've already made one potentially confusing change: I renamed the generated directory from its default. I understand this might make a direct pull request challenging or unclear, and I apologize if that causes any confusion.
My app is not an MCP server, but a MCP server generator. It works,

My intention isn't to merge my specific server directly into the main repository, but rather to understand the process for adding a new, independent MCP server to the broader MCP project (perhaps in an 'examples' or 'community servers' section, if such a thing exists or is planned). I've seen other example servers, and I'd love to learn how to properly submit mine so it can be discovered and used by others, without cluttering the core repo.

Could you please guide me on the best practices or the correct process for contributing a new MCP server project, especially considering I've already made some local directory changes?

Here's a link to my repository if that helps: [Starborn:MCPservergen]

Thank you for your time and guidance!

Best regards,
[Your GitHub Username]

Description

Publishing Your Server

Note: We are no longer accepting PRs to add servers to the README. Instead, please publish your server to the MCP Server Registry to make it discoverable to the MCP ecosystem.

To publish your server, follow the quickstart guide. You can browse published servers at https://registry.modelcontextprotocol.io/.

Server Details

• Server:
• Changes to:

Motivation and Context

How Has This Been Tested?

Breaking Changes

Types of changes

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to change)
• Documentation update

Checklist

• I have read the MCP Protocol Documentation
• My changes follows MCP security best practices
• I have updated the server's README accordingly
• I have tested this with an LLM client
• My code follows the repository's style guidelines
• New and existing tests pass locally
• I have added appropriate error handling
• I have documented all environment variables and configuration options

Additional context

[cliffhall]

Hi @Starborn! Thanks for this, but we're not accepting unsolicited PRs for new reference servers at this time. Reference servers are created by the maintainers for the purpose of demonstrating and testing MCP specification features. Ongoing maintenance of the reference servers is an burden that we have to consider. Keeping them up to date with the SDK they are implemented in, responding to security issues, etc.

[Starborn]

Hi @liffhall! I think there's been a misunderstanding - this isn't a reference server implementation. It's a **code generation tool** (like create-react-app for MCP) that outputs complete TypeScript or Python servers based on user configuration. No ongoing maintenance of server implementations needed since it's the generator itself, not generated servers. **Question:** Does MCP have a `/tools/` or `/generators/` section? If not, would you be open to adding one for community tooling? This could live at: ``` tools/generators/mcp-server-generator/ ``` If tooling contributions aren't in scope for this repo, I'm happy to maintain it independently and link from discussions/community resources. Thanks for your time!

…

On Wed, Jan 14, 2026 at 5:49 AM Cliff Hall ***@***.***> wrote: *cliffhall* left a comment (modelcontextprotocol/servers#3194) <#3194 (comment)> Hi @Starborn <https://github.com/Starborn>! Thanks for this, but we're not accepting unsolicited PRs for new reference servers at this time. Reference servers are created by the maintainers for the purpose of demonstrating and testing MCP specification features. Ongoing maintenance of the reference servers is an burden that we have to consider. Keeping them up to date with the SDK they are implemented in, responding to security issues, etc. — Reply to this email directly, view it on GitHub <#3194 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ACFKUCKQ5A2KWIDOBR5WQQ34GVR5TAVCNFSM6AAAAACRHMJSPKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTONBWG4ZDAOBXG4> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[Starborn]

Cliff, it occurs to me that I may not have been clear in my PR at all My bad entirely, apologies for the confusion! Here is the thing https://github.com/Starborn/MCP-Server-Generator please let me know if there is a place in MCP project to share this with and get feedback/evaluation cheers Paola Starborn On Wed, Jan 14, 2026 at 6:32 AM Paola Di Maio ***@***.***> wrote:

…

Hi @liffhall! I think there's been a misunderstanding - this isn't a reference server implementation. It's a **code generation tool** (like create-react-app for MCP) that outputs complete TypeScript or Python servers based on user configuration. No ongoing maintenance of server implementations needed since it's the generator itself, not generated servers. **Question:** Does MCP have a `/tools/` or `/generators/` section? If not, would you be open to adding one for community tooling? This could live at: ``` tools/generators/mcp-server-generator/ ``` If tooling contributions aren't in scope for this repo, I'm happy to maintain it independently and link from discussions/community resources. Thanks for your time! On Wed, Jan 14, 2026 at 5:49 AM Cliff Hall ***@***.***> wrote: > *cliffhall* left a comment (modelcontextprotocol/servers#3194) > <#3194 (comment)> > > Hi @Starborn <https://github.com/Starborn>! Thanks for this, but we're > not accepting unsolicited PRs for new reference servers at this time. > Reference servers are created by the maintainers for the purpose of > demonstrating and testing MCP specification features. Ongoing maintenance > of the reference servers is an burden that we have to consider. Keeping > them up to date with the SDK they are implemented in, responding to > security issues, etc. > > — > Reply to this email directly, view it on GitHub > <#3194 (comment)>, > or unsubscribe > <https://github.com/notifications/unsubscribe-auth/ACFKUCKQ5A2KWIDOBR5WQQ34GVR5TAVCNFSM6AAAAACRHMJSPKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTONBWG4ZDAOBXG4> > . > You are receiving this because you were mentioned.Message ID: > ***@***.***> >

[cliffhall]

Our focus is to provide SDKs for building servers and clients, reference servers for demonstrating spec features, and Inspectors (UI/CLI) that allow devs to test the servers they have built. That keeps us quite busy.

While it is interesting, a server generator is not really a tool we would currently want to shoulder the ongoing maintenance burden of. As time goes on, this would need continual updates to match the Python SDK's feature set, and some way of testing the output in CI to ensure that the servers it creates conform to spec and operate properly.

@olaservo @evalstate please weigh in if you have a different view on this, as I don't want to unilaterally make a decision that doesn't represent the other maintainers of this repo.

[Starborn]

Thank you Cliff *some way of testing the output in CI to ensure that the servers it creates conform to spec and operate properly. and maintained up to date?* This is so important for me as well, Please point to the mechanism for server evaluation, how does the project ensure the servers it includes in the repo conform to spec?

…

On Fri, Jan 16, 2026 at 5:50 AM Cliff Hall ***@***.***> wrote: *cliffhall* left a comment (modelcontextprotocol/servers#3194) <#3194 (comment)> Our focus is to provide SDKs for building servers and clients, reference servers for demonstrating spec features, and Inspectors (UI/CLI) that allow devs to test the servers they have built. That keeps us quite busy. While it is interesting, a server generator is not really a tool we would currently want to shoulder the ongoing maintenance burden of. As time goes on, this would need continual updates to match the Python SDK's feature set, and some way of testing the output in CI to ensure that the servers it creates conform to spec and operate properly. @olaservo <https://github.com/olaservo> @evalstate <https://github.com/evalstate> please weigh in if you have a different view on this, as I don't want to unilaterally make a decision that doesn't represent the other maintainers of this repo. — Reply to this email directly, view it on GitHub <#3194 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ACFKUCIYMB6GMGIZFVW23CL4HADRNAVCNFSM6AAAAACRHMJSPKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTONJXGA2DGMBUHA> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[Starborn]

Okay, Cliff and everyone To speed up the discussion of how the project validates MCP servers I have created 1, MCP requirements specification V1 (open for feedback) https://github.com/Starborn/MCP-Server-Validator/blob/main/MCP_Server_Validator_Requirements_v1.0.docx.pdf and 2. MCP server validator V1,1 (implements the specification only for parts of the specification so far but it works! the rest planned for soon) https://github.com/Starborn/MCP-Server-Validator It would be awesome to know if this means anything to the project Best pdm On Fri, Jan 16, 2026 at 2:24 PM Paola Di Maio ***@***.***> wrote:

…

Thank you Cliff *some way of testing the output in CI to ensure that the servers it creates conform to spec and operate properly. and maintained up to date?* This is so important for me as well, Please point to the mechanism for server evaluation, how does the project ensure the servers it includes in the repo conform to spec? On Fri, Jan 16, 2026 at 5:50 AM Cliff Hall ***@***.***> wrote: > *cliffhall* left a comment (modelcontextprotocol/servers#3194) > <#3194 (comment)> > > Our focus is to provide SDKs for building servers and clients, reference > servers for demonstrating spec features, and Inspectors (UI/CLI) that allow > devs to test the servers they have built. That keeps us quite busy. > > While it is interesting, a server generator is not really a tool we would > currently want to shoulder the ongoing maintenance burden of. As time goes > on, this would need continual updates to match the Python SDK's feature > set, and some way of testing the output in CI to ensure that the servers it > creates conform to spec and operate properly. > > @olaservo <https://github.com/olaservo> @evalstate > <https://github.com/evalstate> please weigh in if you have a different > view on this, as I don't want to unilaterally make a decision that doesn't > represent the other maintainers of this repo. > > — > Reply to this email directly, view it on GitHub > <#3194 (comment)>, > or unsubscribe > <https://github.com/notifications/unsubscribe-auth/ACFKUCIYMB6GMGIZFVW23CL4HADRNAVCNFSM6AAAAACRHMJSPKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTONJXGA2DGMBUHA> > . > You are receiving this because you were mentioned.Message ID: > ***@***.***> >

[cliffhall]

Please point to the mechanism for server evaluation, how does the project ensure the servers it includes in the repo conform to spec?

There is a WIP conformance testing project, but I don't know if it is ready for prime time.