How to build a connector for Meta Muse
Using a court-booking example, the post shows how to write a connector with Claude Code or Codex and lists four edge cases to test before submitting for review.
What do you need to build a connector for Meta's Muse? Start with one thing that the customer must be able to do. For a pickle ball court app, I would start with this request: "show me the available courts near me tomorrow evening." Each court also has a price. Give that request and the API documentation to Claude Code or Codex. Tell it to make the availability check and the quote first. The quote must show the full price and how long that price is valid. In the app store era, a high-quality mobile app needed $1–2M and a team of 10 people. Now anyone who watches this can do it. Meta must approve each connector, and I think it will reject a service that fails on difficult requests. Before you send yours for review, do these 4 tests: - Ask for a time that is already booked. - Use a quote after its time limit. - Send the same request two times. Make sure that you get only one reservation. - Move a booking to a different day. Then examine the results yourself before customers use it.
This post quotes another post: x.com/startupideaspod/status/2103206860279206047