schedule_line_publish — EchoRelay MCP Tool
schedule_line_publish
(schedule line publish) is one of 80 tools on the
EchoRelay
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call schedule_line_publish from your client
- Claude Code EchoRelay schedule_line_publish run in your project directory
- Claude Desktop EchoRelay schedule_line_publish ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor EchoRelay schedule_line_publish ~/.cursor/mcp.json
- VS Code EchoRelay schedule_line_publish .vscode/mcp.json
- Zed EchoRelay schedule_line_publish ~/.config/zed/settings.json
- Windsurf EchoRelay schedule_line_publish ~/.codeium/windsurf/mcp_config.json
- Cline EchoRelay schedule_line_publish ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI EchoRelay schedule_line_publish ~/.gemini/settings.json
- Grok EchoRelay schedule_line_publish .mcp.json (in your project root)
- ChatGPT EchoRelay schedule_line_publish Settings → Connectors → Advanced → Developer mode
- Claude.ai EchoRelay schedule_line_publish Settings → Connectors → Add custom connector
- LangChain EchoRelay schedule_line_publish pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http management https://mcp.echorelay.devOther tools on this server
- get_project
- list_lines
- list_endpoints
- get_endpoint
- get_config
- config_diff
- list_config_revisions
- get_line_draft
- preview_line_draft
- publish_line_draft
- discard_line_draft
- discard_draft_endpoint
- cancel_line_publish
- rollback_config
- get_billing
- set_burst_opt_in
- set_rpm_ceiling
- set_outbound_allowlist
- create_line
- delete_line
- activate_line
- deactivate_line
- duplicate_line
- set_docs_shared
- create_endpoint
- generate_line_draft
- update_endpoint
- delete_endpoint
- default_endpoint_template
- dry_run_endpoint
- list_members
- invite_member
- remove_member
- set_member_role
- resend_invite
- list_api_keys
- create_api_key
- rotate_api_key
- reveal_rotation_successor
- revoke_api_key
- get_key_policy
- set_key_policy
- list_credentials
- create_credential
- update_credential
- delete_credential
- list_requests
- get_request
- get_receipts
- get_metrics
- list_dlq
- get_dlq_entry
- retry_dlq_entry
- discard_dlq_entry
- list_subscription_plans
- list_credit_packs
- list_addons
- get_subscription
- preview_plan_change
- start_subscription
- change_plan
- cancel_subscription
- set_overage_billing
- start_topup
- subscribe_addon
- unsubscribe_addon
- resume_addon
- downgrade_addon
- list_active_addons
- list_audit_events
- list_projects
- create_project
- rename_project
- archive_project
- protect_project
- unarchive_project
- create_project_token
- list_project_tokens
- revoke_project_token
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.