wi_list_site_abilities — WebinarIgnition MCP Tool
wi_list_site_abilities
(wi list site abilities) is one of 90 tools on the
WebinarIgnition
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call wi_list_site_abilities from your client
- Claude Code WebinarIgnition wi_list_site_abilities run in your project directory
- Claude Desktop WebinarIgnition wi_list_site_abilities ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor WebinarIgnition wi_list_site_abilities ~/.cursor/mcp.json
- VS Code WebinarIgnition wi_list_site_abilities .vscode/mcp.json
- Zed WebinarIgnition wi_list_site_abilities ~/.config/zed/settings.json
- Windsurf WebinarIgnition wi_list_site_abilities ~/.codeium/windsurf/mcp_config.json
- Cline WebinarIgnition wi_list_site_abilities ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI WebinarIgnition wi_list_site_abilities ~/.gemini/settings.json
- Grok WebinarIgnition wi_list_site_abilities .mcp.json (in your project root)
- ChatGPT WebinarIgnition wi_list_site_abilities Settings → Connectors → Advanced → Developer mode
- Claude.ai WebinarIgnition wi_list_site_abilities Settings → Connectors → Add custom connector
- LangChain WebinarIgnition wi_list_site_abilities pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http mcp https://mcp.webinarignition.com/?src=registryOther tools on this server
- wi_get_session_facts
- wi_get_connector_status
- wi_answer_product_question
- wi_get_setup_plan
- wi_start_webinar
- wi_continue_webinar
- wi_write_webinar_invitation_emails
- wi_check_wordpress
- wi_connect_wordpress_woocommerce_site
- wi_disconnect_wordpress
- wi_create_webinar_registration_page
- wi_get_build_status
- wi_create_handoff_link
- wi_delete_webinar
- wi_list_webinar_leads_registrants
- wi_get_webinar_attendance_stats
- wi_get_webinar_funnel_conversion_stats
- wi_get_webinar_revenue_woocommerce
- wi_list_webinars
- wi_get_webinar
- wi_get_webinar_emails
- wi_get_registration_fields
- wi_get_webinar_settings
- wi_get_webinar_colors
- wi_list_webinar_products
- wi_get_streaming_status
- wi_get_webinar_questions
- wi_get_webinar_prompter
- wi_get_renotification_status
- wi_check_mail_delivery
- wi_check_embedding
- wi_list_webinar_links
- wi_list_webhooks
- wi_read_webhook_deliveries
- wi_get_webhook_test_address
- wi_find_wordpress_user
- wi_find_media
- wi_get_webinar_page_blocks
- wi_run_webinar_preflight
- wi_get_webinar_checklist
- wi_check_participant_journey
- wi_get_webinar_report
- wi_export_registrants_csv
- wi_export_webinar
- wi_change_webinar_text
- wi_change_webinar_title
- wi_change_webinar_schedule
- wi_change_webinar_room
- wi_change_webinar_visibility
- wi_change_webinar_video
- wi_change_webinar_cta
- wi_change_webinar_reminders
- wi_change_webinar_email
- wi_change_registration_fields
- wi_change_site_colors
- wi_change_host_photo
- wi_change_webinar_offer
- wi_change_webinar_page_block
- wi_change_registration_animation
- wi_rewrite_webinar_texts
- wi_change_participant_label
- wi_change_webinar_settings
- wi_change_site_settings
- wi_create_webinar_link
- wi_connect_streaming
- wi_repair_webinar_pages
- wi_change_webinar_qa
- wi_answer_webinar_question
- wi_delete_webinar_question
- wi_delete_all_webinar_questions
- wi_write_webinar_prompter
- wi_send_webinar_test_email
- wi_send_webinar_followup
- wi_resend_webinar_mails
- wi_change_webinar_autoresponder
- wi_test_webinar_autoresponder
- wi_save_webhook
- wi_delete_webhook
- wi_test_webhook
- wi_reset_webinar_funnel
- wi_delete_registrant
- wi_fix_thankyou_date
- wi_delete_all_registrants
- wi_import_registrants_csv
- wi_delete_webinar_logs
- wi_change_advanced_settings
- wi_copy_webinar_pages
- wi_import_webinar
- wi_import_legacy_webinar
This list was read from the server itself, by connecting to it and calling tools/list on 14 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.