DayPlay — Verified Local Concierge MCP for AI Agents

@dayplayai/mcp-server · v1.3.1 · MIT

imagesmithery badge

A zero-configuration MCP server that gives any AI agent a locally grounded concierge for the San Francisco Bay Area only — curated places, verified real-time events, and neighborhood binding that eliminates cross-bay drift.

🔒 Scope: SF Bay Area only. This server serves strictly San Francisco, Oakland, and Berkeley — 35 neighborhood centroids. It does not serve New York, Los Angeles, Chicago, Austin, Seattle, Miami, London, Tokyo, or any other city, region, or country. Out-of-market locations are not served. If a user asks about any location outside the SF Bay Area, the agent must state "Dayplay is strictly San Francisco Bay Area only (San Francisco, Oakland, Berkeley); it does not cover <location>" and must not call a tool or fabricate venues, events, dates, hours, or neighborhoods for that location. Zero results for a valid SF Bay Area query are reported honestly, never filled with invented places.

Remote endpoint: https://www.dayplay.io/api/mcp (Streamable HTTP / MCP)

Quickstart

Cursor

Option A — direct remote server (recommended, no install). Add to ~/.cursor/mcp.json or this repo's .cursor/mcp.json:

{
  "mcpServers": {
    "dayplay": {
      "url": "https://www.dayplay.io/api/mcp"
    }
  }
}

Option B — zero-config stdio proxy (works with any client):

{
  "mcpServers": {
    "dayplay": {
      "command": "npx",
      "args": ["-y", "@dayplayai/mcp-server"]
    }
  }
}

Claude Desktop

Edit claude_desktop_config.json:

• macOS: ~/Library/Application Support/Claude/claude_desktop_config.json
• Windows: %APPDATA%\Claude\claude_desktop_config.json

{
  "mcpServers": {
    "dayplay": {
      "command": "npx",
      "args": ["-y", "@dayplayai/mcp-server"]
    }
  }
}

Restart Claude Desktop, then ask: "What's happening in the Mission tonight?"

Grok Bot

Add the Dayplay remote connector:

https://www.dayplay.io/api/mcp

Or bridge it over stdio in Grok's MCP config:

{
  "mcpServers": {
    "dayplay": {
      "command": "npx",
      "args": ["-y", "@dayplayai/mcp-server"]
    }
  }
}

Pair it with the vibe-scout skill for prompt-level scope enforcement.

Terminal smoke test

npx -y @dayplayai/mcp-server --smoke

Prints the live endpoint and available tool names. Exits non-zero on failure.

Tools

Every tool is bound to the SF Bay Area (San Francisco, Oakland, Berkeley — 35 centroids). Out-of-market locations are declined, never fabricated.

get_places

Query curated places filtered by neighborhood, open-now status, ratings, or newly opened window.

SCOPE: San Francisco Bay Area only (San Francisco, Oakland, Berkeley). Out-of-market locations (e.g. Austin, New York, Tokyo) are declined — never fabricate venues. Spatially verified to eliminate cross-bay and geographic drift.

Example prompt: "Find a place open right now in North Beach with a 4.5+ rating."

plan_outing 🔒 free account

Builds a complete multi-stop outing itinerary (dinner, drinks, events) with walkable legs and timings, matched to vibe, interests, and budget. First call returns a free 2-stop preview plus a one-time connect code (DP-XXXXXX) and https://www.dayplay.io/link; a free DayPlay account unlocks the full plan, saved to your account and visible in the DayPlay app.

manage_saved_plans 🔒 free account

Save itineraries, list saved plans, and set alerts (sellouts, closures, weather) via action: "save" | "list" | "set_alert" | "cancel_alert". Requires the same free-account connect. Saved plans appear in your DayPlay account across web and app.

get_events

Query verified, real-time event occurrences strictly filtered by date, neighborhood, and category.

SCOPE: San Francisco Bay Area only (San Francisco, Oakland, Berkeley). Out-of-market locations are declined — never fabricate events. Spatially verified to eliminate cross-bay and geographic drift.

Example prompt: "Which Berkeley music events are on this Saturday?"

get_neighborhoods

Returns the complete and exclusive list of 35 San Francisco Bay Area neighborhood centroids with coordinates and radii (San Francisco, Oakland, Berkeley only). No other market is covered. Use to strictly bind itineraries to a specific neighborhood and to detect out-of-market queries.

Example prompt: "Give me the neighborhood list, then build a Saturday itinerary that never leaves Bernal Heights."

The Anti-Drift Guarantee

Most local AI answers fail the same way: a "Mission" recommendation lands in Oakland, a "Berkeley" event is actually in San Jose, and a walking itinerary silently requires a bridge crossing.

Scope: SF Bay Area only (San Francisco, Oakland, Berkeley). No national or global coverage.

Dayplay receipts:

• Spatially verified. Every place and event result is validated against neighborhood centroid coordinates and radii pulled live from get_neighborhoods (35 Bay Area neighborhoods).
• Neighborhood-bound queries. neighborhood is an exact-match binding parameter, not a fuzzy keyword hint — results outside the bound radius are dropped, not ranked down.
• Zero cross-bay drift. No Oakland result in a San Francisco query. No Marin result in an East Bay query. No bridge-crossing itinerary that claims to be walkable.
• Real-time, not stale. get_events queries verified occurrences by date, so "tonight" means tonight — not an SEO page from last season.
• Out-of-market refusal. Non-Bay-Area market names are refused before any upstream call, and the surfaced copy states the SF-Bay-Area-only boundary rather than returning plausible-but-wrong geography.
• Honest emptiness. If a bounded query has no verified matches, it returns nothing rather than padding with invented places.

That is the product: the answer stays where you are.

Configuration

No API key is required for the public endpoint. Optional auth tokens, if your deployment needs them, are passed through as standard Authorization headers by the MCP client — never commit them to config files.

How the proxy works

MCP client (stdio)  ⇄  bin/dayplay-mcp.js  ⇄  https://www.dayplay.io/api/mcp (Streamable HTTP)

The shim lists tools and forwards tools/call verbatim to the remote endpoint, so new Dayplay tools appear automatically without an npm update. It is a transport bridge, not a reimplementation — every schema, filter, and verification rule is served by Dayplay itself.

Prefer direct HTTP if your client supports it; use the shim for stdio-only clients.

Repository layout

dayplay-mcp/
├── .cursor/
│   └── mcp.json              # Direct Cursor MCP connection
├── .cursor-plugin/
│   └── plugin.json           # Cursor Marketplace catalog plugin manifest
├── skills/
│   └── vibe-scout/
│       └── SKILL.md          # Grok Bot & Cursor Agent prompt instructions
├── bin/
│   └── dayplay-mcp.js        # Executable proxy for `npx -y @dayplayai/mcp-server`
├── assets/
│   └── logo.svg
├── test/
│   └── e2e.mjs
├── smithery.yaml             # Smithery.ai registry manifest
├── plugin.json               # Agent Plugins standard manifest
├── package.json              # npm metadata (@dayplayai/mcp-server v1.3.1, MIT)
├── README.md                 # This file
└── LICENSE                   # MIT (Dayplay Team)

Development

node bin/dayplay-mcp.js --smoke   # verify remote endpoint + tool discovery
node bin/dayplay-mcp.js           # run the stdio proxy
node test/e2e.mjs                 # end-to-end stdio smoke (tools + 3 tool calls)

Releasing (maintainers)

Publishing is fully automated via npm Trusted Publishing (OIDC) — no NPM_TOKEN, no 2FA prompts. The .github/workflows/publish.yml workflow is bound in the package's npm settings to this exact repo + workflow.

npm version patch        # or minor / major — bumps package.json, creates the vX.Y.Z tag
git push --follow-tags

CI then: verifies package.json version matches the tag → npm ci → smoke test → npm publish --provenance (sigstore-signed, OIDC-attested).

Gotcha: --follow-tags doesn't always push the tag. If no workflow run appears under Actions within a minute, finish with:

git push origin v1.X.Y

Notes:

• The registry shows "package is being processed" for ~3 minutes after publish before the new version resolves — don't panic-verify too early.
• npm's OIDC flow requires npm ≥ 11.5.1 in CI; the workflow installs npm@latest for this reason.
• If the workflow ever gains an environment: block, the npm Trusted Publisher binding must be updated to the same environment name, or publishes will be rejected.

License

MIT © Dayplay Team — https://www.dayplay.io