export_model — DataSnack MCP Tool Read-only

export_model (export model) is one of 18 tools on the DataSnack MCP server. Connect the server and your client discovers it on the handshake.

by client

How to call export_model from your client

Claude Code DataSnack export_model run in your project directory
Claude Desktop DataSnack export_model ~/Library/Application Support/Claude/claude_desktop_config.json
Cursor DataSnack export_model ~/.cursor/mcp.json
VS Code DataSnack export_model .vscode/mcp.json
Zed DataSnack export_model ~/.config/zed/settings.json
Windsurf DataSnack export_model ~/.codeium/windsurf/mcp_config.json
Cline DataSnack export_model ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
Gemini CLI DataSnack export_model ~/.gemini/settings.json
Grok DataSnack export_model .mcp.json (in your project root)
ChatGPT DataSnack export_model Settings → Connectors → Advanced → Developer mode
Claude.ai DataSnack export_model Settings → Connectors → Add custom connector
LangChain DataSnack export_model pip install langchain-mcp-adapters

Fastest route

claude mcp add --transport http datasnack https://datasnack.ai/mcp

Other tools on this server

search_models
get_model
overnight
scoreboard
calibration
get_reference_workbook
get_me
list_library
follow_model
unfollow_model
list_notices
cover_status
cover_market
export_options
get_export
list_exports
start_checkout

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.

DataSnack MCP server