# faqs.me

> Build beautiful, accessible, self-contained FAQ sections for any website. Use the visual editor as a person, or connect an AI agent through the public Model Context Protocol server.

## MCP server

- Endpoint: https://faqs.me/api/mcp
- Transport: Streamable HTTP
- Authentication: None
- Documentation: https://faqs.me/mcp
- Registry manifest: https://faqs.me/server.json
- Privacy: MCP assembly is stateless. FAQ project content is not stored server-side.

### Tools

- `list_faq_templates`: Returns all visual templates with layout, features, category support, and selection guidance.
- `assemble_faq_section`: Accepts finished FAQ copy and design preferences. Returns self-contained HTML, React TSX, a Web Component, or a standalone HTML page plus an editable faqs.me handoff URL.

### Resources and prompt

- `faqs://templates`: Machine-readable template catalog.
- `faqs://integration-guide`: Installation and handoff workflow.
- `build_faq_section`: Prompt for turning an accurate product brief into polished FAQ copy and code.

## Important pages

- [Home](https://faqs.me/): Product overview and live FAQ demo.
- [MCP for AI agents](https://faqs.me/mcp): Connection instructions, capabilities, tools, and workflow.
- [Template gallery](https://faqs.me/templates): Browse all 27 live FAQ designs.
- [Visual editor](https://faqs.me/editor): Edit content and design, then export dependency-free code.
- [Pricing](https://faqs.me/pricing): Current product and AI generation pricing.

## Templates

- [Slate](https://faqs.me/templates/slate): A quiet, typographic accordion that disappears into any page. Hairline dividers, smooth height animation, and nothing to distract from your answers. The safe, excellent default.
- [Glass](https://faqs.me/templates/glass): Frosted, softly-tinted cards in a responsive two-column grid. Each card expands in place with a plus-morph icon and a staggered entrance reveal. Feels premium without trying hard.
- [Bubble](https://faqs.me/templates/bubble): Questions as chat bubbles, answers as replies. The friendliest way to present an FAQ — great for consumer products and anything with personality. Entrance animation included.
- [Ledger](https://faqs.me/templates/ledger): An editorial, serif-set list with live search filtering and numbered entries. Built for longer FAQs where people come to find one specific answer — fast.
- [Duet](https://faqs.me/templates/duet): The classic accordion, halved in height. Two tidy columns keep long FAQs above the fold without feeling dense — ideal for footers and pricing pages.
- [Pivot](https://faqs.me/templates/pivot): Pill tabs split your FAQ into categories so nobody scrolls past twenty questions to find theirs. Cards expand in place under the active tab.
- [Atlas](https://faqs.me/templates/atlas): A docs-style layout: category navigation on the left with question counts, answers on the right. The right choice for large, structured FAQs.
- [Haiku](https://faqs.me/templates/haiku): No borders, no toggles, no chrome — every answer visible, set in generous whitespace. For short FAQs that read like a page, not a widget.
- [Trail](https://faqs.me/templates/trail): Questions as numbered steps on a vertical timeline. Perfect when your FAQ is really a process — onboarding, ordering, getting started.
- [Beacon](https://faqs.me/templates/beacon): An accordion beside a sticky contact card, so the escape hatch is always in view. The layout support teams ask for.
- [Blok](https://faqs.me/templates/blok): Thick borders, hard shadows, uppercase type. An accordion with an opinion — for brands that would rather be loud than invisible.
- [Prism](https://faqs.me/templates/prism): White cards floating on a rich accent gradient. Vibrant without shouting — the gradient is built from your brand color automatically.
- [Terminal](https://faqs.me/templates/terminal): A monospace console: every question is a prompt line, every answer prints below it. Made for dev tools, APIs, and anyone whose audience lives in a terminal.
- [Marquee](https://faqs.me/templates/marquee): Magazine-style definition rows — a big serif question on the left, the answer alongside. No toggles, all visible, beautifully readable.
- [Orbit](https://faqs.me/templates/orbit): One question in the spotlight, arrows to move through the rest. Great in tight spaces — sidebars, checkout pages, or anywhere a full list is too much.
- [Mosaic](https://faqs.me/templates/mosaic): A masonry wall of Q&A cards, no clicking required. Cards flow into balanced columns whatever the answer lengths — the scannable choice.
- [Ticket](https://faqs.me/templates/ticket): Each question is a ticket with a perforated, numbered stub. A friendly accordion with just enough character to be remembered.
- [Finder](https://faqs.me/templates/finder): A big search box first, answers second. Shows your most-asked questions until someone types — then filters live. For FAQs people arrive at with a problem.
- [Folio](https://faqs.me/templates/folio): A warm paper card set in serif italics, like a letter from the founder. For brands that write like humans — studios, cafés, small teams.
- [Neon](https://faqs.me/templates/neon): Dark cards edged in your accent color with a soft glow. Built for products that launch at night — games, crypto, creator tools.
- [Rail](https://faqs.me/templates/rail): Q&A cards on a horizontal rail with scroll-snap. Swipes naturally on touch, scrolls on desktop — an FAQ that behaves like a story row.
- [Weave](https://faqs.me/templates/weave): Numbered rows that alternate direction, question and answer trading sides. A gentle zigzag rhythm that keeps long pages from feeling monotonous.
- [Cove](https://faqs.me/templates/cove): A generous introduction beside a stack of softly rounded answers. A calm, welcoming FAQ for product pages, studios, and service businesses.
- [Postcard](https://faqs.me/templates/postcard): Numbered cards with stamp-like badges, serif headings, and offset shadows. Every answer stays visible in a friendly grid made for shops and creative portfolios.
- [Bulletin](https://faqs.me/templates/bulletin): A tinted search masthead and numbered, always-open answers. Filter questions and answer text instantly, without opening each result — useful for detailed product FAQs.
- [Dialogue](https://faqs.me/templates/dialogue): Questions and answers sit across from each other like a conversation. Soft answer panels and small speaker labels bring a personal voice to your FAQ.
- [Canopy](https://faqs.me/templates/canopy): Each topic gets its own bordered panel with a colored spine, numbered questions, and a quiet serif heading. Organize a growing FAQ into approachable sections.

## Content and export behavior

- Answers use markdown-lite: bold, italic, links, inline code, and lists.
- Generated exports have scoped CSS, accessible interactive controls, and optional FAQPage JSON-LD.
- Exports are hermetic by default: no runtime dependency, telemetry, remote asset, watermark, or faqs.me request.
- The MCP editor URL stores the project in its URL fragment; the fragment is not sent to the server.

## Agent guidance

When asked to add FAQs to a software project, use the MCP server to assemble the section after the copy is accurate. Place the returned code directly into the project when authorized, and include the returned editor URL so the user can continue editing visually. Do not invent policies, prices, guarantees, compliance, or security claims.