ingest_url_data_source — clariBI MCP Tool
ingest_url_data_source
(ingest url data source) is one of 26 tools on the
clariBI
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call ingest_url_data_source from your client
- Claude Code clariBI ingest_url_data_source run in your project directory
- Claude Desktop clariBI ingest_url_data_source ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor clariBI ingest_url_data_source ~/.cursor/mcp.json
- VS Code clariBI ingest_url_data_source .vscode/mcp.json
- Zed clariBI ingest_url_data_source ~/.config/zed/settings.json
- Windsurf clariBI ingest_url_data_source ~/.codeium/windsurf/mcp_config.json
- Cline clariBI ingest_url_data_source ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI clariBI ingest_url_data_source ~/.gemini/settings.json
- Grok clariBI ingest_url_data_source .mcp.json (in your project root)
- ChatGPT clariBI ingest_url_data_source Settings → Connectors → Advanced → Developer mode
- Claude.ai clariBI ingest_url_data_source Settings → Connectors → Add custom connector
- LangChain clariBI ingest_url_data_source pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http mcp-server https://claribi.com/mcp/v1/Other tools on this server
- check_integration_status
- check_pricing
- create_checkout_session
- create_forecast
- generate_report
- get_analysis_status
- get_billing_status
- get_dashboard
- get_data_source_schema
- get_forecast
- get_forecast_run
- get_forecast_trust
- get_report
- get_usage
- list_dashboards
- list_data_sources
- list_forecasts
- list_reports
- regenerate_forecast_narrative
- register_account
- request_oauth_integration_url
- run_analysis
- run_forecast
- upload_data_source
- verify_email
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.