Tether MCP Server

What the code does

We read the source, 2 d ago · rules 995398eba69f

What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.

    return os.path.isdir(os.path.join(cache_dir, repo_dir))

Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.

Connect this server

This server runs on your own machine — install it with the package manager and the client starts it for you. Package name taken from the official registry entry.

claude mcp add tether -- uvx tether-memory

{
  "mcpServers": {
    "tether": {
      "command": "uvx",
      "args": [
        "tether-memory"
      ]
    }
  }
}

[mcp_servers.tether]
command = "uvx"
args = ["tether-memory"]

{
  "mcpServers": {
    "tether": {
      "command": "uvx",
      "args": [
        "tether-memory"
      ]
    }
  }
}

{
  "servers": {
    "tether": {
      "type": "stdio",
      "command": "uvx",
      "args": [
        "tether-memory"
      ]
    }
  }
}

Optional settings from the registry entry, left out of the block above: TETHER_DB (Path to the SQLite memory file. Defaults to the platform data dir (e.g. ~/.local/share/tether/memory.db)), TETHER_SEMANTIC (Set to 0 to force keyword-only recall. Semantic recall needs the [semantic] extra and is on by default when available), TETHER_SYNC_URL (Optional libSQL/Turso primary URL to sync memory across devices. Leave unset for local-only), TETHER_SYNC_TOKEN (Auth token for TETHER_SYNC_URL).