Way off topic to discuss the existence of the project itself in this context, I have clients looking very much forward to adding Solr MCP to their tool belt.
What we are discussing is how to improve the *release process* to make sure we vote on the actual artifacts and not something else, and perhpas identify the need for a "smoke tester" script , like we have for both Solr and Solr Operator. That would lower the bar for both committers and others to participate in VOTEs. Please don't take this as critisism from my side, we're in this together and I lift issues with the goal of process improvement in mind. I have another question. The release artifacts are only jar files solr-mcp-1.0.0-javadoc.jar solr-mcp-1.0.0-javadoc.jar.asc solr-mcp-1.0.0-javadoc.jar.sha512 solr-mcp-1.0.0-plain.jar solr-mcp-1.0.0-plain.jar.asc solr-mcp-1.0.0-plain.jar.sha512 solr-mcp-1.0.0-sources.jar solr-mcp-1.0.0-sources.jar.asc solr-mcp-1.0.0-sources.jar.sha512 solr-mcp-1.0.0.jar solr-mcp-1.0.0.jar.asc solr-mcp-1.0.0.jar.sha512 Would not any ASF release need to release the entire source tree as a src.tgz so that anyone can download it in 10 years and build the binaries from source? I can see that the execuable jar is more self contained and all you need to run the mcp... Jan > 3. juni 2026 kl. 06:33 skrev Mark Miller <[email protected]>: > > Personally, I just see it as one more release vote we don't need. How many > Solr MCPs exist already? A dozen? > > Meh. I wouldn't use any of them anyway. It makes a much better Skill. MCPs > take up a crap load of context whether the current prompt uses it or not, > if you launch any agents, that silly token cost multiplies and context rot > extends out like a virus. As a simple skill, all of that is resolved, and > because command line usage is well burrowed into the training data, LLM’s > are much better at using Solr that way than via an MCP - and heck, that > also means you hardly even need much of a skill definition given how well > they know the Solr apis. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
