get_feature_requests — QuailOS MCP Tool Read-only
get_feature_requests
(get feature requests) is one of 102 tools on the
QuailOS
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call get_feature_requests from your client
- Claude Code QuailOS get_feature_requests run in your project directory
- Claude Desktop QuailOS get_feature_requests ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor QuailOS get_feature_requests ~/.cursor/mcp.json
- VS Code QuailOS get_feature_requests .vscode/mcp.json
- Zed QuailOS get_feature_requests ~/.config/zed/settings.json
- Windsurf QuailOS get_feature_requests ~/.codeium/windsurf/mcp_config.json
- Cline QuailOS get_feature_requests ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI QuailOS get_feature_requests ~/.gemini/settings.json
- Grok QuailOS get_feature_requests .mcp.json (in your project root)
- ChatGPT QuailOS get_feature_requests Settings → Connectors → Advanced → Developer mode
- Claude.ai QuailOS get_feature_requests Settings → Connectors → Add custom connector
- LangChain QuailOS get_feature_requests pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http quailos https://www.quailos.com/api/mcp/message
Other tools on this server
- plan_flock
- start_signup
- update_order_notes
- list_vehicles
- get_support_tickets
- create_support_ticket
- reply_to_ticket
- create_feature_request
- get_ticket_thread
- get_hatches
- log_hatch_set
- log_candling
- log_hatch_result
- log_hive_inspection
- log_varroa_treatment
- log_honey_harvest
- update_queen_status
- create_hive
- ping
- get_npip_stock_codes
- get_public_farms
- get_public_wiki_pages
- list_quail_varieties
- predict_quail_cross
- find_quail_pairings
- get_tasks
- get_calendar_events
- get_orders
- get_order_feedback
- get_customer_details
- get_meat_inventory
- get_beekeeping_apiary
- get_financial_pnl
- get_feed_inventory
- get_vendors_and_pos
- get_egg_collections
- get_mileage_logs
- get_bird_batches
- get_time_logs
- get_transactions
- submit_wiki_article
- create_task
- complete_task
- update_task
- log_time
- log_eggs
- create_customer
- update_customer
- create_sales_order
- create_calendar_event
- log_mileage
- log_feed_purchase
- log_manual_transaction
- log_bird_batch
- merge_bird_batches
- unmerge_bird_batches
- get_production_orders
- create_production_order
- delete_task
- delete_calendar_event
- log_meat
- list_emails
- get_email
- draft_email_reply
- move_email
- send_email
- list_supplier_opportunities
- get_make_money_with_quail_guide
- express_supplier_interest
- create_supplier_shipment
- update_supplier_shipment_tracking
- list_my_supplier_shipments
- create_inventory_product
- update_inventory_product
- adjust_inventory_stock
- complete_production_order
- list_rentahatch_vendors
- get_rentahatch_vendor
- list_rentahatch_waitlist
- update_rentahatch_waitlist_status
- list_rentahatch_bookings
- list_rentahatch_payouts
- set_rentahatch_listing_active
- update_rentahatch_payout_status
- activate_rentahatch_booking
- list_farm_notes
- get_farm_note
- create_farm_note
- update_farm_note
- delete_farm_note
- list_farm_times_headlines
- list_farm_times_articles
- get_farm_times_article
- list_quailos_tv
- get_quailos_tv
- list_academy_courses
- get_academy_course
- list_my_academy_enrollments
- enroll_academy_course
- list_library_items
- get_library_item
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.