InnerVault

Tapo MCP

Stale Official MCP Registry, io.github.mihai-dinculescu

MCP server for discovering and controlling TP-Link Tapo smart home devices via AI Agents

Open the source (opens github.com) https://github.com/mihai-dinculescu/tapo

Before you use it

  • Runs on your computer with your permissions. Read what it can do before connecting it to an agent.
  • Needs credentials: TAPO_MCP_API_KEY, TAPO_MCP_CAMERA_PASSWORD, TAPO_MCP_CAMERA_USERNAME, TAPO_MCP_PASSWORD, TAPO_MCP_USERNAME. Use a key with the least access you can.

What it is

MCP servers from io.github.mihai-dinculescu.

The problem it solves and who it suits haven't been reviewed by InnerVault. The description above is the source's own.

How to get it

oci package (streamable-http)

ghcr.io/mihai-dinculescu/tapo-mcp:0.7.0

From the server's entry in the official MCP Registry

Settings it asks for

  • TAPO_MCP_USERNAME secret required · TP-Link Tapo account email
  • TAPO_MCP_PASSWORD secret required · TP-Link Tapo account password
  • TAPO_MCP_CAMERA_USERNAME secret · Optional camera account username; required for taking camera snapshots
  • TAPO_MCP_CAMERA_PASSWORD secret · Optional camera account password; required for taking camera snapshots
  • TAPO_MCP_DISCOVERY_TARGET required · IP address for device discovery, usually the network's broadcast address (e.g. 192.168.1.255)
  • TAPO_MCP_API_KEY secret required · Bearer token that clients send in the Authorization header; the image listens on all interfaces and does not start without it
  • TAPO_MCP_ALLOWED_HOSTS · Optional comma-separated Host header allowlist; replaces the loopback-only default
  • TAPO_MCP_PUBLIC_URL · Optional base URL clients reach the server at; enables short-lived snapshot links
  • TAPO_MCP_DISCOVERY_TIMEOUT · Device discovery timeout in seconds; must be between 1 and 60
  • TAPO_MCP_DISCOVERY_INTERVAL · Seconds between background device discoveries that refresh the device list; must be at least TAPO_MCP_DISCOVERY_TIMEOUT and at most 86400 (one day); tool…
  • OTEL_EXPORTER_OTLP_ENDPOINT · Base URL of an OTLP/HTTP collector to export traces to, such as http://localhost:4318; traces go to /v1/traces under it

Related

  1. tolpo

    MCP servers

    Local-first control of TP-Link Tapo smart-home devices for AI agents

    Stale Official MCP Registry, io.github.signerless Updated 33 days ago 2 notes

    tolpo@0.2.1
  2. GitHub MCP server

    MCP servers

    GitHub's official MCP server. It lets an agent read and work with repositories, issues and pull requests.

    Hand-checked InnerVault (hand-checked), GitHub 34.3k ★MIT

    https://api.githubcopilot.com/mcp/
  3. Official MCP Registry

    MCP servers

    The MCP project's own registry of public MCP servers, so you can look for a connector before building one.

    Hand-checked InnerVault (hand-checked), MCP project Moving from MIT to Apache-2.0

  4. MCP reference servers

    MCP servers

    Small example servers from the MCP project (filesystem, git, fetch, memory and more) that show how MCP works.

    Hand-checked InnerVault (hand-checked), MCP project Moving from MIT to Apache-2.0

  5. Anthropic's guide to adding MCP servers to Claude Code, with examples of local and remote servers.

    Hand-checked InnerVault (hand-checked), Anthropic Anthropic documentation

  6. Playwright MCP

    MCP servers

    Lets an agent drive a real browser: open pages, click, fill in forms and read what's on screen.

    Hand-checked InnerVault (hand-checked), Microsoft Apache-2.0

    claude mcp add playwright npx @playwright/mcp@latest