[
https://issues.apache.org/jira/browse/SOLR-17944?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18030144#comment-18030144
]
David Smiley commented on SOLR-17944:
-------------------------------------
>From the presentation today, it seems that MCP "tools" ought to be highly
>malleable to support custom/evolving use-cases. Like, the endpoints should be
>defined in a non-compiled scripting language.
bq. Integrate as request handler in a new Solr module solr/modules/mcp
I don't recommend that. It would needlessly intertwine the MCP code with being
inside Solr... but the code doesn't care; it just needs to talk to Solr. And
it'd in-effect needlessly invade Solr's classpath; maybe contributing to
version conflicts. A WAR deployed in the same Jetty would isolate the
functionality and allow either co-deployment with Solr (same service), or the
option of deploying elsewhere / standalone (esp. via a Docker image), without
tying the MCP code to either. I think what we could do as a project is ensure
that people can do this easily (say drop-in). Our continued use of Jetty XML
(vs Java hard-coding Jetty) is an enabler for this.
> 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]
