Lineup MCP Server

live.alpic.lineup-bf157e35/lineup

answering

Lineup is answering right now. Last checked 6 min ago. It exposes 2 tools.

Turn one sentence into an event pack: event card, identity badges, QR codes, and .ics.

Uptime history 40 hours of history

40 hours agonow

100.0%

Uptime 24h

91 of 91 checks

Tools

read from the server

835 ms

Response time

average over 24h

open, no key

Access

sse

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 6 min ago.

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

claude mcp add lineup --transport http https://lineup-bf157e35.alpic.live

~/Library/Application Support/Claude/claude_desktop_config.json

{
  "mcpServers": {
    "lineup": {
      "url": "https://lineup-bf157e35.alpic.live"
    }
  }
}

~/.codex/config.toml

[mcp_servers.lineup]
url = "https://lineup-bf157e35.alpic.live"

.cursor/mcp.json

{
  "mcpServers": {
    "lineup": {
      "url": "https://lineup-bf157e35.alpic.live"
    }
  }
}

.vscode/mcp.json

{
  "mcpServers": {
    "lineup": {
      "url": "https://lineup-bf157e35.alpic.live"
    }
  }
}

Available tools 2

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

generate

generate-lineup

Generate an event pack: a Luma-style event card with .ics + RSVP QR, and an identity badge per attendee with a deterministic avatar and vCard-encoded QR. Use when the user describes an event and the people attending (meetup, conference, wedding, hackathon, dinner) and wants shareable cards. Do NOT use to render a single downloadable PNG of one badge — use render-badge-png for that. Output is deterministic: the same attendee name + style always yields the same avatar.

render

render-badge-png

Render a single identity badge as a shareable PNG (avatar + name + role + vCard QR) composed with Satori. Use when the user clicks download on one badge, or asks for a single saveable/printable badge image. Do NOT use to build the whole event view — use generate-lineup for that. Match avatarStyle/gender/accentHex to the badge shown in the Lineup so the PNG looks identical.

Endpoints

URL	Transport	State	Latency	Checked
https://lineup-bf157e35.alpic.live	sse	answering	279 ms	6 min ago

Lineup — questions

Answers built from our own checks of this server.

What can Lineup do?

It exposes 2 tools, read directly from the server on our last check. Among them: generate-lineup, render-badge-png. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →

Is Lineup working right now?

We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 835 ms. The bar chart above shows every period we have measured.

How do I connect Lineup?

Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.

Does Lineup need an API key?

No. Lineup completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 2 of them are readable on this page. This is what we observed, not what the docs claim.

How fast is Lineup?

It answers our handshake in 835 ms on average, which is faster than 9% of all working MCP servers we measure. That is on the slow side — worth knowing if the tool sits inside an interactive loop. The comparison comes from our own checks across the whole registry, every 15 minutes.