cakto_order_bumps_get — Cakto MCP Tool
cakto_order_bumps_get
(cakto order bumps get) is one of 27 tools on the
Cakto
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call cakto_order_bumps_get from your client
- Claude Code Cakto cakto_order_bumps_get run in your project directory
- Claude Desktop Cakto cakto_order_bumps_get ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Cakto cakto_order_bumps_get ~/.cursor/mcp.json
- VS Code Cakto cakto_order_bumps_get .vscode/mcp.json
- Zed Cakto cakto_order_bumps_get ~/.config/zed/settings.json
- Windsurf Cakto cakto_order_bumps_get ~/.codeium/windsurf/mcp_config.json
- Cline Cakto cakto_order_bumps_get ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Cakto cakto_order_bumps_get ~/.gemini/settings.json
- Grok Cakto cakto_order_bumps_get .mcp.json (in your project root)
- ChatGPT Cakto cakto_order_bumps_get Settings → Connectors → Advanced → Developer mode
- Claude.ai Cakto cakto_order_bumps_get Settings → Connectors → Add custom connector
- LangChain Cakto cakto_order_bumps_get pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http cakto-mcp https://api.mcp.ai/p_caktoOther tools on this server
- cakto_list_accounts
- cakto_orders_list
- cakto_orders_get
- cakto_orders_analytics
- cakto_subscriptions_list
- cakto_subscriptions_get
- cakto_subscription_churn
- cakto_customers_list
- cakto_customers_get
- cakto_products
- cakto_products_create
- cakto_products_update
- cakto_offers_list
- cakto_offers_get
- cakto_offers_create
- cakto_offers_update
- cakto_order_bumps_list
- cakto_order_bumps_create
- cakto_order_bumps_update
- cakto_order_bumps_reorder
- 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.