register_for_event — Send16 MCP Tool
register_for_event
(register for event) is one of 87 tools on the
Send16
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call register_for_event from your client
- Claude Code Send16 register_for_event run in your project directory
- Claude Desktop Send16 register_for_event ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Send16 register_for_event ~/.cursor/mcp.json
- VS Code Send16 register_for_event .vscode/mcp.json
- Zed Send16 register_for_event ~/.config/zed/settings.json
- Windsurf Send16 register_for_event ~/.codeium/windsurf/mcp_config.json
- Cline Send16 register_for_event ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Send16 register_for_event ~/.gemini/settings.json
- Grok Send16 register_for_event .mcp.json (in your project root)
- ChatGPT Send16 register_for_event Settings → Connectors → Advanced → Developer mode
- Claude.ai Send16 register_for_event Settings → Connectors → Add custom connector
- LangChain Send16 register_for_event pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http send16 https://mcp.send16.com
Other tools on this server
- whoami
- send_email
- send_campaign_test
- create_campaign
- design_email_template
- list_campaigns
- create_contact
- search_contacts
- list_contacts
- import_contacts
- list_domains
- check_domain_health
- get_campaign_stats
- get_deliverability_status
- list_automations
- get_automation
- enroll_in_automation
- send_event
- list_templates
- save_template
- list_workspace_templates
- send_template_test
- get_template
- render_email_content
- add_domain
- pre_send_review
- generate_email_from_url
- list_messages
- get_message
- get_message_events
- list_convos
- get_convo
- send_reply
- mark_convo_read
- update_convo
- add_convo_note
- screener_decide
- list_inbox_counts
- list_topics
- create_topic
- update_topic
- delete_topic
- list_actions
- get_action
- create_action
- update_action
- delete_action
- list_audiences
- create_audience
- add_contacts_to_audience
- remove_contact_from_audience
- delete_audience
- list_segments
- preview_segment
- list_events
- get_event_insights
- list_event_registrations
- check_in_attendee
- update_contact
- delete_contact
- get_contact_timeline
- get_contact_health_score
- send_broadcast
- schedule_campaign
- update_campaign
- pause_campaign
- resume_campaign
- duplicate_campaign
- delete_campaign
- preview_campaign_recipients
- activate_automation
- pause_automation
- get_automation_stats
- list_automation_enrollments
- list_workspaces
- get_workspace
- get_brand
- update_brand
- get_workspace_usage
- list_suppressions
- add_suppression
- remove_suppression
- list_webhooks
- create_webhook
- delete_webhook
- regenerate_webhook_secret
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.