MCP for assistants

Use this when: you want Cursor, Claude Code, VS Code, or another MCP client to search these guides and the generated TypeDoc API—without copying Markdown into a prompt.

Under the hood, Model Context Protocol exposes tools such as list_guides, read_guide, and search_docs so agents pull the same content as this site.

Endpoint URL

Public Streamable HTTP URL (no bearer token on the default deployment unless you add your own):

https://play-u1.vercel.app/api/mcp

If NEXT_PUBLIC_PLAY_U1_MCP_URL is set at build time, the line above reflects your fork or staging origin.

What the tools do

Tool	Purpose
`list_guides`	Lists guide slugs and titles.
`read_guide`	Returns Markdown for a slug (for example `quickstart`).
`search_docs`	Searches guide sources and the TypeDoc Markdown bundle. From a clone, run `npm run typedoc` before expecting local API Markdown in search.

Cursor (one click)

Add to CursorOpens Cursor to install the play-u1 documentation MCP (install links).

The deeplink targets https://play-u1.vercel.app/api/mcp by default. Override with NEXT_PUBLIC_PLAY_U1_MCP_URL when you build the docs app.

Cursor (manual)

Add a remote MCP server and paste the HTTPS URL. If the client will not connect, add "type": "http" next to "url" in ~/.cursor/mcp.json. See Cursor’s MCP documentation.

Use /api/mcp on this docs site, or /mcp on the optional container image below.

Use the same remote MCP URL (and bearer token, if you enabled MCP_BEARER_TOKEN) in team Cursor Cloud settings so cloud agents can call list_guides, read_guide, and search_docs.

Claude Code

Follow Anthropic’s instructions for remote / URL-based MCP servers.

Hosted docs: https://play-u1.vercel.app/api/mcp (or your deployment’s /api/mcp).
Self-hosted container: https://YOUR_HOST/mcp.

If your toolchain only supports stdio, build play-u1-mcp from a clone and register the stdio command locally—see the play-u1-mcp README on GitHub.

Visual Studio Code

Use VS Code’s MCP configuration for HTTP / remote servers (availability depends on version). Point at https://play-u1.vercel.app/api/mcp or your https://YOUR_HOST/mcp. Add Authorization: Bearer … when the server requires it.

URLs to paste

Hosted documentation (this Next.js app):

https://play-u1.vercel.app/api/mcp

Optional MCP container (TLS at your edge; default path /mcp):

https://YOUR_HOST/mcp

Set MCP_BEARER_TOKEN on the server when clients must send Authorization: Bearer ….

Self-hosting and advanced setups

Same-origin route on this docs app

MCP is served at /api/mcp (Streamable HTTP via mcp-handler).

Environment	URL
Production (this repo’s deployment)	`https://play-u1.vercel.app/api/mcp`
Your deployment	`https://YOUR_DOCS_ORIGIN/api/mcp`
Local dev	`http://localhost:3000/api/mcp` after `npm run docs:dev` from the monorepo root

Optional env: MCP_VERBOSE_LOGS=1; MCP_BEARER_TOKEN plus matching client headers.

Container image from `main`

GitHub Actions publishes ghcr.io/<repository-lowercase>:mcp. Terminate TLS at your edge, set PLAY_U1_ROOT=/app (default), PORT, and a strong MCP_BEARER_TOKEN for anything on the public internet.

Local stdio while developing clients

npm run mcp:build
node packages/play-u1-mcp/dist/stdio.js

Contributor-focused notes live on GitHub.