Inspo MCP provides read-only design-reference search across captured production websites, components, palettes, typography, and page structure for coding agents.
Compare 2-4 captured sites across palette, typefaces, macrostructure, mode, style tags, type/spacing/radius scales and container width. Returns per-site breakdowns plus what they share - triangulates a house style from a few references.
Real sites whose extracted palette sits near a hex colour (OKLAB distance, so 'close' means the same colour family, not just the same hue). Use when a brief names a brand colour.
Real sites featuring a specific UI component (hero, pricing, features, cta, nav, footer, testimonial, logo-cloud, faq, stat), with a per-element crop where one exists. For copy-pasteable code use get_reference_jsx.
Real sites exemplifying one of the 19 named macrostructures. Call it at the macrostructure-pick step. Accepts slugs ('bento-grid') or display names ('Bento Grid').
The canonical reference components as an index: id, label, macrostructure and a note for each hero / pricing / cta / nav / footer archetype. Pick one, then get_reference_jsx(type, id) for its source.
A screen's nearest design neighbours - ranked by design-similarity embeddings where available, else by macrostructure / industry / style overlap. One result per site.
Fetch one issue by slug, including the editor's blurb and ordered screen list.
The full DESIGN.md for one screen - real fonts, frequency-ranked palette, CSS variables, detected tech, colour roles, type ramp. Thin captured tokens are supplemented by a live fetch of the source; `live=false` skips that.
Every value the filters accept: styles, industries, macrostructures, modes, vibes, colors, page types, component types. Zero input. Call it when unsure - an out-of-vocabulary value errors.
The full canonical JSX source for one reference component, including the header stamp naming its macrostructure / theme / states. Copy-pasteable; tweak tokens to the target brand.
Fetch the full record for one screen by slug - every viewport variant, palette, fonts, tech stack, designer credit.
A site's captured pages as an ordered flow (landing → pricing → features → ...) with titles, northstars and thumbnails - how a real product sequences its pages. No arguments returns the directory of flow-capable sites. Accepts a site or screen slug.
List every editor-curated issue. Use this for thematic browsing - e.g. all 'Editorial Layouts' or 'Dark Product Pages'.
Orchestrator - start here for a brief. One call returns a macrostructure pick, 5 real exemplars, matching reference components (source via get_reference_jsx), a palette suggestion, and an `evidence` packet measuring the genre's paper band / display class / accent hue. Pass a macrostructure to skip the pick step. No LLM call.
Search the archive of real website screenshots. Returns screens with palette, fonts, components and image URLs.
The Inspo MCP integration connects your Dench AI CRM directly to Inspo MCP, so agents can read and act on your Inspo MCP data as part of everyday work — answering questions in chat, keeping your CRM in sync, and running automations without anyone copying data between tools.
15 actions are available for agents to invoke on your behalf. Every call runs through Inspo MCP's own authorization, scoped to the account you connect.
Sign in to your Dench workspace and open Integrations.
Find Inspo MCP and click Connect — you'll authorize access through Inspo MCP's own sign-in flow. No API keys or code required.
Ask an agent to use Inspo MCP in chat, or call it from an automation.
Manage or disconnect the connection any time from workspace settings.
The Dench Inspo MCP integration connects your AI CRM to Inspo MCP, so AI agents can work with your Inspo MCP data as part of chats, automations, and CRM workflows. You connect your account once, and every agent in your workspace can use it — governed by your workspace permissions.
The Inspo MCP integration currently exposes 15 actions, including Compare, Find by color, Find components, Find examples for macrostructure, Find reference components, and Find similar. Agents invoke them on your behalf from chat or from automations.
No. You connect Inspo MCP from your Dench workspace using Inspo MCP's own sign-in and authorization flow — no API keys to copy, no glue code to maintain.
Connections are authorized through Inspo MCP's own authentication flow, and Dench stores only the authorization needed to act on your behalf. You can review and disconnect the Inspo MCP connection from your workspace settings at any time.