Quarkus Solr Dev UI

The extension registers a card in the Quarkus Dev UI when running in dev mode. The card is available at /q/dev-ui and provides a direct link to the Solr Admin UI of the running dev service container. The Admin UI URL is resolved dynamically from the running container’s mapped port.

MCP

All Solr Dev UI operations are exposed as MCP tools, making them available to AI assistants and MCP clients connected to the dev mode endpoint. The following tools are provided:

Tool Description

Tool	Description
`getSolrAdminUrl`	Returns the configured Solr URL.
`listCollections`	Lists all collections in the Solr instance.
`getSchema(collection)`	Returns the schema for the named collection.
`search(collection, query, fq, sortClauses, start, rows)`	Executes a search. `query` defaults to `:`. `fq` accepts a plain string or a JSON array of filter queries. `sortClauses` is a JSON object mapping field names to `asc` or `desc`. `start` and `rows` control pagination.
`indexJsonDocuments(collection, json)`	Indexes documents into the named collection. `json` can be a single JSON object or an array of objects. Changes are committed immediately.

getSolrAdminUrl

Returns the configured Solr URL.

listCollections

Lists all collections in the Solr instance.

getSchema(collection)

Returns the schema for the named collection.

search(collection, query, fq, sortClauses, start, rows)

Executes a search. query defaults to :. fq accepts a plain string or a JSON array of filter queries. sortClauses is a JSON object mapping field names to asc or desc. start and rows control pagination.

indexJsonDocuments(collection, json)

Indexes documents into the named collection. json can be a single JSON object or an array of objects. Changes are committed immediately.

The registered Solr beans are also exposed as an MCP resource, so connected clients can inspect the application’s Solr configuration.

See the Quarkus Dev MCP guide for how to connect an MCP client.