data_export_collection — shiply MCP Tool
data_export_collection
(data export collection) is one of 114 tools on the
shiply
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call data_export_collection from your client
- Claude Code shiply data_export_collection run in your project directory
- Claude Desktop shiply data_export_collection ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor shiply data_export_collection ~/.cursor/mcp.json
- VS Code shiply data_export_collection .vscode/mcp.json
- Zed shiply data_export_collection ~/.config/zed/settings.json
- Windsurf shiply data_export_collection ~/.codeium/windsurf/mcp_config.json
- Cline shiply data_export_collection ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI shiply data_export_collection ~/.gemini/settings.json
- Grok shiply data_export_collection .mcp.json (in your project root)
- ChatGPT shiply data_export_collection Settings → Connectors → Advanced → Developer mode
- Claude.ai shiply data_export_collection Settings → Connectors → Add custom connector
- LangChain shiply data_export_collection pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http shiply https://shiply.now/mcpOther tools on this server
- publish_site
- site_status
- verify_site
- list_sites
- get_site
- delete_site
- rollback_site
- list_versions
- pull_site
- set_handle
- duplicate_site
- promote_site
- set_link
- set_site_access
- get_site_access
- export_account
- whoami
- get_account_status
- list_drives
- create_drive
- drive_list_files
- drive_put_file
- drive_delete_file
- publish_from_drive
- set_profile
- feature_site
- set_variable
- list_variables
- delete_variable
- attach_variable
- detach_variable
- list_site_variables
- list_databases
- create_database
- delete_database
- attach_database
- data_list_collections
- data_query
- data_insert
- add_domain
- add_custom_domain
- add_subdomain
- set_primary_subdomain
- list_custom_domains
- connect_provider
- sync_dns
- check_custom_domain
- remove_custom_domain
- list_domains
- check_domain
- remove_domain
- get_analytics
- create_test
- list_tests
- get_test_status
- send_broadcast
- resend_confirmation
- verify_claim
- list_inbox
- read_thread
- summarize_thread
- reply_to_thread
- mark_thread_read
- archive_thread
- unarchive_thread
- forward_thread
- list_test_inbox_addresses
- list_unsubscribes
- list_suppressions
- add_suppression
- remove_suppression
- list_complaints
- list_projects
- create_project
- get_project
- update_brief
- regenerate_brief
- archive_project
- restore_project
- list_project_files
- resend_intake_invite
- list_listings
- create_listing
- update_listing
- delete_listing
- list_my_sales
- list_my_orders
- refund_order
- get_connect_status
- list_sending_domains
- add_sending_domain
- verify_sending_domain
- remove_sending_domain
- contract_draft
- contract_send
- contract_amend
- contract_pdf
- contract_status
- deploy_function
- get_function
- remove_function
- set_secret
- list_secrets
- remove_secret
- list_crons
- set_cron
- remove_cron
- get_function_logs
- send_email
- list_site_inbox
- set_mailbox
- list_mailbox_contacts
- send_mailbox_broadcast
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.