mark_all_notifications_read — Iris MCP Tool
mark_all_notifications_read
(mark all notifications read) is one of 81 tools on the
Iris
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call mark_all_notifications_read from your client
- Claude Code Iris mark_all_notifications_read run in your project directory
- Claude Desktop Iris mark_all_notifications_read ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Iris mark_all_notifications_read ~/.cursor/mcp.json
- VS Code Iris mark_all_notifications_read .vscode/mcp.json
- Zed Iris mark_all_notifications_read ~/.config/zed/settings.json
- Windsurf Iris mark_all_notifications_read ~/.codeium/windsurf/mcp_config.json
- Cline Iris mark_all_notifications_read ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Iris mark_all_notifications_read ~/.gemini/settings.json
- Grok Iris mark_all_notifications_read .mcp.json (in your project root)
- ChatGPT Iris mark_all_notifications_read Settings → Connectors → Advanced → Developer mode
- Claude.ai Iris mark_all_notifications_read Settings → Connectors → Add custom connector
- LangChain Iris mark_all_notifications_read pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http iris https://api.iris-ai.dev/mcpOther tools on this server
- list_campaigns
- create_campaign
- get_campaign
- update_campaign
- delete_campaign
- list_campaign_contacts
- add_campaign_contacts
- list_campaign_chats
- get_campaign_chat_messages
- rename_campaign_chat
- delete_campaign_chat
- get_campaign_usage
- analyze_campaign
- list_target_profiles
- create_target_profile
- delete_target_profile
- list_contacts
- create_contact
- get_contact
- get_contact_handles
- update_contact
- delete_contact
- bulk_import_contacts
- get_contact_usage
- list_contact_conversations
- list_conversations
- get_conversation
- create_conversation
- create_conversation_message
- get_conversation_messages
- mark_conversation_read
- update_conversation
- get_engagement_metrics
- list_pending_messages
- approve_message
- reject_message
- retry_message
- mark_message_sent
- submit_message_feedback
- bulk_message_action
- generate_content
- generate_campaign_content
- analyze_response
- get_ai_usage
- search_contacts
- search_campaign_contacts
- get_discovery_job
- list_discovery_sources
- get_analytics_overview
- get_campaign_analytics
- get_performance_metrics
- get_response_time
- get_contact_types
- get_billing_plans
- list_connected_accounts
- check_channel_availability
- send_channel_message
- list_notifications
- update_notification
- delete_notification
- get_usage
- get_changelog
- get_autopilot_status
- configure_autopilot
- run_autopilot_now
- get_responder
- configure_responder
- list_responder_activity
- get_conversation_responder
- set_conversation_responder
- list_responder_comment_triggers
- create_responder_comment_trigger
- update_responder_comment_trigger
- delete_responder_comment_trigger
- list_responder_posts
- list_audiences
- create_audience
- generate_audiences
- attach_audience_to_campaign
- delete_audience
This list was read from the server itself, by connecting to it and calling tools/list on 10 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.