Koskamo

PourWire MCP

An official MCP server by PourWire that provides AI assistants with real-time data on upcoming restaurant and bar openings in 11 US metros. It exposes tools to search for pre-opening signals based on liquor license and building permit filings, and to retrieve summary statistics for specific metropolitan areas, supporting trade users in identifying new venues before they open.

Endpoint and access

No sign-in to connect and list tools. Individual tools may still need a vendor account, credentials, or permissions; check the documented prerequisites.

PourWire MCP logo, by PourWireVendor evidenceStreamable HTTPNo sign-inEndpoint checked 2026-11-01Operated by PourWire
MCP endpoint (Streamable HTTP)
https://pourwire.com/mcp
Vendor documentation

What you can do with it

  • Search for upcoming restaurant openings in a specific metro area
  • Retrieve summary statistics for tracked venues in a metro
  • Identify new liquor license filings for market intelligence
  • Access pre-opening signals for hospitality trade outreach

Source and maintenance

Vendor evidenceRegistry 1.0.2

Protocol and capabilities

Server
pourwire 1.0.0
MCP protocol
2025-06-18
Tools
2 advertised
Resources
Not advertised
Resource templates
Not advertised
Prompts
Not advertised
Server-advertised capabilities
{
  "tools": {}
}

Tools

2 advertised

search_openings — Search upcoming restaurant and bar openings
Advertised by the server during the last successful anonymous check.
Advertised read-onlyOpen-world

Search upcoming restaurant/bar openings in a metro (pre-opening signals from liquor license & permit filings). Returns venues with estimated opening window, owner and evidence trail. Without an API key: the public tier (every filing, block-level address, no owner contacts), each with a link to its page.

search_openings input schema
{
  "type": "object",
  "required": [
    "metro"
  ],
  "properties": {
    "limit": {
      "type": "integer",
      "default": 20
    },
    "metro": {
      "enum": [
        "los-angeles",
        "new-york",
        "westchester",
        "long-island",
        "austin",
        "waco-temple",
        "dallas-fort-worth",
        "houston",
        "san-antonio",
        "phoenix",
        "chicago-suburbs"
      ],
      "type": "string"
    },
    "status": {
      "enum": [
        "new",
        "in_buildout",
        "approved",
        "opened"
      ],
      "type": "string"
    }
  }
}
search_openings annotations
{
  "title": "Search upcoming restaurant and bar openings",
  "readOnlyHint": true,
  "openWorldHint": true
}
metro_stats — Metro opening stats
Advertised by the server during the last successful anonymous check.
Advertised read-onlyOpen-world

Summary stats for a metro: tracked venues, new this week, sources.

metro_stats input schema
{
  "type": "object",
  "required": [
    "metro"
  ],
  "properties": {
    "metro": {
      "enum": [
        "los-angeles",
        "new-york",
        "westchester",
        "long-island",
        "austin",
        "waco-temple",
        "dallas-fort-worth",
        "houston",
        "san-antonio",
        "phoenix",
        "chicago-suburbs"
      ],
      "type": "string"
    }
  }
}
metro_stats annotations
{
  "title": "Metro opening stats",
  "readOnlyHint": true,
  "openWorldHint": true
}

Prompts

Not advertised

No prompt definitions available.

Resources

Not advertised

No resource definitions available.

30-day availability

Aggregated from read-only remote checks; this is not a tool-execution or security guarantee.

Successful checks
1 of 1 (100%)
Average latency
954 ms
95th percentile latency
954 ms

Maintenance history

Public check and source-refresh events. Editorial and ownership records remain private.

  • · probe · passed · 954 ms · metadata changed · 2 tool(s)

Connect from your client

Each snippet registers the same endpoint; pick the client you use.

This server is operated by the named third party. Listing and endpoint checks are not an endorsement or a security audit. Review the operator's permissions, terms, and data handling before connecting. How listings are checked and corrected.

Claude Code

Run this once in a terminal. It registers the remote server. Use --scope project to write .mcp.json for the repo.
Claude Code configuration
claude mcp add --transport http pourwire-mcp https://pourwire.com/mcp

Codex

Run this once. Codex stores MCP servers in ~/.codex/config.toml (or .codex/config.toml in a trusted project).
Codex configuration
codex mcp add pourwire-mcp --url https://pourwire.com/mcp

Cursor

Merge this server into .cursor/mcp.json in your project, then enable pourwire-mcp in your MCP settings.
Cursor configuration
{
  "mcpServers": {
    "pourwire-mcp": {
      "url": "https://pourwire.com/mcp"
    }
  }
}

Cline

Merge this into cline_mcp_settings.json (Cline → MCP Servers → Configure).
Cline configuration
{
  "mcpServers": {
    "pourwire-mcp": {
      "type": "streamableHttp",
      "url": "https://pourwire.com/mcp",
      "disabled": false
    }
  }
}

VS Code

Merge this server into .vscode/mcp.json. Use MCP: List Servers to start pourwire-mcp and inspect its tools.
VS Code configuration
{
  "servers": {
    "pourwire-mcp": {
      "type": "http",
      "url": "https://pourwire.com/mcp"
    }
  }
}

Gemini CLI

Run this once. It writes .gemini/settings.json in the current project; pass --scope user for ~/.gemini/settings.json.
Gemini CLI configuration
gemini mcp add --transport http pourwire-mcp https://pourwire.com/mcp

Claude Desktop

Merge this into claude_desktop_config.json (macOS: ~/Library/Application Support/Claude/, Windows: %APPDATA%\Claude\), then restart Claude Desktop.
Claude Desktop configuration
{
  "mcpServers": {
    "pourwire-mcp": {
      "url": "https://pourwire.com/mcp"
    }
  }
}

Windsurf

Merge this into ~/.codeium/windsurf/mcp_config.json, then refresh MCP in Cascade. Windsurf remote servers use serverUrl, not url.
Windsurf configuration
{
  "mcpServers": {
    "pourwire-mcp": {
      "serverUrl": "https://pourwire.com/mcp"
    }
  }
}

Let your agent find its tools

Find servers like PourWire MCP from your agent. Add Koskamo once to search the index for endpoints, access requirements, and client setup. Public discovery needs no key.

Do you run PourWire MCP?

Prove ownership with a DNS record, a well-known file, or your Official MCP Registry entry, and your edits publish immediately. Proofs are re-checked weekly; admins can still hide or remove a listing.

Claim this listing