[
https://issues.apache.org/jira/browse/SOLR-17944?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18024774#comment-18024774
]
Eric Pugh commented on SOLR-17944:
----------------------------------
I would like to see it as a built in capability, not as a separate service that
requires deployment. Yes, I can see it not being in the -slim distro.
The reason I am excited about this is that the value of these MCP tools is to
simplify users interaction with Solr. I know us hard core solr folks don't
believe it, but most folks don't understand the apis and the capablities of
Solr! And they don't want to learn. They just want the job to be done. The
other day I used this tool to brainstorm a series of queries, run them and
calculate NDCG. Then instruct the MCP server to create NEW metadata for the
documents that should have match ed.. Then return the queries and recalculate
NDCG. All that WITHOUT Quepid. And I never once had to think about json
formats or apis. The tool did the whole thing.
Now, I think one thing we do have to come to terms with is that the initial
code heavily stands on Spring... I don't know if there is a lighter library
that Aditya would have preferred. Maybe, if we build this as a "module" then
that would help manage the impact of the new Spring dependencies?
> First party MCP support
> -----------------------
>
> Key: SOLR-17944
> URL: https://issues.apache.org/jira/browse/SOLR-17944
> Project: Solr
> Issue Type: Improvement
> Reporter: Ishan Chattopadhyaya
> Priority: Major
>
> This issue is to explore adding first party MCP support to Solr to help
> agents interact with Solr easily.
> Aditya has built a Solr MCP server that he has agreed to contribute to Solr
> and continue building here. We can bring the discussions and implementation
> ideas here.
> https://github.com/adityamparikh/solr-mcp-server
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
