Your agent’s Spring knowledge is two versions old.

Sprig is an MCP server that answers from the Spring release you actually run. Reference documentation and framework source, searched by version, returned as primary sources.

https://mcp.sprig.dev/mcp

Free for documentation search. No key, no sign-up.

Without sprig

@Bean
HttpServiceProxyFactory factory(
  RestClient.Builder builder) {
  return HttpServiceProxyFactory
    .builderFor(/* … */)
    .build();
}

Hand-wired from 2023 training data. Dead code on Boot 4, which registers this for you.

With sprig

search_spring_docs(
  "HTTP service client",
  bootVersion: "4.0.2")

→ "HTTP service clients are
   auto-configured. Declare the
   interface and inject it."

One call, a few hundred tokens, the answer for the version in your pom.

An agent with stale training data hand-wires what Spring Boot already auto-configures. Sprig lets it check the pinned docs first.

Pinned to your version
Pass your Spring Boot version with the call. Sprig resolves it through the Boot BOM to the exact release of every Spring project it covers, and every answer names the version it came from.
Primary sources
Real sections of the reference documentation and real framework source, each with a canonical docs.spring.io link. Nothing is summarized or paraphrased on the way through.
Light on tokens
A search hit costs a few hundred tokens. A type outline replaces a nine-hundred-line file. Your agent stops unzipping Maven artifacts to grep for class names.

Point your agent at it

Claude Code

claude mcp add --transport http sprig https://mcp.sprig.dev/mcp

Any MCP client

{
  "mcpServers": {
    "sprig": { "type": "http", "url": "https://mcp.sprig.dev/mcp" }
  }
}

Your agent’s Spring knowledge is two versions old.

Pinned to your version

Primary sources

Light on tokens

Point your agent at it