intent_list_matches — LivinIsto — home watch MCP Tool
intent_list_matches
(intent list matches) is one of 4 tools on the
LivinIsto — home watch
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call intent_list_matches from your client
- Claude Code LivinIsto — home watch intent_list_matches run in your project directory
- Claude Desktop LivinIsto — home watch intent_list_matches ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor LivinIsto — home watch intent_list_matches ~/.cursor/mcp.json
- VS Code LivinIsto — home watch intent_list_matches .vscode/mcp.json
- Zed LivinIsto — home watch intent_list_matches ~/.config/zed/settings.json
- Windsurf LivinIsto — home watch intent_list_matches ~/.codeium/windsurf/mcp_config.json
- Cline LivinIsto — home watch intent_list_matches ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI LivinIsto — home watch intent_list_matches ~/.gemini/settings.json
- Grok LivinIsto — home watch intent_list_matches .mcp.json (in your project root)
- ChatGPT LivinIsto — home watch intent_list_matches Settings → Connectors → Advanced → Developer mode
- Claude.ai LivinIsto — home watch intent_list_matches Settings → Connectors → Add custom connector
- LangChain LivinIsto — home watch intent_list_matches pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http intents https://www.livinisto.sk/mcp/zameryOther tools on this server
This list was read from the server itself, by connecting to it and calling tools/list on 21 October 2026. It is what
the server actually exposes, not what its listing claims.
Mutating and Read-only are read off each tool's name, not its schema — a hint, not a guarantee. The registry stores tool names only; connect the server for its live schemas.