get_payout_setup — DJfindr MCP Tool Read-only
get_payout_setup
(get payout setup) is one of 141 tools on the
DJfindr
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call get_payout_setup from your client
- Claude Code DJfindr get_payout_setup run in your project directory
- Claude Desktop DJfindr get_payout_setup ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor DJfindr get_payout_setup ~/.cursor/mcp.json
- VS Code DJfindr get_payout_setup .vscode/mcp.json
- Zed DJfindr get_payout_setup ~/.config/zed/settings.json
- Windsurf DJfindr get_payout_setup ~/.codeium/windsurf/mcp_config.json
- Cline DJfindr get_payout_setup ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI DJfindr get_payout_setup ~/.gemini/settings.json
- Grok DJfindr get_payout_setup .mcp.json (in your project root)
- ChatGPT DJfindr get_payout_setup Settings → Connectors → Advanced → Developer mode
- Claude.ai DJfindr get_payout_setup Settings → Connectors → Add custom connector
- LangChain DJfindr get_payout_setup pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http djfindr https://mcp.djfindr.com/mcpOther tools on this server
- search_djs
- get_dj
- get_dj_content
- list_reference
- get_reference
- list_locations
- get_location
- book_dj
- get_me
- get_account
- get_account_billing
- list_booking_events
- get_booking_event
- list_booking_proposals
- get_booking_proposal
- get_booking_invitation
- list_pending_reviews
- request_booking
- preview_booking_request
- reject_offer
- withdraw_booking
- request_extension
- cancel_extension
- review_booking
- claim_invitation
- get_booking_overview
- list_booking_clients
- get_booking_client
- list_booking_reviews
- get_review_summary
- get_offer_defaults
- list_document_templates
- get_travel_estimate
- accept_request
- decline_request
- edit_offer
- send_offer
- set_offer_defaults
- add_document
- edit_document
- remove_document
- convert_document
- accept_extension
- decline_extension
- create_sourced_booking
- list_payments
- get_payment
- list_received_payments
- get_received_payment
- get_payout_summary
- list_transfers
- list_paylinks
- get_transfer
- get_paylink
- create_paylink
- send_paylink
- cancel_paylink
- list_calendar_blocks
- list_calendar_events
- get_availability
- get_calendar_days
- get_calendar_feed
- export_calendar
- get_calendar_block
- create_busy_block
- update_busy_block
- delete_busy_block
- restore_busy_block
- skip_busy_occurrence
- create_calendar_feed
- rotate_calendar_feed
- get_profile
- check_handle
- check_dj_link
- update_profile
- set_service_areas
- set_vocabulary
- set_profile_tags
- set_avatar
- set_cover
- change_handle
- claim_dj_link
- release_dj_link
- list_mixes
- get_mix
- list_soundcloud_tracks
- list_posts
- get_post
- list_live_events
- get_live_event
- list_widget_domains
- create_mix
- update_mix
- delete_mix
- reorder_mixes
- import_soundcloud
- create_post
- update_post
- delete_post
- pin_post
- restore_post
- create_live_event
- update_live_event
- delete_live_event
- publish_live_event
- unpublish_live_event
- cancel_live_event
- archive_live_event
- preview_live_event
- add_widget_domain
- remove_widget_domain
- list_conversations
- get_conversation
- list_messages
- start_conversation
- send_message
- mark_conversation_read
- start_multipart_upload
- complete_multipart_upload
- import_file
- abort_multipart_upload
- delete_file
- get_file
- list_integrations
- list_integration_calendars
- choose_integration_calendar
- set_import_busy
- sync_integration
- disconnect_integration
- get_analytics
- search
- whats_next
- get_checkout_link
- get_cancel_link
- get_pay_link
- get_refund_link
- get_upload_link
- get_file_view_link
- get_link
- revoke_link
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.