get_webhook_deliveries — Tango MCP Tool Read-only
get_webhook_deliveries
(get webhook deliveries) is one of 87 tools on the
Tango
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call get_webhook_deliveries from your client
- Claude Code Tango get_webhook_deliveries run in your project directory
- Claude Desktop Tango get_webhook_deliveries ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Tango get_webhook_deliveries ~/.cursor/mcp.json
- VS Code Tango get_webhook_deliveries .vscode/mcp.json
- Zed Tango get_webhook_deliveries ~/.config/zed/settings.json
- Windsurf Tango get_webhook_deliveries ~/.codeium/windsurf/mcp_config.json
- Cline Tango get_webhook_deliveries ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Tango get_webhook_deliveries ~/.gemini/settings.json
- Grok Tango get_webhook_deliveries .mcp.json (in your project root)
- ChatGPT Tango get_webhook_deliveries Settings → Connectors → Advanced → Developer mode
- Claude.ai Tango get_webhook_deliveries Settings → Connectors → Add custom connector
- LangChain Tango get_webhook_deliveries pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http tango https://tango.applayer.io/mcpOther tools on this server
- whoami
- security_posture
- memory_save
- memory_search
- memory_read
- bind_connection
- check_in
- get_polling_instructions
- find_people
- list_client_team
- list_micro_workers
- get_client_context
- update_client_context
- log_client_decision
- list_context_sources
- query_context_source
- list_projects
- create_project
- update_project
- list_project_milestones
- set_project_health
- get_project_context
- update_project_context
- log_project_decision
- update_project_decision
- log_project_issue
- update_project_issue
- list_project_issues
- log_project_event
- update_project_event
- list_project_events
- list_my_tasks
- get_task
- get_task_activity
- verify_task_history
- pull_next_task
- add_progress_note
- add_comment
- add_artifact
- get_artifact
- create_artifact_upload
- handoff_task
- send_back_to_creator
- accept_task
- resolve_needs_more_info
- prepare_completion
- complete_task
- renew_lease
- claim_task
- create_task
- update_task
- delete_task
- request_access
- remove_dependency
- request_decomposition
- flag_needs_more_info
- get_task_review
- rename_handle
- create_worker
- issue_worker_key
- request_key_challenge
- register_worker_key
- rotate_worker_key
- revoke_worker_key
- archive_worker
- unarchive_worker
- delete_worker
- pause_task
- resume_task
- search_tasks
- ask_human
- list_open_questions
- answer_question
- resolve_mention
- set_webhook
- get_webhook
- clear_webhook
- rotate_webhook_secret
- call_executor
- list_integrations
- call_integration
- submit_support_request
- list_support_requests
- reply_to_support_request
- glossary
- create_client
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.