Pifini MCP

A thin stdio ↔ HTTPS proxy to Pifini's hosted MCP server — real events, reviewed places, and ticket checkout across the Caribbean & Latin America.

If your MCP client supports remote HTTP servers, you don't need this package at all. Connect directly to:

https://pifini.net/api/mcp

That's a stateless Streamable-HTTP endpoint. This package exists only for clients that speak stdio (a local command + JSON-RPC over stdin/stdout) instead. It has no logic of its own — it reads each request from stdin, forwards it verbatim to the hosted endpoint over HTTPS, and writes the response back to stdout. Nothing here is hardcoded, so every method the hosted server supports (initialize, tools/list, tools/call, ...) works automatically without this proxy needing to know what a "tool" even is.

Install

npx pifini-mcp

Or add it to your MCP client's config (Claude Desktop example):

{
  "mcpServers": {
    "pifini": {
      "command": "npx",
      "args": ["-y", "pifini-mcp"]
    }
  }
}

What Pifini's MCP server does

• search_events / get_event — search and read real festivals, carnivals, concerts, and cultural events, strongest coverage in the Caribbean and Latin America.
• search_places / get_place — search reviewed restaurants, bars, venues, attractions, and professionals, including their published reviews.
• create_ticket_checkout — generate a Stripe-hosted payment link for event tickets. The agent hands the link to its human, who completes payment themselves — agents never see card details.

Read tools are open; no API key required. Full documentation, tool schemas, and a live example live at pifini.net/agents.

Why a proxy package exists at all

Pifini's server is closed-source and hosted (it's part of a larger commercial application), so there's no public repository to point an MCP client's stdio launcher at directly. This package is that missing piece: a small, genuinely open-source (MIT), auditable bridge — not a stand-in for real server code, just the stdio transport Pifini's hosted server doesn't speak natively.

It holds no API keys, no database access, and no business logic. Every request it receives is forwarded byte-for-byte to https://pifini.net/api/mcp (or the URL in PIFINI_MCP_URL, if you want to point it somewhere else for testing) and the response is passed back unmodified.

License

MIT — see LICENSE.