get_reply_order — Cosend MCP Tool Read-only
get_reply_order
(get reply order) is one of 98 tools on the
Cosend
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call get_reply_order from your client
- Claude Code Cosend get_reply_order run in your project directory
- Claude Desktop Cosend get_reply_order ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Cosend get_reply_order ~/.cursor/mcp.json
- VS Code Cosend get_reply_order .vscode/mcp.json
- Zed Cosend get_reply_order ~/.config/zed/settings.json
- Windsurf Cosend get_reply_order ~/.codeium/windsurf/mcp_config.json
- Cline Cosend get_reply_order ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Cosend get_reply_order ~/.gemini/settings.json
- Grok Cosend get_reply_order .mcp.json (in your project root)
- ChatGPT Cosend get_reply_order Settings → Connectors → Advanced → Developer mode
- Claude.ai Cosend get_reply_order Settings → Connectors → Add custom connector
- LangChain Cosend get_reply_order pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http mcp https://mcp.cosend.app/mcpOther tools on this server
- whoami
- list_conversations
- search_conversations
- read_conversation
- send_message
- list_contacts
- upsert_contact
- set_contact_consent
- list_templates
- submit_template
- list_automations
- validate_automation
- upsert_automation
- deploy_automation
- set_automation_state
- list_runs
- get_run
- get_usage
- resolve_conversation
- create_setup_link
- check_setup_link
- cancel_setup_link
- whatsapp_link
- template_check
- message_cost
- get_conversation
- search_messages
- get_message
- get_media
- get_inbox_overview
- mark_read
- translate_message
- draft_reply
- update_conversation
- bulk_update_conversations
- take_over_conversation
- ask_for_conversation
- list_chat_notes
- chat_notes
- list_inbox_views
- inbox_views
- get_contact
- update_contact
- tag_contact
- delete_contact
- merge_contacts
- list_contact_fields
- contact_fields
- import_contacts
- list_contact_imports
- list_numbers
- get_number
- list_connectors
- get_integration_accounts
- list_google_logins
- get_setup_guide
- get_template
- change_template
- sync_templates
- list_template_category_changes
- acknowledge_category_change
- get_automation
- manage_automation
- test_automation
- run_automation
- cancel_run
- get_automation_catalogue
- automation_recipes
- list_members
- get_billing
- get_report
- get_data_policy
- upload_media
- get_assistant_persona
- update_assistant_persona
- get_knowledge
- change_knowledge
- try_assistant
- get_business_profile
- update_number
- manage_number
- read_integration
- manage_integration
- create_spreadsheet
- get_authoring_chat
- describe_automation
- get_approvals
- request_approval
- list_audiences
- create_audience
- list_campaigns
- get_campaign
- create_campaign
- update_campaign
- preview_campaign
- send_campaign
- cancel_campaign
This list was read from the server itself, by connecting to it and calling tools/list on 11 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.