---
title: "Inspo MCP integration for LuumenAI"
url: "https://www.luumen.ai/integrations/inspo-mcp/"
entity: SoftwareIntegration
category: "AI & automation"
audience: "SRE, DevOps, platform engineering, IT operations"
---

# Inspo MCP integration for LuumenAI

Design references from real captured sites, read-only, no credential needed

## What LuumenAI can do with Inspo MCP

LuumenAI connects to Inspo MCP without a credential of its own and exposes 15 tools (15 read-only). Every tool is read-only, so it can answer questions from Inspo MCP but cannot change anything in it. Read actions still follow the configured access and approval policy.

## Key facts

- Authentication: none required
- Tools available: 15 tools (15 read-only)
- Deployment: scoped as part of your Pilot, Platform, or Managed rollout
- Category: AI & automation

## About Inspo MCP with LuumenAI

Ask for design precedent while you build. Inspo MCP searches captured production sites for palettes, typography, components, and page structure. Pull one screen's full record with INSPO_MCP_GET_SCREEN, or compare a shortlist side by side with INSPO_MCP_COMPARE. Every tool is read-only, and the connection needs no credential.

## Example tools

Read-only (15 in total):

- `INSPO_MCP_COMPARE` — Compare 2-4 captured sites across palette, typefaces, macrostructure, mode, style tags, type/spacing/radius scales and container width.
- `INSPO_MCP_FIND_BY_COLOR` — Real sites whose extracted palette sits near a hex colour (OKLAB distance, so 'close' means the same colour family, not just the same hue).
- `INSPO_MCP_FIND_COMPONENTS` — 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.
- `INSPO_MCP_FIND_EXAMPLES_FOR_MACROSTRUCTURE` — Real sites exemplifying one of the 19 named macrostructures.
- `INSPO_MCP_FIND_REFERENCE_COMPONENTS` — The canonical reference components as an index: id, label, macrostructure and a note for each hero / pricing / cta / nav / footer archetype.
- `INSPO_MCP_FIND_SIMILAR` — A screen's nearest design neighbours - ranked by design-similarity embeddings where available, else by macrostructure / industry / style overlap.
- `INSPO_MCP_GET_COLLECTION` — Fetch one issue by slug, including the editor's blurb and ordered screen list.
- `INSPO_MCP_GET_DESIGN_SYSTEM` — The full DESIGN.md for one screen - real fonts, frequency-ranked palette, CSS variables, detected tech, colour roles, type ramp.

## Frequently asked questions

### How does LuumenAI connect to Inspo MCP?

Inspo MCP needs no credential of its own, so there is nothing to authorize. Access is still granted per agent, skill, and team inside Luumen, and every call is logged.

### Can LuumenAI change things in Inspo MCP on its own?

No. Every one of the 15 tools is read-only, so LuumenAI can answer questions from Inspo MCP but cannot change anything in it. Read actions still follow the configured access and approval policy.

### Is there an audit trail?

Every call to Inspo MCP is recorded with the actor, the input, and the result.

Full page: https://www.luumen.ai/integrations/inspo-mcp/