Solr MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MCP_TRANSPORT | No | Set to choose how the server connects to the client. Values: `stdio` (default) or `sse`. | |
| SOLR_BASE_URL | Yes | Your Solr Admin base URL (including the `/solr` path). | |
| ZOOKEEPER_HOSTS | No | Optional. Comma-separated list of ZooKeeper hosts (e.g. `localhost:2181`). When unset, collections are discovered through Solr’s HTTP API. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| sql-selectA | Execute SQL SELECT queries against Solr (advanced). Prefer the Collection/Field Rules:
WHERE Clause Differences:
Supported Features:
Parameters:
|
| semantic-selectA | Semantic (vector) search combined with SQL filtering (advanced). Extends sql-select with semantic search: natural language Parameters:
|
| vector-selectA | Vector similarity search combined with SQL filtering (advanced). Extends sql-select with a query vector matched against a dense_vector/knn_vector
field. ORDER BY is not allowed in Parameters:
|
| get-schemaA | Retrieve schema information for a Solr collection. Returns field definitions, field types, and copy-field relationships from the Schema API. Call this before search when you need valid field names or types. Parameters:
|
| get-default-text-vectorizerA | Get the default embedding model used for semantic-select. Returns model name, vector dimensionality, and service URL. Use this to ensure Solr vector fields match the embedding model dimensions. |
| list-collectionsA | List all available Solr collections in the cluster. |
| searchA | Full-text search with filtering, faceting, sorting, and pagination. Queries Solr's Parameters:
Examples:
|
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 7 tools
The four query tools (search, sql-select, semantic-select, vector-select) overlap in purpose, but descriptions explicitly steer agents—search for Lucene/full-text, sql-select for the SQL interface, and the two vector variants differ clearly by taking either natural-language text or a precomputed vector. Boundaries are mostly clear with only minor potential confusion between semantic-select and vector-select.
All names use consistent kebab-case (get-default-text-vectorizer, list-collections, get-schema, sql-select, etc.), which is predictable and readable. Minor deviation: a few tools are noun-style rather than verb_noun (search, sql-select, vector-select), but the pattern is still coherent.
Seven tools is well-scoped for a Solr query server, with each tool covering a distinct capability (listing, schema introspection, full-text search, SQL, semantic, vector, and vectorizer defaults). No filler or redundancy that would suggest bloat.
The read/query surface is fairly complete (collections, schema, multiple query modes), but there are no write operations—no document indexing/update/delete and no collection create/delete—which are core Solr lifecycle operations. Agents can search but cannot mutate data or manage collections, leaving notable gaps.