This sounds awesome, please let me know if you have any optimizations in mind, 
more than happy to take up that work stream :)

Question: What kind scenarios you have in mind for caching of some MCP Calls?
On Oct 6, 2026 at 1:15 PM -0500, Aditya Parikh <[email protected]>, 
wrote:
> Thank you all for the +1s.
>
> Arup,
> Thanks for the question! We added a slide covering this question for our
> CoC presentation. We hope to release Solr-MCP 1.0 with the latest current
> versions of Spring AI, Spring Boot:
>
> Spring Boot version Spring AI version MCP Java SDK version MCP protocol
> version
> 3.5.14 <https://github.com/spring-projects/spring-boot/releases/tag/v3.5.14>
> (current main) 1.1.7
> <https://github.com/spring-projects/spring-ai/releases/tag/v1.1.7> 0.18.2
> <https://github.com/modelcontextprotocol/java-sdk/releases/tag/v0.18.2>
> 2025-11-25 <https://modelcontextprotocol.io/specification/2025-11-25>
> 4.1.1 <https://github.com/spring-projects/spring-boot/releases/tag/v4.1.1>
> (after #23 <https://github.com/apache/solr-mcp/pull/23>) 2.0.1
> <https://github.com/spring-projects/spring-ai/releases/tag/v2.0.1> 2.0.0
> <https://github.com/modelcontextprotocol/java-sdk/releases/tag/v2.0.0>
> (Spring AI default), 2.0.1
> <https://github.com/modelcontextprotocol/java-sdk/releases/tag/v2.0.1>
> (pinned by #23) 2025-11-25
> <https://modelcontextprotocol.io/specification/2025-11-25>
> 4.2 (currently 4.2.0-M2
> <https://github.com/spring-projects/spring-boot/releases/tag/v4.2.0-M2>) 2.1
> (currently 2.1.0-M1
> <https://github.com/spring-projects/spring-ai/releases/tag/v2.1.0-M1>) TBD (
> java-sdk#1089 <https://github.com/modelcontextprotocol/java-sdk/pull/1089>)
> 2026-07-28 <https://modelcontextprotocol.io/specification/2026-07-28> (in
> progress)
> As of now, an MCP Java SDK built on the MCP protocol spec version
> 2026-07-28 does not exist yet. We will always be updating our dependencies
> as they become available.
>
> My main takeaway from this update is that the protocol went stateless which
> would make it easier to scale. We already built the MCP server with
> stateless mode so we should be good with just updating versions. We don't
> rely on any of the features that *changed* -
> *Elicitation* - server asks the user (via the client) for input
> mid-tool-call, e.g. a confirmation. It changed from a server-initiated
> request on an open stream to Multi Round-Trip Requests: the server returns `
> input_required` and the client retries the call with the answers.
> Or *deprecated* -
> - *Logging*: the server streams log messages to the client over MCP. We use
> logback + OpenTelemetry, which is the spec's recommended migration.
> - *Sampling*: the server asks the client's LLM to generate a completion on
> its behalf.
> - *Roots*: the client tells the server which filesystem/URI locations it
> may work in. Our Solr target comes from `SOLR_URL` config instead.
>
> We can look into optimizations when we might get to implementing finer
> grained security having different roles for authorizing tool calls and
> caching as we understand them better.
>
> Thanks,
> Aditya
>
> On Tue, Oct 6, 2026 at 11:21 AM Eric Pugh <[email protected]> wrote:
>
> >
> >
> > On 2026/10/05 21:52:43 Marc Byrd wrote:
> > > > +1
> > > >
> > > > Thanks!
> > > >
> > > > m
> > > >
> > > >
> > > > On Mon, Oct 5, 2026 at 3:36 PM <[email protected]> wrote:
> > > >
> > > > > > Hello!
> > > > > >
> > > > > > +1 (non-binding)
> > > > > >
> > > > > > Something I wanted to add:
> > > > > >
> > > > > > I see that the README already lists STDIO as a transport mode.
> > > > > >
> > > > > > Aditya, I was curious whether there is anything from the newer MCP
> > > > > > specification that we could implement or optimize in Solr MCP.
> > > > > >
> > > > > > Link:
> > > > > > https://blog.modelcontextprotocol.io/posts/2026-07-28/
> > > > > >
> > > > > >
> > > > > > Would love to hear everyone’s views on this.
> > > > > >
> > > > > > Thanks, Arup
> > > > > > On Oct 5, 2026 at 2:08 PM -0500, Andrzej Bialecki <[email protected]>,
> > wrote:
> > > > > > > > +1 (binding)
> > > > > > > >
> > > > > > > > Cheers,
> > > > > > > > Andrzej
> > > > > > > >
> > > > > > > > On 2026-10-05 18:50 UTC Eric Pugh wrote:
> > > > > > > > > > Hello all,
> > > > > > > > > >
> > > > > > > > > > As many of you may be familiar with, there has been a 
> > > > > > > > > > desire to
> > enable
> > > > > > Solr inside agentic environments natively through the MCP protocol
> > with a
> > > > > > community blessed solution (
> > > > > > https://github.com/adityamparikh/solr-mcp-server/issues/12). Such a
> > tool
> > > > > > will ensure that Solr becomes more accessible to non developers like
> > data
> > > > > > scientists or ops folks who primarily interact via Agents with Solr.
> > > > > > > > > >
> > > > > > > > > > We have already created the public ASF repo for "Solr MCP", 
> > > > > > > > > > almost
> > a
> > > > > > year ago, however we never held the formal vote thread for this
> > process.
> > > > > > > > > >
> > > > > > > > > > This thread is a vote on creating a public ASF repo for 
> > > > > > > > > > "Solr
> > MCP", a
> > > > > > contribution from https://github.com/adityamparikh/solr-mcp-server
> > that
> > > > > > Eric Pugh has been working closing with the original developer, 
> > > > > > Aditya
> > > > > > Parikh on making ASF compliant and work well with Solr, with
> > supervision
> > > > > > from Jan Høydahl. For context, Solr MCP has been demoed in community
> > > > > > meetings, and will be featured at Community over Code 2026 in the
> > Search
> > > > > > Track. I encourage you to test out a nightly build via this
> > "playground"
> > > > > > https://adityamparikh.github.io/solr-mcp/.
> > > > > > > > > >
> > > > > > > > > > A passing vote means:
> > > > > > > > > > * Confirming two github repo github.com/apache/solr-mcp 
> > > > > > > > > > under
> > current
> > > > > > Solr ownership
> > > > > > > > > > * Confirming the current state of the Solr MCP code (clean
> > history).
> > > > > > This has been documented in
> > > > > > https://github.com/apache/solr-mcp/blob/main/solr-mcp-ip-clearance.xml
> > > > > > > > > > * PMC to conduct legal check and IP clearance as needed. 
> > > > > > > > > > This has
> > > > > > already been started, see
> > https://issues.apache.org/jira/browse/LEGAL-716.
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > > Please vote on initiating a new solr-mcp sub-project under 
> > > > > > > > > > the
> > Apache
> > > > > > Solr project:
> > > > > > > > > >
> > > > > > > > > > [] +1 Accept the proposal --- I support creating these 
> > > > > > > > > > repositories
> > > > > > > > > > [] 0 No strong opinion
> > > > > > > > > > [] -1 Object --- Provide a reason
> > > > > > > > > >
> > > > > > > > > > This is a procedural vote with simple majority. Votes from 
> > > > > > > > > > PMC
> > members
> > > > > > are binding;
> > > > > > > > > > votes from community members are welcome.
> > > > > > > > > >
> > > > > > > > > > The vote will remain open for at least 3 business days, 
> > > > > > > > > > closing no
> > > > > > earlier than:
> > > > > > > > > > 2026-10-08 22:00 UTC
> > > > > > > > > >
> > > > > > > > > > The vote result will guide further action
> > > > > > > > > >
> > > > > > > > > > - Eric
> > > > > > > > > >
> > > > > > > > > > References:
> > > > > > > > > > *
> > > > > > https://lists.apache.org/thread.html/2gvf4cz0tm22bsv8hg1ywcwvpk8zsv2n
> > > > > > > > > > * https://github.com/adityamparikh/solr-mcp-server/issues/12
> > > > > > > > > > * https://issues.apache.org/jira/browse/LEGAL-716
> > > > > > > > > > *
> > > > > > https://github.com/apache/solr-mcp/blob/main/solr-mcp-ip-clearance.xml
> > > > > > > > > >
> > > > > > > > > >
> > ---------------------------------------------------------------------
> > > > > > > > > > To unsubscribe, e-mail: [email protected]
> > > > > > > > > > For additional commands, e-mail: [email protected]
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > >
> > > > > > > > ---------------------------------------------------------------------
> > > > > > > > To unsubscribe, e-mail: [email protected]
> > > > > > > > For additional commands, e-mail: [email protected]
> > > > > > > >
> > > > > >
> > > >
> >
> > Here is my +1 (binding).
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: [email protected]
> > For additional commands, e-mail: [email protected]
> >
> >
>
> --
> Thanks,
> Aditya

Reply via email to