tinysearch MCP Server

What this does

tinysearch exposes a set of tools to Claude over the Model Context Protocol. After you add it to claude_desktop_config.json (snippet above) and restart Claude Desktop, those tools become callable inside any conversation.

Requirements

This server needs the following environment variables to be set before it can run:

MCP_TRANSPORT
TINYSEARCH_CONFIG_PATH
SEARXNG_URL
TINYSEARCH_EMBEDDING_BACKEND
TINYSEARCH_EMBEDDING_MODEL
OTEL_SERVICE_NAME
OTEL_EXPORTER_OTLP_ENDPOINT
OTEL_EXPORTER_OTLP_PROTOCOL
OTEL_EXPORTER_OTLP_HEADERS
OTEL_RESOURCE_ATTRIBUTES
OTEL_TRACES_EXPORTER
OTEL_METRICS_EXPORTER
OTEL_SDK_DISABLED

Set these via the env object in your MCP config (see claude_desktop_config.json snippet above).

How do I install tinysearch?

The install section on this page carries the maker's install command for tinysearch, as submitted. Restart your client afterwards and the tools appear in your next conversation.

Which clients work with tinysearch?

This page carries setup and config for Claude Code. Any other MCP client that accepts a standard server config can connect to tinysearch as well.

Does tinysearch need an API key?

Yes. Before it can run, set these environment variables: MCP_TRANSPORT, TINYSEARCH_CONFIG_PATH, SEARXNG_URL, TINYSEARCH_EMBEDDING_BACKEND, TINYSEARCH_EMBEDDING_MODEL, OTEL_SERVICE_NAME, OTEL_EXPORTER_OTLP_ENDPOINT, OTEL_EXPORTER_OTLP_PROTOCOL, OTEL_EXPORTER_OTLP_HEADERS, OTEL_RESOURCE_ATTRIBUTES, OTEL_TRACES_EXPORTER, OTEL_METRICS_EXPORTER, OTEL_SDK_DISABLED. They go in the env block of your MCP config.