opensolr-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| OPENSOLR_EMAIL | Yes | Opensolr account email | |
| OPENSOLR_API_KEY | Yes | Opensolr API key |
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 |
|---|---|
| opensolr_searchA | Search an Opensolr index and return the k most relevant documents. |
| opensolr_search_by_imageA | Search an Opensolr index with a PHOTO instead of a text query. |
| opensolr_ai_answerA | Ask a question and get a grounded RAG answer generated ONLY from the content already indexed in the given Opensolr index. Retrieval runs through the platform's tuned hybrid pipeline (the index's saved Search Tuning applies automatically) — the top rag_docs hits (first rag_words words of text each) become the LLM context, the same pipeline as the hosted search UI. filter_query optionally narrows retrieval with a raw Solr fq expression; instruction optionally replaces the default prompt (e.g. "Answer in German", "Extract a list of people"); tuning optionally overrides retrieval knobs per call. That list is the whole set, not a sample — an abbreviated one reads as everything that is supported, and freshness_boost was invisible to callers because of it: fw_title, fw_description, fw_uri, fw_text, fw_text_t, lexical_weight, vector_weight, vector_topk, search_mode (union / keywords_required / meaning_required / intersection), quality_boost, min_score, freshness_boost, fresh_bias, lexical_norm_k, mm (flexible / balanced / strict or raw Solr mm syntax). freshness_boost and fresh_bias are different knobs despite the names: the first is a hard window in DAYS that filters older documents out, the second only re-orders, multiplying each score by a recency curve on creation_date so recent documents win ties while nothing becomes unreachable. |
| opensolr_list_indexesA | List all search indexes in the connected Opensolr account. |
| opensolr_index_infoB | Get connection details for an index: Solr URL, version, environment. (Credentials are intentionally not returned.) |
| opensolr_add_documentsA | Index plain-text documents via the Opensolr Data Ingestion API. |
| opensolr_ingest_statusB | Status of a Data Ingestion job (state, processed/success/failed doc counts). Also visible in the Opensolr Control Panel. |
| opensolr_delete_documentsA | Delete documents by ids (Solr ids or your original ids) or by a raw Solr query, e.g. 'meta_category:"drafts"' or '+id:"abc123"'. |
| opensolr_create_indexB | Create a new vector-enabled Opensolr index. location: us, de, fi, or any environment id from opensolr_vector_regions. Additional dedicated regions can be deployed on request (support@opensolr.com). |
| opensolr_vector_regionsA | List the vector-enabled Opensolr environments currently available (Solr 9.x with dense vectors and the hybrid query parser). |
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 10 tools
Each tool targets a distinct operation: text search, image search, RAG answering, index listing/info, ingestion lifecycle, deletion, and creation. Even the two search variants are clearly separated by query type, and the supporting region/status tools have unambiguous roles.
All tools share the opensolr_ prefix and generally follow a verb_noun pattern, but a few names like opensolr_index_info, opensolr_ai_answer, opensolr_ingest_status, and opensolr_vector_regions are noun-style rather than verb-first. The convention is still predictable and readable.
Ten tools cover the primary surface of an Opensolr search server: searching, ingesting, managing documents, and managing indexes. The count feels appropriately scoped without redundant or excessive entries.
Core workflows are well covered: create/list/inspect indexes, ingest and check status, delete documents, search by text or image, and get grounded answers. Minor gaps exist, such as no delete_index operation and no explicit index settings update or single-document fetch, but these are not fatal to typical usage.