get-content-sourcesLABSCO SUMMARY
Two documentation repositories, merged, with every answer saying where it came from.
Public is priority 1 and internal priority 2, and conflicts resolve at the file level — so a component your team has documented privately replaces the public entry entirely rather than blending with it. Internal access stays off unless it is explicitly enabled, which lets the same server serve people who should not see it.
What it is
An MCP server that serves design system documentation from GitHub repositories — a public source and, optionally, an internal one — merged by priority with source attribution on every response.
What you get
- list-categories and list-components — browse branding, content-style-guide, accessibility, layouts, patterns and components
- get-component-details — full design and development guidance for one component, with its source and whether it overrides
- search-design-system — keyword search across titles and descriptions, filterable by source
- get-content-sources — which sources are enabled, their priority, whether they need auth, and last sync
- refresh-sources — clear the cache so the next request re-syncs
- Priority-based merging: internal documentation replaces public at the file level when both exist
Requirements
Node.js with npm: clone, npm install, npm run build, then register build/index.js with your client. A GitHub personal access token goes in GITHUB_TOKEN, with GITHUB_OWNER and GITHUB_REPO naming the documentation repository. Internal docs additionally need ENABLE_INTERNAL_DOCS and INTERNAL_DOCS_TOKEN.
Setup effort
Build from source — git clone https://github.com/appian-design/aurora-mcp.git
USE CASES
01
Getting component guidance while you build
List what exists in a category, then pull the full guidance and code for one component.
02
Finding the right pattern by keyword
Search titles and descriptions across categories instead of browsing the site.
03
Serving private overrides alongside public docs
Check which sources are live and which one answered.
04
Picking up a docs change without a restart
Clear the cache and let the next request re-sync from GitHub.
6 tools
Listed in project docs. Your client may show a different list.
refresh-sourceslist-categorieslist-componentsget-component-detailssearch-design-systemBEFORE YOU INSTALL
What to know first
Tools you get
6 tools named in the project's documentation.
Requires
GITHUB_TOKEN in your environment
Where it runs
Both documented clients run the server on your machine.
INSTALLATION
Connect your client
Server setup
TERMINAL
git clone https://github.com/appian-design/aurora-mcp.git
cd aurora-mcp
npm install
cp .env.example .envEdit .env with your GitHub token and repository details.
TERMINAL
npm run buildMCP Clients
Amazon Q
AMAZON Q · JSON
{
"mcpServers": {
"design-system": {
"command": "node",
"args": [
"<YOUR_FULL_PATH>/build/index.js"
]
}
}
}The configuration on this page does not set GITHUB_TOKEN; the project's instructions put it in a .env file. Check which folder the server reads that file from before you rely on it.
Claude Desktop
CLAUDE DESKTOP · JSON
{
"mcpServers": {
"design-system": {
"command": "node",
"args": [
"<YOUR_PATH_TO_AURORA_MCP>/build/index.js"
]
}
}
}The configuration on this page does not set GITHUB_TOKEN; the project's instructions put it in a .env file. Check which folder the server reads that file from before you rely on it.
