teamleader_invoice_draft_operation_status — Teamleader Focus MCP by usefulapi MCP Tool
teamleader_invoice_draft_operation_status
(teamleader invoice draft operation status) is one of 38 tools on the
Teamleader Focus MCP by usefulapi
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call teamleader_invoice_draft_operation_status from your client
- Claude Code Teamleader Focus MCP by usefulapi teamleader_invoice_draft_operation_status run in your project directory
- Claude Desktop Teamleader Focus MCP by usefulapi teamleader_invoice_draft_operation_status ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Teamleader Focus MCP by usefulapi teamleader_invoice_draft_operation_status ~/.cursor/mcp.json
- VS Code Teamleader Focus MCP by usefulapi teamleader_invoice_draft_operation_status .vscode/mcp.json
- Zed Teamleader Focus MCP by usefulapi teamleader_invoice_draft_operation_status ~/.config/zed/settings.json
- Windsurf Teamleader Focus MCP by usefulapi teamleader_invoice_draft_operation_status ~/.codeium/windsurf/mcp_config.json
- Cline Teamleader Focus MCP by usefulapi teamleader_invoice_draft_operation_status ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Teamleader Focus MCP by usefulapi teamleader_invoice_draft_operation_status ~/.gemini/settings.json
- Grok Teamleader Focus MCP by usefulapi teamleader_invoice_draft_operation_status .mcp.json (in your project root)
- ChatGPT Teamleader Focus MCP by usefulapi teamleader_invoice_draft_operation_status Settings → Connectors → Advanced → Developer mode
- Claude.ai Teamleader Focus MCP by usefulapi teamleader_invoice_draft_operation_status Settings → Connectors → Add custom connector
- LangChain Teamleader Focus MCP by usefulapi teamleader_invoice_draft_operation_status pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http teamleader-focus https://teamleader-focus.usefulapi.io/mcpOther tools on this server
- teamleader_create_invoice_drafts
- teamleader_get_current_user
- teamleader_list_users
- teamleader_list_contacts
- teamleader_get_contact
- teamleader_list_companies
- teamleader_get_company
- teamleader_list_deals
- teamleader_get_deal
- teamleader_list_deal_pipelines
- teamleader_list_deal_phases
- teamleader_list_invoices
- teamleader_get_invoice
- teamleader_list_projects
- teamleader_list_tasks
- teamleader_list_time_tracking
- teamleader_list_tickets
- teamleader_list_work_types
- teamleader_list_departments
- teamleader_list_products
- teamleader_get_product
- teamleader_list_product_categories
- teamleader_list_quotations
- teamleader_get_quotation
- teamleader_list_activity_types
- teamleader_list_events
- teamleader_list_subscriptions
- teamleader_get_subscription
- teamleader_list_notes
- teamleader_create_contact
- teamleader_create_company
- teamleader_create_deal
- teamleader_create_task
- teamleader_add_note
- teamleader_create_event
- teamleader_complete_task
- teamleader_add_time_tracking
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.