Propose hosting ember-mcp

[NullVoxPopuli]

Propose hosting ember-mcp

Rendered

Summary

This pull request is proposing a new RFC.

To succeed, it will need to pass into the Exploring Stage, followed by the Accepted Stage.

A Proposed or Exploring RFC may also move to the Closed Stage if it is withdrawn by the author or if it is rejected by the Ember team. This requires an "FCP to Close" period.

An FCP is required before merging this PR to advance to Accepted.

Upon merging this PR, automation will open a draft PR for this RFC to move to the Ready for Released Stage.

Exploring Stage Description

This stage is entered when the Ember team believes the concept described in the RFC should be pursued, but the RFC may still need some more work, discussion, answers to open questions, and/or a champion before it can move to the next stage.

An RFC is moved into Exploring with consensus of the relevant teams. The relevant team expects to spend time helping to refine the proposal. The RFC remains a PR and will have an Exploring label applied.

An Exploring RFC that is successfully completed can move to Accepted with an FCP is required as in the existing process. It may also be moved to Closed with an FCP.

Accepted Stage Description

To move into the "accepted stage" the RFC must have complete prose and have successfully passed through an "FCP to Accept" period in which the community has weighed in and consensus has been achieved on the direction. The relevant teams believe that the proposal is well-specified and ready for implementation. The RFC has a champion within one of the relevant teams.

If there are unanswered questions, we have outlined them and expect that they will be answered before Ready for Release.

When the RFC is accepted, the PR will be merged, and automation will open a new PR to move the RFC to the Ready for Release stage. That PR should be used to track implementation progress and gain consensus to move to the next stage.

Checklist to move to Exploring

• The team believes the concepts described in the RFC should be pursued.
• The label S-Proposed is removed from the PR and the label S-Exploring is added.
• The Ember team is willing to work on the proposal to get it to Accepted

Checklist to move to Accepted

• This PR has had the Final Comment Period label has been added to start the FCP
• The RFC is announced in #news-and-announcements in the Ember Discord.
• The RFC has complete prose, is well-specified and ready for implementation.
  • All sections of the RFC are filled out.
  • Any unanswered questions are outlined and expected to be answered before Ready for Release.
  • "How we teach this?" is sufficiently filled out.
• The RFC has a champion within one of the relevant teams.
• The RFC has consensus after the FCP period.

[apellerano-pw]

Hosting it would definitely improve adoption in my org. We discourage running npx without --no-install because it's susceptible to npm supply chain attacks and typosquatting. So to use the ember-mcp we have to download a specific version locally and set it up by hand.

It would be nicer if it was hosted on an official domain and submitted to the MCP registries, so we could trust it and install it from our various AI tools' marketplaces.

Not sure if this RFC covers both the hosting and the tools published by the MCP. On the tool front, I don't know if Ember MCP should have generic npm ecosystem tools like get_npm_package_info, compare_npm_versions, and detect_package_manager. These seem like they could be part of some separate NPM MCP that someone else spends their time maintaining.

[gossi]

I'm fine calling it initial datasource. They are subject to change anyway. I know there are a couple of community writings (done/happening) and a future consolidation of these resources under the official ember banner will then naturally turn into the datasource.

[gossi]

Happy with that one. Even more about an officially hosted one ;)

[NullVoxPopuli]

on: https://www.netlify.com/blog/web-frameworks-2025-year-in-review/

Every major framework shipped its own MCP server in 2025:
Angular
Astro
Next.js
Nuxt
Svelte
TanStack Start (alpha, just before publication)

We have one, and anyone using AI with ember, I would tell them to use the ember-mcp -- hopefully we can recommend it formally soon 🤞

[cloke]

Huge thumbs up. Ember with skills and mcp is creating such a stable dev solution for us. Would be great to have it official.

[bartocc]

Very happy to see this happening! It will definitely help Ember.js adoption and DX!