device_list — Netmon (demo) MCP Tool
device_list
(device list) is one of 36 tools on the
Netmon (demo)
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call device_list from your client
- Claude Code Netmon (demo) device_list run in your project directory
- Claude Desktop Netmon (demo) device_list ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Netmon (demo) device_list ~/.cursor/mcp.json
- VS Code Netmon (demo) device_list .vscode/mcp.json
- Zed Netmon (demo) device_list ~/.config/zed/settings.json
- Windsurf Netmon (demo) device_list ~/.codeium/windsurf/mcp_config.json
- Cline Netmon (demo) device_list ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Netmon (demo) device_list ~/.gemini/settings.json
- Grok Netmon (demo) device_list .mcp.json (in your project root)
- ChatGPT Netmon (demo) device_list Settings → Connectors → Advanced → Developer mode
- Claude.ai Netmon (demo) device_list Settings → Connectors → Add custom connector
- LangChain Netmon (demo) device_list pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http netmon-demo https://netmon.com/mcp-demo/mcpOther tools on this server
- get_network_entity_info
- arp_lookup
- ping
- traceroute
- port_map
- search_ip
- syslog_search
- eventlog_search
- eve_search
- eve_get
- log_severity_summary
- syslog_facets
- netflow_search
- netflow_raw_search
- flow_summary
- device_get
- device_find
- overwatch_summary
- snmp_test
- snmp_walk_last
- snmp_walk_run
- agent_services
- agent_processes
- alerts_list
- alerts_history
- maintenance_windows_list
- tags_list
- top_bandwidth
- arp_table
- interfaces_search
- device_metric_summary
- agent_disk_usage
- capture_list
- capture_get
- speedtest_history
This list was read from the server itself, by connecting to it and calling tools/list on 24 September 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.