MCP server registry
Data & contentPublic source

Search MCP Server

Unified search for AI agents — full-text, vector/semantic, and structured search with index management, analytics, and synonym configuration. 20 tools supporting 7 backends with dual-mode (text + vector simultaneously).

What it gives an agent

A purpose-built capability behind one MCP connection.

The server owns its domain logic and publishes a tool contract an MCP client can discover. ADK-Rust can load that contract into an agent, normalize each schema for the chosen model provider, and keep the connection lifecycle outside the agent’s business logic.

01

Provides search capabilities through a typed MCP contract.

Architecture

How Search MCP Server fits into an agent system.

The model never needs the implementation details or credentials of the system behind the server. It sees reviewed tool definitions. The MCP client handles discovery and calls, while the server keeps ownership of validation, policy, and communication with its domain system.

01

ADK-Rust agent

Chooses a capability from the reviewed tool catalog.

02

MCP client

Discovers schemas, sends calls, and receives typed content.

03

Search MCP Server

Validates the request and owns 20 documented tool contracts.

04

Domain system

Keeps the API, data, credentials, and business rules behind the server.

Connection: stdio · Server framework: ADK MCP SDK + rmcp

From the project documentation

The server’s published architecture

Open the source diagram ↗
Search MCP Server architecture diagram from its official repository

Tool catalog

What can an agent ask Search MCP Server to do?

Each tool has a stable name, a human-readable purpose, and a JSON input contract discovered during MCP initialization. Risk classes come from the project’s registry manifest when one is available.

20 named tools

search

Full-text search with filters, facets, pagination

see documentation
semantic_search

Vector similarity search using embeddings

see documentation
multi_search

Search across multiple indexes at once

see documentation
suggest

Autocomplete/typeahead suggestions

see documentation
find_similar

Find documents similar to a given one

see documentation
list_indexes

List all indexes/collections

see documentation
get_index

Index schema, doc count, size

see documentation
create_index

Create index with field mappings

see documentation
index_document

Add/update a document

see documentation
delete_document

Remove a document

see documentation
upsert_vectors

Insert/update embeddings

see documentation
query_vectors

Top-k nearest neighbors

see documentation

Governance

Understand the effect of every tool.

A server connection inherits the authority of its credentials and deployment environment. The declarations below come from this project’s README and MCP registry manifest; your application still decides which tools an agent receives and where approval is required.

20 see documentation
  • Review the server documentation and deployment credentials before enabling it for an agent.

MCP surface

What the current documentation declares.

MCP can carry tools, resources, prompts, structured results, progress, cancellation, and long-running work. This record highlights the modern protocol features explicitly mentioned by this repository.

The current README concentrates on its tool surface. Check the source and release notes before relying on optional MCP capabilities beyond tool discovery and invocation.
ADK MCP SDKrmcp

Install and connect

Follow the project’s documented starting point.

Install the server in the environment that owns its credentials and domain access. Add it to your MCP host, verify the discovered tools, and narrow the toolset before giving it to a production agent.

Install
cargo install mcp-search
ADK-Rust connection shape
let toolset = McpToolset::from_stdio(
    "mcp-search",
    ["mcp-search"],
).await?;

let agent = LlmAgentBuilder::new("agent")
    .tools(toolset.tools().await?)
    .build()?;

Commands and configuration are extracted from the public README. Confirm prerequisites, environment variables, and release-specific options in the official documentation before deployment.

Official documentation

Continue with the project maintainers’ source of truth.

This page provides an approachable map of the server. The repository remains authoritative for exact schemas, prerequisites, configuration, examples, tests, releases, and security updates.

Source record

Release and repository metadata for this catalog entry.

View public repository ↗
Version
1.0.0
License
Apache-2.0
Tools
20
Revision
da789503e8a4
Updated
May 25, 2026
Transportsstdio