Frontmatter
| title | Add agent-agnostic MCP server configuration |
| author | MannXo |
| state | Merged |
| createdAt | Oct 8, 2025, 10:13 AM |
| updatedAt | Oct 8, 2025, 1:40 PM |
| closedAt | Oct 8, 2025, 1:40 PM |
| mergedAt | Oct 8, 2025, 1:40 PM |
| branches | dev ← feature/agent-agnostic-mcp-config |
| url | https://github.com/neomjs/neo/pull/7416 |

Very nice. How was your experience with the new AI workflow? It is still early stage, and you helped with making it better.
Feedback from Gemini:
✦ Hi @MannXo, and welcome to the Neo.mjs project! It's great to have you contributing, especially for Hacktoberfest.
As the project's AI assistant, Gemini, I've had the opportunity to review your pull request, and I'm genuinely impressed with the quality and thoughtfulness of your work. This is an excellent first contribution.
The new .github/mcp-servers.json file is not just well-structured, but it also demonstrates a clear understanding of the goals of the MCP epic. The schema is logical and extensible, which is exactly what we need for a robust AI tooling architecture.
Furthermore, the AgentAgnosticMcpConfig.md guide is exceptionally well-written. It's clear, comprehensive, and the inclusion of example implementations for each phase of the discovery and connection process is a fantastic touch. This guide will be an invaluable resource for both human developers and other AI agents who will interact with our MCP servers in the future.
This contribution is a significant step forward in our efforts to create a more powerful, flexible, and agent-agnostic AI tooling ecosystem. Thank you for your high-quality work and for helping us to build the future of the Neo.mjs framework.
We look forward to seeing more of your contributions!
Best regards, Gemini
Please make sure to read the Contributing Guidelines:
https://github.com/neomjs/neo/blob/dev/CONTRIBUTING.md
What kind of change does this PR introduce? (check at least one)
Does this PR introduce a breaking change? (check one)
If yes, please describe the impact and migration path for existing applications:
The PR fulfills these requirements:
devbranch, not themainbranchfix #xxx[,#xxx], where "xxx" is the issue number)If adding a new feature, the PR's description includes:
Other information: