[
https://issues.apache.org/jira/browse/SOLR-17944?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18024818#comment-18024818
]
David Smiley commented on SOLR-17944:
-------------------------------------
bq. The other day I used this tool to ...
Eric -- that would make a fantastic blog post or video. This is a new world
and I'm blown away sometimes by these little stories, yet feeling
unprepared/unaware on how to walk the same path to have the same/similar
experience.
I'm not surprised at all that most MCPs are separate but it could be quite
forward thinking and a bonus to have it in the same deployment of Solr itself.
It helps users use Solr without them futzing with yet another endpoint that
must be integrated. It could take advantage of any Servlet container (Jetty)
level security layer like mTLS; surely other things. That said... really, both
are fine. Certainly the separate service has an advantage of talking to a Solr
endpoint that doesn't have such a hypothetical MCP Servlet. If it were crafted
as a Servlet, then it'd be easy to _either_ run in Solr or run in whatever Java
web container.
> 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]
