crm_publish_file — CRM MCP Tool
crm_publish_file
(crm publish file) is one of 36 tools on the
CRM
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call crm_publish_file from your client
- Claude Code CRM crm_publish_file run in your project directory
- Claude Desktop CRM crm_publish_file ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor CRM crm_publish_file ~/.cursor/mcp.json
- VS Code CRM crm_publish_file .vscode/mcp.json
- Zed CRM crm_publish_file ~/.config/zed/settings.json
- Windsurf CRM crm_publish_file ~/.codeium/windsurf/mcp_config.json
- Cline CRM crm_publish_file ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI CRM crm_publish_file ~/.gemini/settings.json
- Grok CRM crm_publish_file .mcp.json (in your project root)
- ChatGPT CRM crm_publish_file Settings → Connectors → Advanced → Developer mode
- Claude.ai CRM crm_publish_file Settings → Connectors → Add custom connector
- LangChain CRM crm_publish_file pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http crm-mcp https://api.mcp.ai/p_crm
Other tools on this server
- crm_describe
- crm_list_objects
- crm_create_records
- crm_list_records
- crm_get_records
- crm_update_records
- crm_delete_records
- crm_search
- crm_define_object
- crm_add_field
- crm_get_object
- crm_update_object
- crm_delete_object
- crm_update_field
- crm_remove_field
- crm_link_record
- crm_unlink_record
- crm_related_records
- crm_move_stage
- crm_upload_file
- crm_confirm_upload
- crm_upload_from_url
- crm_list_files
- crm_get_file
- crm_download_file
- crm_delete_file
- crm_unpublish_file
- crm_usage
- crm_list_accounts
- show_version
- report_bug
- connect
- toolkit_info
- marketplace
- authenticate
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.