# libtmux_mcp.resources.hierarchy.register_completions

- **Module:** libtmux_mcp.resources.hierarchy
- **Package:** libtmux-mcp
- **Language:** Python
- **Kind:** function
- **Source:** https://github.com/tmux-python/libtmux-mcp/blob/4daddc0dfca96c43bf521d818bf91564e1434760/src/libtmux_mcp/resources/hierarchy.py#L53
- **Page:** https://libtmux.org/en/py/latest/mcp/reference/libtmux_mcp-resources-hierarchy-register_completions/

```
libtmux_mcp.resources.hierarchy.register_completions(mcp: FastMCP) -> None
```

Answer argument completion for the ``tmux://`` templates.

The templates take live tmux identifiers, which a reader cannot guess
and the template listing does not carry — MCP publishes only the URI
template itself, never its parameter domain. A completion handler is
the protocol's way to offer them.

Agent clients do not send ``completion/complete``; human-facing hosts
(the MCP Inspector's UI, VS Code) do, which is who this serves.