Tinycontext

Tinycontext runs locally from a container image in an OCI registry such as Docker Hub or GitHub Container Registry: docker.io/marcellm01/tinycontext:v0.5.0. 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 TINYCONTEXT_CONFIG_PATH -e TINYCONTEXT_MEMORY_DB_PATH -e TINYCONTEXT_MODELS_DIR -e OTEL_SERVICE_NAME -e OTEL_EXPORTER_OTLP_ENDPOINT -e OTEL_EXPORTER_OTLP_PROTOCOL -e OTEL_EXPORTER_OTLP_HEADERS docker.io/marcellm01/tinycontext:v0.5.0. It reads these environment variables: MCP_TRANSPORT, TINYCONTEXT_CONFIG_PATH, TINYCONTEXT_MEMORY_DB_PATH, TINYCONTEXT_MODELS_DIR, OTEL_SERVICE_NAME, OTEL_EXPORTER_OTLP_ENDPOINT, OTEL_EXPORTER_OTLP_PROTOCOL and OTEL_EXPORTER_OTLP_HEADERS (secret); set them in the client's configuration for this server.

Tinycontext runs locally from a Python package published to PyPI: tinysuite-context version 0.5.0. 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-context.

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

{
  "mcpServers": {
    "tinycontext": {
      "command": "docker",
      "args": [
        "run",
        "-i",
        "--rm",
        "-e",
        "MCP_TRANSPORT",
        "-e",
        "TINYCONTEXT_CONFIG_PATH",
        "-e",
        "TINYCONTEXT_MEMORY_DB_PATH",
        "-e",
        "TINYCONTEXT_MODELS_DIR",
        "-e",
        "OTEL_SERVICE_NAME",
        "-e",
        "OTEL_EXPORTER_OTLP_ENDPOINT",
        "-e",
        "OTEL_EXPORTER_OTLP_PROTOCOL",
        "-e",
        "OTEL_EXPORTER_OTLP_HEADERS",
        "docker.io/marcellm01/tinycontext:v0.5.0"
      ],
      "env": {
        "MCP_TRANSPORT": "<value>",
        "TINYCONTEXT_CONFIG_PATH": "<value>",
        "TINYCONTEXT_MEMORY_DB_PATH": "<value>",
        "TINYCONTEXT_MODELS_DIR": "<value>",
        "OTEL_SERVICE_NAME": "<value>",
        "OTEL_EXPORTER_OTLP_ENDPOINT": "<value>",
        "OTEL_EXPORTER_OTLP_PROTOCOL": "<value>",
        "OTEL_EXPORTER_OTLP_HEADERS": "<secret>"
      }
    }
  }
}

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