Neuria Agent MCP Server

Emotion-driven design intelligence for AI coding tools. That is what the neuria agent mcp server brings to an AI assistant: the same capability, reachable through the Model Context Protocol rather than a separate app or dashboard.

The short version

NEURIA quantifies that feeling into actionable design tokens.

Each emotion includes color palettes, typography settings, spacing scales, border radii, shadow styles, and animation parameters — all derived from statistical analysis of real CSS extracted from 300+ top websites.

Getting it running

Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client. The configuration blocks on this page cover the common clients.

What it needs from you

Configuration is passed through the environment: FIRECRAWL_API_KEY, SCREENSHOTONE_API_KEY, IMAGGA_API_KEY, HUME_API_KEY, SUPABASE_URL, SUPABASE_KEY, THREE_D_AI_STUDIO_KEY, IMAGGA_API_SECRET. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.

Things to watch

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
• Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.

How it compares

Plenty of developer tooling servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. It is maintained by kosukeuemura0220-del; worth a glance at recent repository activity before you build anything load-bearing on it.

SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.