The Third-Party Servers section (Official Integrations + Community
Servers) has been superseded by the MCP Registry at
https://registry.modelcontextprotocol.io/. The README already carried a
deprecation note and CONTRIBUTING.md froze new additions. This removes
the list, updates CONTRIBUTING.md to describe the new state, and
refreshes the readme-pr-check workflow's bot comment.
* add useless toolkit mcp servers
* change postion
move from community group to official group
* Move Toolkit from official group to community group
Move Toolkit from official group to community group
* Add AI Endurance MCP server to README: AI-powered training platform for endurance athletes with 20 tools including workout management, activity analysis, performance predictions, and recovery tracking. Supports cycling, running, and triathlon.
* Move AI Endurance to community servers
* Add Google Analytics 4 to Community Servers
* Move Google Analytics 4 to Community Servers section
* Remove extra blank line
---------
Co-authored-by: leonardosepulvedat <lsepulvedatabares@gmail.com>
* Adding Semilattice MCP to README.md
* Remove "- audience prediction" from Semilattice MCP name
Co-authored-by: adam jones <domdomegg+git@gmail.com>
---------
Co-authored-by: adam jones <domdomegg+git@gmail.com>
- Agent Interviews: AI-powered qualitative research platform
- MCP Bundles Hub: Discovery and management platform with 500+ MCP provider integrations
Moved to Community Servers section per reviewer feedback.
- Added Arr Suite MCP server for Plex and *arr media automation suite
- Added Restream MCP server for multi-platform live streaming management
- Both servers added in alphabetical order to Community Servers section
* Add Context Processor to Third-Party Servers
- Intelligent context management MCP server
- Configurable pre-processing strategies (clarify, analyze, search, fetch)
- Published on npm at context-processor v1.0.0
- 81 passing tests with comprehensive documentation
- GitHub: https://github.com/mschultheiss83/context-processor
* Move Context Processor to Community Servers section
The reviewer requested moving Context Processor from Official Integrations
to Community Servers section, as it is a community-developed server rather
than an official company integration.
As mentioned in https://github.com/makenotion/notion-mcp-server/issues/142 by @jamiecool, the official open-sourced Notion MCP server does not work well. It returns the raw JSON response from the Notion API, which is way to verbose. This fork of the Notion Server converts read responses to usable Markdown content which is more token efficient.
