Credentials. The first search asks you to sign in at Syncso.com, so keep the sign-in code private and do not paste it into shared logs or chats.
Who it is forA developer who works in Claude Code and wants the agent to look up New York events while planning a trip, a demo or a team outing.
The problemClaude Code has no access to current local event listings, so any event lookup from it is out of date or invented.
The outcomeClaude Code can call find_things_to_do and get_details against SyncSo and report real listings with booking links.
What you need first
- An account at syncso.com, with a sign-in code from syncso.com/connect when the first search asks for it
- An MCP-capable assistant (Claude, ChatGPT developer mode, Cursor, Windsurf, VS Code or another MCP client), or an agent that can read a skill file and make HTTPS requests
- Interest in New York, since SyncSo covers New York only for now
Steps
- Open a terminal where Claude Code is installed.
- Run
claude mcp add --transport http syncso https://rtdb.syncso.com/partner/mcp. - Start Claude Code and ask for New York events for a specific day.
- Complete the one-time sign-in at Syncso.com when the first search asks for it.
- Ask for details on one result with get_details and confirm the booking link resolves.
Prompt for your agent
In Claude Code, with the SyncSo MCP server from SyncSo-Inc/syncso connected, search for live music events in New York on <date> and list the top three with time, price, and booking link. Verify each result by calling get_details on it before you report it.
Caveat. The README documents a single MCP URL and only two tools, so do not assume other endpoints or features exist.
Get 5 new use cases every morning. Free, one short email, unsubscribe anytime.
Get them freeShare: X LinkedIn Hacker News Email Copy link
Disclaimer
Deduped lists open-source repositories that belong to other people. We do not own, maintain, audit, or vouch for any of them, and a repo appearing here is not an endorsement or a safety check. The use cases, steps, and prompts are written by AI and may be incomplete, outdated, or just wrong. Where a use case is marked "Seen in the wild", we link to public posts where someone described something similar, but we have not verified those posts and the use case itself is still our AI's own write-up. Use all of this at your own risk. Only run code, commands, or agents on systems and accounts you are authorized to use, and read the code and every command before you run it, especially anything that touches credentials, files, or the network. Nothing here is professional, security, legal, or financial advice. All trademarks and project names belong to their respective owners, and their use here does not imply affiliation. Content is provided as is, without warranties of any kind. Found a mistake, a safety problem, or something you want removed? Email [email protected] and we will look at it promptly. Full disclaimer page