list_monitors — Orbilyn MCP Tool Read-only
list_monitors
(list monitors) is one of 21 tools on the
Orbilyn
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call list_monitors from your client
- Claude Code Orbilyn list_monitors run in your project directory
- Claude Desktop Orbilyn list_monitors ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Orbilyn list_monitors ~/.cursor/mcp.json
- VS Code Orbilyn list_monitors .vscode/mcp.json
- Zed Orbilyn list_monitors ~/.config/zed/settings.json
- Windsurf Orbilyn list_monitors ~/.codeium/windsurf/mcp_config.json
- Cline Orbilyn list_monitors ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Orbilyn list_monitors ~/.gemini/settings.json
- Grok Orbilyn list_monitors .mcp.json (in your project root)
- ChatGPT Orbilyn list_monitors Settings → Connectors → Advanced → Developer mode
- Claude.ai Orbilyn list_monitors Settings → Connectors → Add custom connector
- LangChain Orbilyn list_monitors pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http mcp https://app.orbilyn.com/api/mcpOther tools on this server
- list_integrations
- list_mismatches
- get_monitoring_alerts
- find_product
- get_comparison_summary
- catalog_health_score
- list_critical_issues
- prepare_fix_list
- ai_readiness_report
- explain_issue
- get_webhook_config
- configure_webhook
- run_monitoring
- start_catalog_audit
- get_audit_status
- get_audit_result
- create_monitor
- update_monitor
- pause_monitor
- get_monitor_history
This list was read from the server itself, by connecting to it and calling tools/list on 5 November 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.