request_pilot_key — PoolParty Main Stage Airtime MCP Tool
request_pilot_key
(request pilot key) is one of 71 tools on the
PoolParty Main Stage Airtime
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call request_pilot_key from your client
- Claude Code PoolParty Main Stage Airtime request_pilot_key run in your project directory
- Claude Desktop PoolParty Main Stage Airtime request_pilot_key ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor PoolParty Main Stage Airtime request_pilot_key ~/.cursor/mcp.json
- VS Code PoolParty Main Stage Airtime request_pilot_key .vscode/mcp.json
- Zed PoolParty Main Stage Airtime request_pilot_key ~/.config/zed/settings.json
- Windsurf PoolParty Main Stage Airtime request_pilot_key ~/.codeium/windsurf/mcp_config.json
- Cline PoolParty Main Stage Airtime request_pilot_key ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI PoolParty Main Stage Airtime request_pilot_key ~/.gemini/settings.json
- Grok PoolParty Main Stage Airtime request_pilot_key .mcp.json (in your project root)
- ChatGPT PoolParty Main Stage Airtime request_pilot_key Settings → Connectors → Advanced → Developer mode
- Claude.ai PoolParty Main Stage Airtime request_pilot_key Settings → Connectors → Add custom connector
- LangChain PoolParty Main Stage Airtime request_pilot_key pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http main-stage-airtime https://www.poolparty.io/api/mcpOther tools on this server
- list_program_modes
- get_program_mode_manifest
- list_block_types
- get_block_type_schema
- draft_slide_block_from_project
- preview_slide_block
- revise_slide_block
- list_channel_templates
- preview_channel_template
- resolve_channel
- get_superblock_offerings
- get_collateral_opportunity
- claim_test_pol
- claim_test_collateral
- prepare_block_mint
- finalize_block_mint
- get_block_mint_status
- pool_block
- finalize_pool_support
- withdraw_pool_support
- get_wallet_pooling_state
- get_pooling_receipt
- get_block_economics
- get_sim_signer_access
- get_distribution_report
- get_channel_metrics
- get_airtime_opportunity
- get_platform_pulse
- browse_channels
- get_channel_stream
- get_channel_feed
- get_open_submission_calls
- get_reward_opportunities
- get_sponsor_opportunities
- list_programming_scope_profiles
- check_key_request_status
- get_key_info
- complete_sim_pool_back
- create_join_session
- attach_wallet_to_session
- request_media_upload_url
- complete_media_upload
- submit_media_block
- prepare_superblock_purchase
- quote_superblock_reservation
- quote_sponsor_reservation
- settle_paid_action
- get_paid_action_receipt
- create_channel_from_template
- update_channel_settings
- configure_open_call
- list_programming_candidates
- preview_programming_candidate
- inspect_programming_discovery_inventory
- admit_programming_candidates
- list_program_queue
- list_programming_buckets
- list_live_queue
- inspect_channel_programming_policy
- create_program_item
- draft_program_queue
- set_programming_bucket
- reorder_program_queue
- simulate_program_queue_publish
- publish_program_queue
- insert_live_next
- remove_live_queue_item
- skip_current_live_item
- propose_program_order
- accept_programming_proposal
This list was read from the server itself, by connecting to it and calling tools/list on 24 September 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.