@dayplayai/mcp-server 1.2.1 → 1.3.0
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +28 -1
- package/package.json +10 -7
- package/smithery.yaml +10 -11
package/README.md
CHANGED
|
@@ -1,7 +1,9 @@
|
|
|
1
|
-
#
|
|
1
|
+
# DayPlay — Verified Local Concierge MCP for AI Agents
|
|
2
2
|
|
|
3
3
|
**`@dayplayai/mcp-server`** · v1.2.1 · MIT
|
|
4
4
|
|
|
5
|
+
[](https://smithery.ai/servers/dayplayai/dayplay)
|
|
6
|
+
|
|
5
7
|
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.
|
|
6
8
|
|
|
7
9
|
> 🔒 **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.
|
|
@@ -213,6 +215,31 @@ node test/e2e.mjs # end-to-end stdio smoke (tools + 3 tool calls
|
|
|
213
215
|
|
|
214
216
|
---
|
|
215
217
|
|
|
218
|
+
## Releasing (maintainers)
|
|
219
|
+
|
|
220
|
+
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.
|
|
221
|
+
|
|
222
|
+
```bash
|
|
223
|
+
npm version patch # or minor / major — bumps package.json, creates the vX.Y.Z tag
|
|
224
|
+
git push --follow-tags
|
|
225
|
+
```
|
|
226
|
+
|
|
227
|
+
CI then: verifies `package.json` version matches the tag → `npm ci` → smoke test → `npm publish --provenance` (sigstore-signed, OIDC-attested).
|
|
228
|
+
|
|
229
|
+
**Gotcha:** `--follow-tags` doesn't always push the tag. If no workflow run appears under *Actions* within a minute, finish with:
|
|
230
|
+
|
|
231
|
+
```bash
|
|
232
|
+
git push origin v1.X.Y
|
|
233
|
+
```
|
|
234
|
+
|
|
235
|
+
Notes:
|
|
236
|
+
|
|
237
|
+
- The registry shows *"package is being processed"* for ~3 minutes after publish before the new version resolves — don't panic-verify too early.
|
|
238
|
+
- npm's OIDC flow requires **npm ≥ 11.5.1** in CI; the workflow installs `npm@latest` for this reason.
|
|
239
|
+
- 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.
|
|
240
|
+
|
|
241
|
+
---
|
|
242
|
+
|
|
216
243
|
## License
|
|
217
244
|
|
|
218
245
|
MIT © Dayplay Team — https://www.dayplay.io
|
package/package.json
CHANGED
|
@@ -1,19 +1,22 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "@dayplayai/mcp-server",
|
|
3
|
-
"version": "1.
|
|
4
|
-
"description": "
|
|
3
|
+
"version": "1.3.0",
|
|
4
|
+
"description": "DayPlay MCP \u2014 verified real-time SF Bay Area places, events & walkable itineraries for AI agents. 3 free discovery tools + AI outing planning with a free account. Remote endpoint: https://www.dayplay.io/api/mcp",
|
|
5
5
|
"keywords": [
|
|
6
6
|
"mcp",
|
|
7
7
|
"model-context-protocol",
|
|
8
|
-
"
|
|
9
|
-
"sf",
|
|
8
|
+
"ai-agents",
|
|
10
9
|
"san-francisco",
|
|
11
10
|
"bay-area",
|
|
11
|
+
"oakland",
|
|
12
|
+
"berkeley",
|
|
13
|
+
"events-api",
|
|
14
|
+
"places-api",
|
|
12
15
|
"travel",
|
|
13
|
-
"
|
|
16
|
+
"concierge",
|
|
17
|
+
"walkability",
|
|
14
18
|
"itinerary",
|
|
15
|
-
"
|
|
16
|
-
"anti-drift"
|
|
19
|
+
"local-search"
|
|
17
20
|
],
|
|
18
21
|
"license": "MIT",
|
|
19
22
|
"author": "Dayplay Team (https://www.dayplay.io)",
|
package/smithery.yaml
CHANGED
|
@@ -1,16 +1,15 @@
|
|
|
1
1
|
name: dayplay
|
|
2
|
-
displayName:
|
|
2
|
+
displayName: DayPlay — SF Bay Area Local Concierge for AI Agents
|
|
3
3
|
description: >-
|
|
4
|
-
|
|
5
|
-
|
|
6
|
-
|
|
7
|
-
|
|
8
|
-
|
|
9
|
-
|
|
10
|
-
|
|
11
|
-
|
|
12
|
-
|
|
13
|
-
version: 1.2.0
|
|
4
|
+
Verified real-time places, events & walkable itineraries for AI agents.
|
|
5
|
+
Geo-locked to San Francisco, Oakland & Berkeley (35 neighborhood centroids).
|
|
6
|
+
3 free discovery tools; a free account unlocks plan_outing — full multi-stop
|
|
7
|
+
evening plans with walk times, saved to the user's DayPlay account — plus
|
|
8
|
+
saved plans and sellout/closure/weather alerts. Honest zero-results protocol:
|
|
9
|
+
agents never fabricate venues, events, dates, or hours (Anti-Drift Guarantee).
|
|
10
|
+
One remote URL, no API key. NOT AVAILABLE outside the SF Bay Area — out-of-market
|
|
11
|
+
requests are refused by protocol, never invented.
|
|
12
|
+
version: 1.3.0
|
|
14
13
|
license: MIT
|
|
15
14
|
homepage: https://www.dayplay.io
|
|
16
15
|
repository: https://github.com/dayplayTeam/dayplay-mcp
|