edesk_get_ticket — eDesk MCP by usefulapi MCP Tool
edesk_get_ticket
(edesk get ticket) is one of 18 tools on the
eDesk MCP by usefulapi
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call edesk_get_ticket from your client
- Claude Code eDesk MCP by usefulapi edesk_get_ticket run in your project directory
- Claude Desktop eDesk MCP by usefulapi edesk_get_ticket ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor eDesk MCP by usefulapi edesk_get_ticket ~/.cursor/mcp.json
- VS Code eDesk MCP by usefulapi edesk_get_ticket .vscode/mcp.json
- Zed eDesk MCP by usefulapi edesk_get_ticket ~/.config/zed/settings.json
- Windsurf eDesk MCP by usefulapi edesk_get_ticket ~/.codeium/windsurf/mcp_config.json
- Cline eDesk MCP by usefulapi edesk_get_ticket ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI eDesk MCP by usefulapi edesk_get_ticket ~/.gemini/settings.json
- Grok eDesk MCP by usefulapi edesk_get_ticket .mcp.json (in your project root)
- ChatGPT eDesk MCP by usefulapi edesk_get_ticket Settings → Connectors → Advanced → Developer mode
- Claude.ai eDesk MCP by usefulapi edesk_get_ticket Settings → Connectors → Add custom connector
- LangChain eDesk MCP by usefulapi edesk_get_ticket pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http edesk https://edesk.usefulapi.io/mcp
Other tools on this server
- edesk_whoami
- edesk_list_users
- edesk_list_channels
- edesk_list_tag_groups
- edesk_list_tags
- edesk_list_templates
- edesk_get_template
- edesk_list_tickets
- edesk_get_message
- edesk_list_contacts
- edesk_list_sales_orders
- edesk_get_sales_order
- edesk_list_order_notes
- edesk_update_ticket
- edesk_add_ticket_note
- edesk_reply_to_ticket
- edesk_add_order_note
This list was read from the server itself, by connecting to it and calling tools/list on 14 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.