amego_query_invoice — amego MCP by usefulapi MCP Tool
amego_query_invoice
(amego query invoice) is one of 13 tools on the
amego MCP by usefulapi
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call amego_query_invoice from your client
- Claude Code amego MCP by usefulapi amego_query_invoice run in your project directory
- Claude Desktop amego MCP by usefulapi amego_query_invoice ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor amego MCP by usefulapi amego_query_invoice ~/.cursor/mcp.json
- VS Code amego MCP by usefulapi amego_query_invoice .vscode/mcp.json
- Zed amego MCP by usefulapi amego_query_invoice ~/.config/zed/settings.json
- Windsurf amego MCP by usefulapi amego_query_invoice ~/.codeium/windsurf/mcp_config.json
- Cline amego MCP by usefulapi amego_query_invoice ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI amego MCP by usefulapi amego_query_invoice ~/.gemini/settings.json
- Grok amego MCP by usefulapi amego_query_invoice .mcp.json (in your project root)
- ChatGPT amego MCP by usefulapi amego_query_invoice Settings → Connectors → Advanced → Developer mode
- Claude.ai amego MCP by usefulapi amego_query_invoice Settings → Connectors → Add custom connector
- LangChain amego MCP by usefulapi amego_query_invoice pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http amego https://amego.usefulapi.io/mcp
Other tools on this server
- amego_list_invoices
- amego_get_invoice_upload_status
- amego_get_invoice_file
- amego_check_lottery_invoices
- amego_get_track_status
- amego_list_track_ranges
- amego_query_allowance
- amego_list_allowances
- amego_get_allowance_upload_status
- amego_get_allowance_file
- amego_lookup_company_name
- amego_check_mobile_barcode
This list was read from the server itself, by connecting to it and calling tools/list on 8 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.