tetherscope

by joseteoio.github.joseteo/tetherscopev0.3.0

Give your AI coding agent eyes and hands on a real Android phone: live device mirror, localhost observability dashboard, and MCP server for Claude Code, Codex, and any MCP client. Screenshot, tap, swipe, type, and deep-link a real device while you build,

  • Runs on your machine
  • No known advisories
  • MIT

Version checks

  • Available on npm, latest 0.3.0 · checked

Not run yet – package checks are being switched on. It runs from a package on your machine, so instead of uptime we will start each new version in our sandbox.

How we check

Run it on your machine

Add to config.json in oterm's data folder (~/Library/Application Support/oterm on macOS, ~/.local/share/oterm on Linux, %APPDATA%\oterm on Windows):

{
  "mcpServers": {
    "tetherscope": {
      "command": "npx",
      "args": ["-y", "tetherscope"]
    }
  }
}
For agents: the install prompt

Every step above as one Markdown text, for an assistant installing it for you.

# Install the MCP server tetherscope (`io.github.joseteo/tetherscope`)

Its page: https://plug.directory/servers/io.github.joseteo/tetherscope

It runs on the person's machine and needs Node.js installed.

Use the section for the person's client.

## Claude Desktop, Cursor, Devin Desktop, Cline, LM Studio, Gemini CLI, mcp-client-cli, oterm, TUUI, BoltAI, AnythingLLM, Augment Code, Bob Shell, ECA, Kiro, Kiro CLI

Merge into the place for the person's client:

- Claude Desktop: claude_desktop_config.json (Settings › Developer › Edit Config)
- Cursor: ~/.cursor/mcp.json
- Devin Desktop: ~/.config/devin/mcp_config.json
- Cline: cline_mcp_settings.json (MCP Servers › Configure › Configure MCP Servers)
- LM Studio: mcp.json (Program › Install › Edit mcp.json)
- Gemini CLI: ~/.gemini/settings.json
- mcp-client-cli: ~/.llm/config.json
- oterm: config.json in oterm's data folder (~/Library/Application Support/oterm on macOS, ~/.local/share/oterm on Linux, %APPDATA%\oterm on Windows)
- TUUI: resources/assets/config/mcp.json in the installed app
- BoltAI: ~/.boltai/mcp.json
- AnythingLLM: anythingllm_mcp_servers.json in the AnythingLLM storage plugins directory
- Augment Code: Augment Settings Panel – MCP section – Import from JSON (VS Code extension)
- Bob Shell: ~/.bob/settings/mcp.json (global) or .bob/mcp.json (project)
- ECA: ~/.config/eca/config.json (global) or .eca/config.json in the project
- Kiro: ~/.kiro/settings/mcp.json (user) or .kiro/settings/mcp.json (workspace)
- Kiro CLI: ~/.kiro/settings/mcp.json (user) or .kiro/settings/mcp.json (workspace)

```json
{
  "mcpServers": {
    "tetherscope": {
      "command": "npx",
      "args": ["-y", "tetherscope"]
    }
  }
}
```

## Claude Code

Run in a terminal:

```sh
claude mcp add --transport stdio tetherscope -- npx -y tetherscope
```

## VS Code

Merge into .vscode/mcp.json:

```json
{
  "servers": {
    "tetherscope": {
      "type": "stdio",
      "command": "npx",
      "args": ["-y", "tetherscope"]
    }
  }
}
```

## Zed

Merge into ~/.config/zed/settings.json:

```json
{
  "context_servers": {
    "tetherscope": {
      "command": "npx",
      "args": ["-y", "tetherscope"]
    }
  }
}
```

## Continue

Merge into ~/.continue/config.yaml:

```yaml
mcpServers:
  - name: "tetherscope"
    type: stdio
    command: "npx"
    args:
      - "-y"
      - "tetherscope"
```

## Goose

Merge into ~/.config/goose/config.yaml:

```yaml
extensions:
  "tetherscope":
    type: stdio
    name: "tetherscope"
    enabled: true
    cmd: "npx"
    args: ["-y", "tetherscope"]
    env_keys: []
    envs: {}
    timeout: 300
```

## Codex

Run in a terminal:

```sh
codex mcp add tetherscope -- npx -y tetherscope
```

## Agenvoy

Merge into ~/.config/agenvoy/mcp.json:

```json
{
  "servers": {
    "tetherscope": {
      "command": "npx",
      "args": ["-y", "tetherscope"]
    }
  }
}
```

## Amp

Merge into ~/.config/amp/settings.json (user) or .amp/settings.json (workspace):

```json
{
  "amp.mcpServers": {
    "tetherscope": {
      "command": "npx",
      "args": ["-y", "tetherscope"]
    }
  }
}
```

Then restart the client, or reload its MCP servers, and ask it to list the server's tools to confirm it started.

Known advisories

None known for its packages.

Checked 2026-10-28 against OSV.dev and deps.dev.

From npm. We have not checked this server yet. Report a problem