# Design Stream
> Design Stream is MonoMind's private library of real websites, captured whole and split into sections, with each page's design system, copy and SEO metadata extracted. Designers browse it; AI agents query it through an authenticated API and MCP server.
Design Stream is built and run by MonoMind (https://monomind.one). The library holds over 2,300 captured websites and more than 18,000 sections: hero, pricing, testimonials, logo walls, FAQ, footer and more. Each capture keeps a screenshot of every section plus the design system read off the live page. That covers the palette with measured contrast, the type ramp, spacing stops, radii, shadows, breakpoints and the site's own `:root` CSS custom properties. It also covers the page's `
`, meta description, canonical URL and heading outline.
Any captured site can be rendered as a design brief: a deterministic Markdown document (`design.md`) built only from the capture record, meant to be pasted into a prompt. People curate sites and sections into boards, which can be shared with a client by link.
Access is private and by invitation. There are no public sign-ups. MonoMind adds your email and an invitation arrives, and you sign in at https://auth.designstream.dev. What you can reach depends on your role:
- admin and team members browse the whole library at https://designstream.dev/gallery/ and can create boards.
- clients see only the boards shared with them.
- headless callers (scripts, CI, MCP clients) send `Authorization: Bearer `. The token is a per-user API token (it never expires by default, or lasts 30, 60 or 90 days, and can be revoked at any time) that a signed-in admin or team member creates from the library's "API tokens for MCP" dialog.
Only `/api` and `/api/health` answer without a credential. Every library read returns `401` without one, so nothing in the library can be read anonymously over HTTP.
The library MCP server is hosted by Design Stream itself. It speaks Streamable HTTP at `https://designstream.dev/mcp` and accepts the same bearer token as the API: a per-user API token from the library's "API tokens for MCP" dialog, sent as `Authorization: Bearer `. There is nothing to install. Adding it to Claude Code:
```bash
claude mcp add --transport http -s user design-stream-library https://designstream.dev/mcp \
--header "Authorization: Bearer "
```
`claude mcp add` refuses a name that already exists, so to swap in a new token run `claude mcp remove -s user design-stream-library` first. The "API tokens for MCP" dialog composes the line with the token filled in and that removal in front.
Other MCP clients take the same URL and header in their own configuration. Cursor reads `~/.cursor/mcp.json`:
```json
{
"mcpServers": {
"design-stream-library": {
"url": "https://designstream.dev/mcp",
"headers": { "Authorization": "Bearer " }
}
}
}
```
VS Code reads `.vscode/mcp.json`, where the entry goes under `servers` and needs `"type": "http"` beside the same `url` and `headers`. Claude Desktop and claude.ai custom connectors sign in with OAuth, which the hosted server does not offer yet, so neither can connect today.
The server exposes 22 tools: `search_library`, `browse_sites`, `browse_sections`, `get_site` and `library_facets` (find references); `get_design_brief`, `export_tokens`, `compare_design_systems` and `list_blocks` (read a design system); `render_style_board`, `render_type_scale`, `render_spacing_scale`, `render_seo_board`, `render_design_md`, `render_css` and `render_dna` (render views of a capture); `list_boards`, `get_board`, `get_board_brief` and `save_to_board` (boards); and `whoami` and `library_status`. `save_to_board` is the only one that writes: it adds items to a board the caller owns.
The full user guide, with setup for Claude Code, Cursor, VS Code and other clients, a reference for every tool, example workflows and troubleshooting, is at https://designstream.dev/mcp-guide.
## Access
- [Sign in](https://auth.designstream.dev): the Design Stream auth service. Invitation only.
- [Design Stream](https://designstream.dev/): the public landing page, which explains what the library is and how engagements work.
- [Book a consultation](https://monomind.one/contact/?ref=design-stream): how to get access, or run Design Stream for your own studio.
- [MCP user guide](https://designstream.dev/mcp-guide): getting a token, connecting to the MCP server, the tool reference and troubleshooting.
- [Logo & Icons](https://designstream.dev/brand): the Design Stream logo, icon, colours and usage rules, with SVG downloads.
## API
The base URL is `https://designstream.dev/api`. Responses are JSON unless noted, and errors look like `{"error": {"code", "message"}}`. Everything except `/api` and `/api/health` needs a bearer token.
- [GET /api/health](https://designstream.dev/api/health): public. Reports the API version, search mode, auth mode and record counts.
- [GET /api/sites](https://designstream.dev/api/sites): captured sites, filtered by `q`, `page_type`, `industry`, `visual_style`, `category`, `color_mode`, `kind` and `tag`. Pages through results with `cursor`.
- [GET /api/sites/{slug}](https://designstream.dev/api/sites/stripe-com): one site's full record, including `seo`.
- [GET /api/sites/{slug}/design.md](https://designstream.dev/api/sites/stripe-com/design.md): that site as a Markdown design brief (`text/markdown`).
- [GET /api/sections](https://designstream.dev/api/sections): sections across every site, with the same filters.
- [POST /api/search](https://designstream.dev/api/search): searches sections or sites from a JSON body (`q`, `target`, `filters`). The response's `mode` says whether ranking was `hybrid` (embeddings plus full text) or `lexical`.
- [GET /api/facets](https://designstream.dev/api/facets): every filter value, with counts.
- [GET /api/boards](https://designstream.dev/api/boards): the caller's boards, and the ones shared with them.
- [GET /api/auth/session](https://designstream.dev/api/auth/session): who the presented credential belongs to, and what kind it is.
## Optional
- [MonoMind](https://monomind.one): the company behind Design Stream.