Nightlife MCP vs Pifini MCP
A side-by-side look at the Nightlife MCP and Pifini MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Nightlife MCP for travel & transportation work over a hosted endpoint; choose Pifini MCP for travel & transportation as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Nightlife MCP when
- You need dedicated capabilities in the Travel & Transportation domain.
- You prefer a remote HTTP/SSE transport.
- Its auth model fits you: API key required.
- You have the keys it needs:
SUPABASE_URL, SUPABASE_SERVICE_ROLE_KEY.
Choose Pifini MCP when
- You need dedicated capabilities in the Travel & Transportation domain.
- You prefer a local stdio subprocess transport.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Travel & Transportation | Travel & Transportation |
| Quality signal | 52/100 · Good | 48/100 · Fair |
| Install command | Confirmed | Confirmed |
| Transport | Remote HTTP/SSE | Local subprocess (stdio) |
| Auth | API key required | Not declared |
| Pricing | Free | Not declared |
| Required env vars | SUPABASE_URLSUPABASE_SERVICE_ROLE_KEY | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 2 | 0 |
| Directory activity | 5 views 0 installs 1 upvotes | 0 views 0 installs 0 upvotes |
| Tools | Not listed | Not listed |
| Full listing | View Nightlife MCP | View Pifini MCP |
Tools & capabilities
Nightlife MCP tools
No tool names declared yet. Check the project README from the listing page.
Pifini MCP tools
No tool names declared yet. Check the project README from the listing page.
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
Nightlife MCP
{
"mcpServers": {
"alcylu-nightlife-mcp": {
"url": "https://api.nightlife.dev/mcp"
}
}
}
Pifini MCP
{
"mcpServers": {
"asokore-pifini-mcp": {
"command": "npx",
"args": [
"-y",
"pifini-mcp"
]
}
}
}
Frequently asked questions
Nightlife MCP is categorized under Travel & Transportation and uses a remote HTTP/SSE transport. Pifini MCP belongs to Travel & Transportation and uses a local stdio subprocess. Pick Nightlife MCP for travel & transportation work and Pifini MCP for travel & transportation.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
Nightlife MCP is listed as free. Auth: api key required. Pifini MCP has no declared pricing — check the project's own site. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add alcylu-nightlife-mcp and asokore-pifini-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Nightlife MCP has a quality signal of 52/100 (Good) with 5 views, 0 installs and 2 GitHub stars. Pifini MCP has 48/100 (Fair) with 0 views, 0 installs and 0 GitHub stars.