DrinkedIn Night Out

io.github.haim-baradPublished by GitHub account haim-baradv1.1.0Updated Oct 29, 2026

Plans walkable 2-4 stop nights out between officially validated venues. No sign-in.

VerifiedStreamable HTTPWeb executableLocation & LifestyleProductivity & Workflow

Overview

AI-generated overview

Plans walkable 2-4 stop nights out between venues validated against official registers or their own sites, and returns a shareable route link.

What you can do
  • Plan a night out: build a walkable 2-4 stop route near a point, address or place, with optional style, stop count and maximum walking distance.
  • Read the guide: learn how to call the planner, which vibes and route styles are supported, and the rules for relaying a plan.
  • Share routes: planned or partial routes come with a link to a page showing stops, walks and a map.
When to use it
Useful when someone wants a bar crawl, craft beer crawl, dinner-and-drinks or club night planned around a specific place, and prefers venues checked against official registers or their own websites. It is a planning aid only, not a booking or ranking service.
Requirements
A remote Streamable HTTP endpoint; no account, API key or environment variable is needed. The client must support Streamable HTTP MCP servers. Typed addresses are geocoded through OpenStreetMap Nominatim, so network access to the service is required.
Before you install
Typed addresses are sent to OpenStreetMap Nominatim for geocoding. Planned routes are stored for 30 days so share links work; the server states it keeps only public venue data and never the user's coordinates, address, IP or client details. Walking times are estimates, hours and prices are not asserted, and nothing is booked or paid for. Alcohol is for legal drinking age only.

Installation

In SourceWeft

  1. Open DrinkedIn Night Out in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.haim-barad%2Fdrinkedin-night-out/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "drinkedin-night-out": {
      "type": "http",
      "url": "https://ai.drinkedin.net/mcp/night-out"
    }
  }
}

README

DrinkedIn Night Out

This plugin connects Claude Code to the DrinkedIn Night Out MCP server at https://ai.drinkedin.net/mcp/night-out (Streamable HTTP). The server is free and needs no account or key. It books and buys nothing. The one thing it saves is a planned route, so the route's share link works (see Plan links below); it never saves your location.

Install (Claude Code)

/plugin marketplace add haim-barad/drinkedin-night-out/plugin install drinkedin-night-out@drinkedin

Install (Cursor)

Install DrinkedIn Night Out from the Cursor marketplace, or add the server to your mcp.json:

json
{ "mcpServers": { "drinkedin-night-out": { "url": "https://ai.drinkedin.net/mcp/night-out" } } }

Install (Gemini CLI)

gemini extensions install https://github.com/haim-barad/drinkedin-night-out

Any other MCP client

Streamable HTTP, no auth: https://ai.drinkedin.net/mcp/night-out

What it does

Ask for a night out near a place. The planner builds a walkable route of 2 to 4 stops. Every venue on the route has been validated against an official liquor-licence register or premises census, or the venue's own website.

There are two tools:

  • drinkedin_plan_night_out plans the route and saves it for its share link (public venue data only, 30 days).
    • Give it latitude and longitude (preferred), a street address or landmark, or a place name with its region or country.
    • Optional: style (bar_crawl, craft_beer_crawl, dinner_and_drinks, club_night), stops (2 to 4) and max_walk_m (200 to 2000).
  • drinkedin_get_guide explains how to call the planner and the rules for relaying a plan. It is read-only.

Example prompts:

  • "Plan me a night out near Kennedy Plaza in Providence, RI."
  • "Do a bar crawl starting from Kennedy Plaza, Providence, RI."
  • "Dinner and then drinks near Kennedy Plaza, just two stops."

What to expect

  • Statuses: a reply is planned, partial, needs_input, no_coverage or error. The planner works best where coverage is validated. Where coverage is thin it says so instead of padding the route.
  • Estimates: walking times are estimates. Hours and prices are never asserted, so check the venue's own site.
  • Geocoding: a typed address is sent to OpenStreetMap Nominatim to find the point. The reply's geocoded_as shows what it matched.
  • Plan links: a planned or partial route can carry plan_url, a page on drinkedin.net with the stops, the walks and a map that the person may open or share. DrinkedIn keeps that route for 30 days after it was last planned, then deletes it. It keeps only the venues' public data, the walks, the style label, the town the stops share and the dates; never the person's coordinates, typed address, IP address or client details.
  • Age: alcohol is for people of legal drinking age where they are.

Links

Published by Haim Barad. No sponsored placement.

Source: README.md at commit d5ec330

Tools

2

drinkedin_plan_night_out

Plan a night out

Plan a walkable 2-4 stop night out around a place using only venues DrinkedIn has validated against the venue's own site or an official register. Free. Saves the planned route (public venue data only, 30 days) so it can be shared; never saves the user's location. The most reliable input is a point: give latitude and longitude. Choose it from the user's context, never from a default: 'near me' is the user's current location; an area the user names (a neighbourhood or district) is the centre of that area; for a trip the user is planning, look up the destination they name (use its country to pick the right place) and give its coordinates. If the context holds no location, ask the user. With no coordinates, a free-text address or landmark in address also works: it is geocoded to one point and planned like coordinates (coordinates win if both are given). The text is sent to a public geocoding service (OpenStreetMap Nominatim), which ranks matches and does not confirm them: the reply's geocoded_as says what it matched, so confirm that with the person when the text was ambiguous. A place name also works when it identifies one place, so give it with its country or region; a name several places share returns needs_input with labelled choices: pick the one that fits the user's context and call again with its place_key or coordinates. Never guess between choices. Walking times are estimates (straight line x 1.3). Hours and prices are never asserted: tell the user to check with the venue (its own site when the stop has own_site). Say the plan is for adults of legal drinking age where they are; never state an age as a number. If the user says they are under the legal drinking age, do not call this tool. Show only the stops returned and add no venues, details or place names of your own.

Parameterscitynearstopsstylevibesbudgetregionaddresscountrylanguagelatitudelongitude+5 more

drinkedin_get_guide

Night-out guide

How to use the night-out planner: some places with validated venues (not a ranking and not a coverage claim), supported vibes, route styles, and the rules to follow when relaying a plan (validated venues only, no invented details, legal drinking age where they are). Read-only and free.

Takes no parameters.

Version history

2
  1. v1.1.0LatestOct 29, 2026
  2. v1.0.0Oct 23, 2026

Score

100% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listedRequired15 pts
  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts