Tinysearch

Tinysearch runs locally from a container image in an OCI registry such as Docker Hub or GitHub Container Registry: docker.io/marcellm01/tinysearch:v0.6.5. It speaks MCP over stdio, so the client starts it as a program and talks to it through standard input and output. It needs Docker or another OCI container runtime; started with docker run - the usual command is docker run -i --rm -e MCP_TRANSPORT -e TINYSEARCH_CONFIG_PATH -e SEARXNG_URL -e TINYSEARCH_EMBEDDING_BACKEND -e TINYSEARCH_EMBEDDING_MODEL -e OTEL_SERVICE_NAME -e OTEL_EXPORTER_OTLP_ENDPOINT -e OTEL_EXPORTER_OTLP_PROTOCOL -e OTEL_EXPORTER_OTLP_HEADERS -e OTEL_RESOURCE_ATTRIBUTES -e OTEL_TRACES_EXPORTER -e OTEL_METRICS_EXPORTER -e OTEL_SDK_DISABLED docker.io/marcellm01/tinysearch:v0.6.5. It reads 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 (secret), OTEL_RESOURCE_ATTRIBUTES, OTEL_TRACES_EXPORTER, OTEL_METRICS_EXPORTER and OTEL_SDK_DISABLED; set them in the client's configuration for this server.

Tinysearch runs locally from a Python package published to PyPI: tinysuite-search version 0.6.5. It speaks MCP over stdio, so the client starts it as a program and talks to it through standard input and output. It needs Python; clients usually start it with uvx (from uv) or after pip install - the usual command is uvx tinysuite-search.

In the mcpServers JSON format that many desktop and editor MCP clients read, the entry looks like this (placeholders in angle brackets):

{
  "mcpServers": {
    "tinysearch": {
      "command": "docker",
      "args": [
        "run",
        "-i",
        "--rm",
        "-e",
        "MCP_TRANSPORT",
        "-e",
        "TINYSEARCH_CONFIG_PATH",
        "-e",
        "SEARXNG_URL",
        "-e",
        "TINYSEARCH_EMBEDDING_BACKEND",
        "-e",
        "TINYSEARCH_EMBEDDING_MODEL",
        "-e",
        "OTEL_SERVICE_NAME",
        "-e",
        "OTEL_EXPORTER_OTLP_ENDPOINT",
        "-e",
        "OTEL_EXPORTER_OTLP_PROTOCOL",
        "-e",
        "OTEL_EXPORTER_OTLP_HEADERS",
        "-e",
        "OTEL_RESOURCE_ATTRIBUTES",
        "-e",
        "OTEL_TRACES_EXPORTER",
        "-e",
        "OTEL_METRICS_EXPORTER",
        "-e",
        "OTEL_SDK_DISABLED",
        "docker.io/marcellm01/tinysearch:v0.6.5"
      ],
      "env": {
        "MCP_TRANSPORT": "<value>",
        "TINYSEARCH_CONFIG_PATH": "<value>",
        "SEARXNG_URL": "<value>",
        "TINYSEARCH_EMBEDDING_BACKEND": "<value>",
        "TINYSEARCH_EMBEDDING_MODEL": "<value>",
        "OTEL_SERVICE_NAME": "<value>",
        "OTEL_EXPORTER_OTLP_ENDPOINT": "<value>",
        "OTEL_EXPORTER_OTLP_PROTOCOL": "<value>",
        "OTEL_EXPORTER_OTLP_HEADERS": "<secret>",
        "OTEL_RESOURCE_ATTRIBUTES": "<value>",
        "OTEL_TRACES_EXPORTER": "<value>",
        "OTEL_METRICS_EXPORTER": "<value>",
        "OTEL_SDK_DISABLED": "<value>"
      }
    }
  }
}

Derived from the registry entry, not tested here. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect