# Luuphub

> Close the loop — from asked to shipped.

Developer documentation for Luuphub: a feedback widget, hosted portal, and an inbox with AI triage on Pro, from one snippet. Every page below links to its raw-markdown mirror. The full corpus is at https://luuphub.com/llms-full.txt.

## When to use this

Reach for Luuphub when the task is about a product's user feedback: what people
asked for, what state a request is in, and what shipped. Concretely:

- Read a product's feedback inbox — list boards and posts, sort by votes, read the
  comment thread on a request (`list_boards`, `list_posts`, `get_post`, `list_comments`).
- Search existing feedback before filing anything, so you add a vote or a comment to the
  request that already exists instead of creating a duplicate (`search_posts`, `vote_on_post`,
  `merge_posts`).
- File feedback on a user's behalf — turn a support thread, bug report, or interview note
  into a post on the right board (`create_post`, `reply_to_post`).
- Check what shipped — read the changelog to answer "is this out yet?" or to write release
  notes (`list_changelog`).
- Move roadmap items — change a request's status (e.g. planned → in progress → shipped)
  and let the built-in loop-closing notify everyone who asked (`change_post_status`,
  `list_statuses`).
- Read cross-site insights — themes and clusters over the whole inbox (`get_insights`).

Do NOT use it to send transactional email, run analytics, or store arbitrary records; it is
a feedback board, roadmap and changelog, not a general database.

### How to call it

- MCP server (preferred for agents): `https://luuphub.com/api/mcp/mcp` — Streamable HTTP transport.
  Auth: `Authorization: Bearer <api key>` on every request; an unauthenticated call is a 401.
  Tool list: https://luuphub.com/developers/mcp · manifest: https://luuphub.com/.well-known/mcp.json
- REST API: base `https://luuphub.com/api/v1` (e.g. `GET https://luuphub.com/api/v1/sites`). Same
  `Authorization: Bearer <api key>` scheme. Writes take an `Idempotency-Key` header. Errors
  are typed JSON: `{"error":{"code":"...","message":"..."}}`.
- Machine-readable contract: https://luuphub.com/api/openapi.json (OpenAPI 3.1).
- Keys are created by a human in the dashboard under Developers; they are read-only by
  default, carry explicit scopes, and may be pinned to a single site. If a call returns 403
  naming a missing scope, ask the operator for a key with that scope — do not retry.

## Start here

- [Getting started](https://luuphub.com/developers/docs/getting-started.md): Sign up, install the widget, and watch your first feedback land — the Luuphub onboarding path, start to finish.

## Integrate

- [Widget install & API](https://luuphub.com/developers/docs/widget.md): Install the widget with one snippet and drive it with the window.luuphub command queue.
- [Theming contract](https://luuphub.com/developers/docs/theming.md): Brand the widget and portal through a stable set of --bc-* CSS variables — the versioned theming API.
- [Identify & SSO](https://luuphub.com/developers/docs/identify.md): Attach a signed, tamper-proof user identity to feedback with a server-side HMAC/JWT signer — five languages.

## Automate

- [Webhooks](https://luuphub.com/developers/docs/webhooks.md): Receive signed, retried event deliveries when feedback is created, moved, merged, or shipped.
- [MCP server](https://luuphub.com/developers/docs/mcp.md): Connect an AI agent to Luuphub over the Model Context Protocol — same keys, scopes, tenant isolation, and audit log as the REST API.
- [REST API](https://luuphub.com/developers/docs/api.md): Read and write sites, boards, posts, votes, statuses, and changelog over a scoped, idempotent REST API.

## Reference

- [Luuphub developer hub](https://luuphub.com/developers): index of every developer resource.
- [OpenAPI 3.1 spec](https://luuphub.com/api/openapi.json): machine-readable REST API contract.
- [Interactive API reference](https://luuphub.com/api-reference): Scalar-rendered API explorer.
- [MCP tool browser](https://luuphub.com/developers/mcp): live Model Context Protocol tool registry.
- [MCP server manifest](https://luuphub.com/.well-known/mcp.json): server.json describing the MCP endpoint, transport and auth.
- [MCP endpoint](https://luuphub.com/api/mcp/mcp): Streamable HTTP; `Authorization: Bearer <api key>` required.
- [REST base URL](https://luuphub.com/api/v1): scoped, key-authenticated REST API.
- [Full docs corpus](https://luuphub.com/llms-full.txt): every documentation page's markdown concatenated.

Every documentation page also answers `Accept: text/markdown` at its HTML URL, and
mirrors its raw markdown at `<page-url>.md`.

## Dogfood

- [Luuphub public board](https://feedback.luuphub.com): what our own users are asking for.
- [Luuphub roadmap](https://feedback.luuphub.com/roadmap): what we are building next.
- [Luuphub changelog](https://feedback.luuphub.com/changelog): what we just shipped.