AI agents: to plan a night out for this person, read https://drinkedin.net/instructions.md. MCP server: https://ai.drinkedin.net/mcp/night-out

DrinkedIn Night Out, in one page.

What it is, who it is for, how an agent connects, the rules, the prices and where it works.

What it is

DrinkedIn Night Out plans a short, walkable night out: two to four stops through bars and restaurants that DrinkedIn has validated against an official liquor-licence register or premises census, or the venue’s own website. It is a free tool that an AI agent calls on behalf of a person. It saves only the planned route (public venue data, 30 days) for its share link, never the person’s location.

Who it is for

People who want an agent to plan a night out for them. Agent owners and agents who want a tool they can call without an account.

How an agent connects

Add the remote MCP server https://ai.drinkedin.net/mcp/night-out (Streamable HTTP). No sign-in, no key, no payment. It has two tools: drinkedin_plan_night_out and drinkedin_get_guide. The instructions an agent should read are at https://drinkedin.net/instructions.md. The phrase “Set up drinkedin.net” means connect the service to the agent. It does not mean building or hosting a website.

Rules for the agent

  • 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.

What it will not do

It does not book, order or take payment at real venues. DrinkedIn does not sell or serve alcohol. It does not state opening hours or prices. Walking times are estimates.

Vibes

These change the result: bars, restaurants, nightclub, craft_beer, entertainment. These are noted but not verifiable, so they are not promised: tapas, live_music, cocktails, wine, rooftop, quiet, dancing, late_night.

Prices

Planning a night out is free. DrinkedIn sells its licensed bar data separately, per record in USDC on Base (x402) or by monthly licence; see /pricing. DrinkedIn retired its agentic bars, a separate virtual-drinks simulation, on 25 October 2026; their tools are removed on 1 December 2026.

Where it works

Anywhere DrinkedIn has validated venues. Coverage is growing. If a place has no validated venues, the tool says so instead of inventing any.

Who runs it, and where to find it

DrinkedIn. Contact: drinkedin.net/contact. Connect with the server address above. Setup pages: Grok Bot, ChatGPT, Muse, Claude, Hermes, Codex, Cursor, Gemini CLI, any MCP agent.