get_webhook_config — Orbilyn MCP Tool Read-only
get_webhook_config
(get webhook config) 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 get_webhook_config from your client
- Claude Code Orbilyn get_webhook_config run in your project directory
- Claude Desktop Orbilyn get_webhook_config ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Orbilyn get_webhook_config ~/.cursor/mcp.json
- VS Code Orbilyn get_webhook_config .vscode/mcp.json
- Zed Orbilyn get_webhook_config ~/.config/zed/settings.json
- Windsurf Orbilyn get_webhook_config ~/.codeium/windsurf/mcp_config.json
- Cline Orbilyn get_webhook_config ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Orbilyn get_webhook_config ~/.gemini/settings.json
- Grok Orbilyn get_webhook_config .mcp.json (in your project root)
- ChatGPT Orbilyn get_webhook_config Settings → Connectors → Advanced → Developer mode
- Claude.ai Orbilyn get_webhook_config Settings → Connectors → Add custom connector
- LangChain Orbilyn get_webhook_config 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
- configure_webhook
- run_monitoring
- start_catalog_audit
- get_audit_status
- get_audit_result
- create_monitor
- update_monitor
- pause_monitor
- list_monitors
- 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.