modelcontextprotocol / modelcontextprotocol/servers
Community registry submission guidance for embercore
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 90.5k
- Forks
- 11.7k
- Avg merge
- 2d 2h
- Merged PRs (30d)
- 5
Description
Hi! I'd like to submit embercore for official MCP ecosystem discovery.
Repo: https://github.com/embercore-labs/embercore
Description:
embercore — Open-source, plan-first AI marketing planner. MCP-native, BYOK, MIT licensed. Single Go binary engine with 5 named agents (Athena/Apollo/Hestia/Hermes/Hephaestus) and human checkpoints between every stage.
From the README here, it looks like modelcontextprotocol/servers is reserved for steering-group reference implementations and community servers should instead be published to the MCP Registry.
Could you confirm the preferred path for publishing a community-built server like embercore to the official registry, and whether any additional review step is needed beyond registry publication?
Thanks!
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the README and the MCP Registry guidance referenced in the issue. Confirm the preferred publication path for community-built servers and whether registry publication requires additional review, then document the confirmed guidance if a repository change is requested.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- documentation
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100