Skip to main content
raulg0001
Inspiring
Oct 16, 2026 10:15 PM UTC
Question

Aurora MCP

In my development work, I’m using several tools: `dev mcp`, `mcp doc`, `dev mcp skill`, and `aurora mcp`.

I’m wondering about the difference between using `dev mcp skill` and `aurora mcp`—do their functionalities overlap, or are they meant for different purposes? As I understand it, `dev mcp skill` already covers the same ground as `aurora mcp`. Could someone please clarify?

 

https://github.com/appian-design/aurora-mcp

https://github.com/appian/dev-mcp-skills

6 replies

mathieud0001
Genius
Oct 16, 2026 10:21 PM UTC

That MCP is for Appian Design.

This is a Model Context Protocol (MCP) server that provides access to Appian's design system documentation through GitHub repositories. It supports both public and internal documentation sources, allowing LLMs like Claude to query and explore design system components, layouts, and patterns with appropriate access controls.

 

raulg0001
raulg0001Author
Inspiring
Oct 16, 2026 10:24 PM UTC

I understand that; my question is whether or not you recommend using it, given that the MCP dev skill allows for the creation of interfaces without using Aurora. In other words, when should I use Aurora?

mathieud0001
Genius
Oct 16, 2026 11:24 PM UTC

You shouldn’t have to think about it, just plug it and the LLM combined with the skills will determine whether they use it or not.

Inspiring
Oct 19, 2026 3:02 PM UTC

I see them as complementary rather than replacements. Dev MCP Skills helps with Appian development tasks, including creating interfaces, while Aurora MCP provides additional guidance on Appian's design system, UI components, layouts, and design patterns. I would use Aurora when UI consistency and following Appian design guidelines are important. For general interface development, Dev MCP Skills should be sufficient. You can also configure both and let the AI assistant use them based on the task.