MCP access

How to connect

Enlighten Assets is available through the hosted remote MCP endpoint for SSO-capable clients. If your client does not support remote MCP OAuth yet, use the local stdio fallback from a cloned copy of this repository. Additions to the registry happen through MCP, not the web UI.

Hosted MCP URL: https://mcp.assets.enlightenailabs.com/mcp

Compatible MCP clients

These are common MCP-capable clients to start with. Remote OAuth and stdio support vary by client, so use the hosted endpoint when your client supports remote MCP OAuth and the local fallback when it does not.

Claude CodeCursorCodexMCP InspectorOther MCP clients

Prerequisites

Access

Git access to the Enlighten Assets repository and permission to use company brand, skill, and client materials.

Runtime

Node and npm installed locally. This repo expects a current Node runtime compatible with the project engines.

Local copy

Only needed for the stdio fallback. Clone the repo, open a terminal at the repo root, and run npm install.

Configure hosted remote MCP

Add a remote MCP server entry pointing at the hosted endpoint. The exact settings file location depends on your coding assistant, but the server definition should look like this:

{
  "mcpServers": {
    "enlighten-assets": {
      "url": "https://mcp.assets.enlightenailabs.com/mcp"
    }
  }
}

On first use, your client should open the Clerk sign-in flow. Sign in with your Enlighten account, then retry the MCP request after the client stores the OAuth token.

Local stdio fallback

If your client does not support remote MCP OAuth, add an MCP server entry using stdio transport:

{
  "mcpServers": {
    "enlighten-assets": {
      "command": "npm",
      "args": ["run", "mcp:stdio"],
      "cwd": "/path/to/enlighten-assets"
    }
  }
}

Replace /path/to/enlighten-assets with the absolute path to your cloned repo. The command must run from that directory so the server can read the local registry and assets.

Reload the connection

Save the config, then restart or reload the AI coding tool or MCP client. After it starts, confirm that the Enlighten Assets server appears in the available MCP servers list and that its tools are available.

Useful prompts

Browse

Ask it to call list_skills, list_design_systems, or search_assets.

Use

Ask it to get a design system, read a skill, install a skill, or pull an asset into your working context.

Add to the registry

Ask it to add a client with add_client, add a skill with add_skill, or add a design system with add_design_system. These MCP tools are the supported creation path.

Troubleshooting

Problem	What to check
Server does not show up	Restart or reload the MCP client after saving config. Check that the server name is enabled.
Command exits immediately	Run `npm install` in the cloned repo, then try `npm run mcp:stdio` from a terminal.
Repo cannot be found	Use an absolute `cwd`. If your repo path contains spaces, keep the path as one JSON string.
Remote endpoint fails	Confirm your MCP client supports OAuth for remote MCP servers, then sign in again. If OAuth is not supported, use the local stdio fallback.

Security

Enlighten Assets is for company users only. Keep local environment files, tokens, and secrets out of git, and do not commit local env files or credentials when contributing assets.