FunNow

Dining & Spontaneous Bookings

Discover your next great meal with FunNow. Whether you are planning a special event or need a table right now, FunNow makes it easy to find and book restaurants tailored to your specific needs across Asia's top culinary destinations.

What you can ask

I need a romantic restaurant in Robertson Quay for a date this Saturday.
Example path →

MCP connector

Server URL: https://openai-mcp-app.myfunnow.com/mcp
Login: None
Protocol: MCP 2025-11-25
Instructions: FunNow restaurant booking server. Tools: (discovery), (confirmed slot queries).
TOOL SEQUENCE: Read the exact branch_name, bid, brand, and product_ids from booking_refs in a prior result when available. Match the selected branch_name exactly; never substitute another branch with a similar name. Pass bid alone to query all products under a branch, or pass selected IDs as product_ids to target specific products. If neither identifier is available, still call with the known booking details; follow its needs_restaurant_search handoff, call , and then retry with the returned identifier.
CROSS-TOOL MEMORY: Once has run, reuse its bid/product_ids for follow-up availability queries — do not call again for the same restaurants.
BOOKING CONTINUATION: If the assistant asks for missing reservation details and the user replies with a terse value such as "2 people, 19:00", resolve the restaurant, date, brand, and bid from conversation context and call . Do not require the user to repeat the restaurant name or booking intent.
SEARCH-TIME AVAILABILITY: does not expose exact available times. Questions about specific times, changed party size or booking criteria, or fresh availability require a call.

Tools

Reads data2

Skills

None in the store listings or on the server

What you can ask

I need a romantic restaurant in Robertson Quay for a date this Saturday.

Example path →

MCP connector

Server URL

https://openai-mcp-app.myfunnow.com/mcp

None

Protocol

MCP 2025-11-25

Instructions

FunNow restaurant booking server. Tools: (discovery), (confirmed slot queries).

TOOL SEQUENCE: Read the exact branch_name, bid, brand, and product_ids from booking_refs in a prior result when available. Match the selected branch_name exactly; never substitute another branch with a similar name. Pass bid alone to query all products under a branch, or pass selected IDs as product_ids to target specific products. If neither identifier is available, still call with the known booking details; follow its needs_restaurant_search handoff, call , and then retry with the returned identifier.

CROSS-TOOL MEMORY: Once has run, reuse its bid/product_ids for follow-up availability queries — do not call again for the same restaurants.

BOOKING CONTINUATION: If the assistant asks for missing reservation details and the user replies with a terse value such as "2 people, 19:00", resolve the restaurant, date, brand, and bid from conversation context and call . Do not require the user to repeat the restaurant name or booking intent.

SEARCH-TIME AVAILABILITY: does not expose exact available times. Questions about specific times, changed party size or booking criteria, or fresh availability require a call.