create_workspace — SalesBlink Cold Email MCP Tool Mutating
create_workspace
(create workspace) is one of 88 tools on the
SalesBlink Cold Email
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call create_workspace from your client
- Claude Code SalesBlink Cold Email create_workspace run in your project directory
- Claude Desktop SalesBlink Cold Email create_workspace ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor SalesBlink Cold Email create_workspace ~/.cursor/mcp.json
- VS Code SalesBlink Cold Email create_workspace .vscode/mcp.json
- Zed SalesBlink Cold Email create_workspace ~/.config/zed/settings.json
- Windsurf SalesBlink Cold Email create_workspace ~/.codeium/windsurf/mcp_config.json
- Cline SalesBlink Cold Email create_workspace ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI SalesBlink Cold Email create_workspace ~/.gemini/settings.json
- Grok SalesBlink Cold Email create_workspace .mcp.json (in your project root)
- ChatGPT SalesBlink Cold Email create_workspace Settings → Connectors → Advanced → Developer mode
- Claude.ai SalesBlink Cold Email create_workspace Settings → Connectors → Add custom connector
- LangChain SalesBlink Cold Email create_workspace pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http cold-email-salesblink https://mcp.salesblink.io/mcp
Other tools on this server
- signup
- get_all_lists
- create_list
- get_list
- update_list
- get_all_templates
- create_template
- get_template
- update_template
- get_inbox_threads
- get_thread_messages
- send_reply
- forward_inbox_message
- update_mail_state
- get_all_sequences
- create_sequence
- get_sequence
- update_sequence
- get_sequence_stats
- get_all_users
- add_user
- get_user
- update_user
- generate_login_link
- get_all_senders
- get_all_folders
- add_contacts
- remove_contact
- get_sent_activity
- get_opens_activity
- get_clicks_activity
- get_replies_activity
- archive_list
- archive_template
- archive_sequence
- archive_contact
- get_leads
- update_lead
- move_lead
- get_all_workspaces
- update_workspace
- clone_sequence
- get_inbox_placement_tests
- create_inbox_placement_test
- pause_inbox_placement_test
- delete_inbox_placement_test
- get_reports
- create_folder
- get_warmup_links
- get_sender_connect_link
- get_bulk_senders_upload_link
- initialize_google_oauth
- initialize_outlook_oauth
- get_custom_domains
- get_signatures
- get_api_keys
- get_api_key_page_link
- get_api_key_refresh_link
- delete_api_key
- update_sender
- get_add_card_login_link
- get_remove_card_login_link
- get_analytics_overall
- get_analytics_daily
- get_analytics_lead_stats
- get_analytics_mailbox_stats
- reconnect_sender
- get_sender_health
- get_sender_warmup_stats
- fetch_sender_messages
- fetch_multiple_sender_messages
- get_sequence_leads
- unsubscribe_lead_from_sequence
- unsubscribe_lead_globally
- get_lead_messages
- export_sequence_leads
- update_sequence_status
- get_lead_activity_by_id
- get_lead_activity_by_email
- get_blocklist
- add_to_blocklist
- remove_from_blocklist
- check_blocklist
- delete_blocklist_entry
- verify_account
- list_my_workspaces
- select_workspace
This list was read from the server itself, by connecting to it and calling tools/list on 14 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.