create_checkout_session — clariBI MCP Tool Mutating
create_checkout_session
(create checkout session) 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 create_checkout_session from your client
- Claude Code clariBI create_checkout_session run in your project directory
- Claude Desktop clariBI create_checkout_session ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor clariBI create_checkout_session ~/.cursor/mcp.json
- VS Code clariBI create_checkout_session .vscode/mcp.json
- Zed clariBI create_checkout_session ~/.config/zed/settings.json
- Windsurf clariBI create_checkout_session ~/.codeium/windsurf/mcp_config.json
- Cline clariBI create_checkout_session ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI clariBI create_checkout_session ~/.gemini/settings.json
- Grok clariBI create_checkout_session .mcp.json (in your project root)
- ChatGPT clariBI create_checkout_session Settings → Connectors → Advanced → Developer mode
- Claude.ai clariBI create_checkout_session Settings → Connectors → Add custom connector
- LangChain clariBI create_checkout_session 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_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
- ingest_url_data_source
- 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.