Plan a bar crawl with Claude. Free, no sign-in.
Night Out is a free MCP server. Add it to Claude once, then ask for a bar crawl, a pub crawl or a night out, and Claude plans a walkable route through validated venues.
Set it up
Claude on the web and Claude Desktop: custom connector
- Open Customize > Connectors. In Claude on the web or in Claude Desktop, go to Customize > Connectors.
- Add a custom connector. Click Add custom connector and give it a name, for example DrinkedIn Night Out.
- Enter the server URL. Paste the remote MCP server URL:
https://ai.drinkedin.net/mcp/night-out
- Choose No sign in. If Claude asks how people connect, choose No sign in. Night Out needs no account and no OAuth credentials. Click Add.
- Turn it on in a chat. In a conversation, open the + menu, then Connectors, and switch DrinkedIn Night Out on.
Source: Claude: add a connector that isn't in the directory
Claude Code
- Add the server from a terminal. Run this once. --scope user makes it available in every project:
claude mcp add --scope user --transport http drinkedin-night-out https://ai.drinkedin.net/mcp/night-out
- Check it connected. Run claude mcp list in a terminal, or /mcp inside Claude Code. drinkedin-night-out should show as connected.
Source: Claude Code: connect to tools via MCP
The server address
Remote MCP server, Streamable HTTP, no authentication:
https://ai.drinkedin.net/mcp/night-out
Or ask Claude to do it
Say: Set up drinkedin.net
That means connect DrinkedIn’s service to the agent. It does not mean building or hosting a website. An agent that can add servers reads https://drinkedin.net/instructions.md, adds the server and asks where you want to go out.
What you should see
Two tools: drinkedin_plan_night_out and drinkedin_get_guide. If Claude shows neither, the server was not added; check the address above.
Try these prompts
Plan a walkable bar crawl in your neighbourhood starting at 8pm, cocktails then live music.Plan dinner and drinks in your neighbourhood: a restaurant first, then a bar or two a short walk away.Plan a craft beer crawl in your neighbourhood, three stops with short walks between them.
Replace your neighbourhood with the area and town you mean, or ask for somewhere near you if your assistant knows where you are.
What the reply looks like
Plan a walkable bar crawl in your neighbourhood starting at 8pm, cocktails then live music.
Here's a walkable night near your neighbourhood: 3 stops (Corner Cocktail Bar, The Listening Room, Late Room), about 6 minutes of walking between them. I can't verify the cocktails, live music vibe yet, so these stops are chosen by distance and type of place, not by that vibe. This follows the 'Bar crawl' style: Bars and hotel bars only, one after another, with short walks between stops.
Share this plan: https://drinkedin.net/night-out/p/pn_…
Walking times are estimates. Check hours and prices with each venue. For people of legal drinking age where they are.
An illustration of a reply’s shape. The first paragraph and each stop’s line are the tool’s own words for this request; the venue names are placeholders, not real places, and the assistant writes the rest in its own words. What you get depends on the validated venues near the place you give: fewer stops, or a plain answer that there are too few, are possible. Cocktails and live music cannot be verified yet, so the tool says so and plans by distance and type of place.
Share the plan
A planned route comes with a plan link: a page anyone with the link can open, with the route map, the stops, their sources and a directions link. It keeps only the planned route (public venue data) for 30 days after the route was last planned, never your location. How plan links work.
Troubleshooting
Add custom connector is not there
On Team and Enterprise plans only an Owner (or, on Enterprise, a role that manages the organization's libraries) can add a custom connector; ask them to add it, then click Connect under Customize > Connectors. On the Free plan you can add one custom connector.
The connector is added but Claude does not use it
Turn it on for the conversation from the + menu, then Connectors. When Claude asks to use a DrinkedIn tool, allow it.
Claude Code reports the server as failed
Run claude mcp get drinkedin-night-out and check the URL is exactly https://ai.drinkedin.net/mcp/night-out, with no trailing slash. Remove it with claude mcp remove drinkedin-night-out and add it again.
It answers from memory instead of calling the tool
Ask for it by name: “Use DrinkedIn Night Out to plan …”. A reply with no DrinkedIn page links did not come from the tool.
It returns fewer stops, or says there are too few venues
That is the tool's answer, not a fault: there are not enough validated venues close together for that route. Try longer walks, another style, or a nearby area. It does not fill a route with places it has not validated.
It asks which place you mean
Several places share that name. Pick one, or add the region or country.
Rules for Claude
- Show only the venues the tool returns; never add venues, details or place names of your own. Name the area with the person's own words or the town in the stops' addresses, not raw coordinates.
- Never state that a venue is open, or what anything costs. Hours and prices are unverified: tell the person to check with the venue (its own site when the stop has own_site).
- Walking times are estimates. Say so if asked.
- Mention that alcohol is for people of legal drinking age where they are. Never state an age as a number, not even the local one. If the person says they are under that age, do not plan: say so in one sentence, without a lecture, and offer other help.
- Choose the location from the user's context: their current location ('near me'), the area they named (the centre of that area), or the trip they are planning (the destination they name, looked up with its country to pick the right place, then given as coordinates). If the context has no location, ask. Never default to a place, and never guess between places that share a name.
- If the person gives an address or a landmark and you have no coordinates, pass it as address; coordinates win when you have them. A geocoder ranks matches and does not confirm them: tell the person what it matched (geocoded_as), and when the text was ambiguous, such as a bare place name with no country or region, confirm the match with them before relaying the plan.
- If the status is no_coverage, say so honestly. You may offer largest_places as some places with validated venues (not a ranking and not a coverage claim); never call a place covered or best covered. Do not offer to find other venues on the web. If it is needs_input, ask the user for what meaning says is missing or wrong: a place, a choice between places, a different vibe, a different style, or valid coordinates.
- If the person asks for a route shape that matches a style in styles, pass its id as style, and call the plan by that style's name only when the reply carries style_applied. If no listed style matches, plan without one and say so.
- A style names the shape of a route only: it says nothing about hours, prices, atmosphere or events. If too few venues fit a style the status is partial or no_coverage: say so and offer to try without the style; never add other kinds of place yourself.
More: Night Out vs bar-crawl apps · fact sheet · server reference · for agents · for people.