get_checkout_intent — Escrova MCP Tool Read-only

get_checkout_intent (get checkout intent) is one of 18 tools on the Escrova MCP server. Connect the server and your client discovers it on the handshake.

by client

How to call get_checkout_intent from your client

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

Fastest route

claude mcp add --transport http escrova https://www.escrova.io/api/mcp

Other tools on this server

search_products
get_fees
get_prices
get_terms
list_categories
get_category
get_directory
get_deals
auth_challenge
whoami
list_addresses
get_delegation
prepare_checkout
create_listing_draft
update_listing_draft
get_listing_draft
prepare_listing_publish

This list was read from the server itself, by connecting to it and calling tools/list on 11 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.

Escrova MCP server