npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

@neural-ng/mcp-server

v0.1.0-beta.6

Published

Read-only MCP server for NeuralNg component and compact theme contracts.

Readme

@neural-ng/mcp-server

Read-only Model Context Protocol server for NeuralNg component discovery, contracts, package exports, documentation and compact theme recipe workflows.

The server is separate from @neural-ng/core. Angular applications never load an MCP runtime in the browser. Theme tools return recipes, validation results, diffs and compile summaries; they do not write files or execute shell commands.

Run

npx -y @neural-ng/mcp-server

Generic MCP client configuration:

{
  "command": "npx",
  "args": ["-y", "@neural-ng/mcp-server"]
}

The process uses stdio. Standard output is reserved for MCP JSON-RPC messages; fatal diagnostics are written to standard error.

Resources

Component and package resources:

  • neural://catalog
  • neural://package/exports
  • neural://components/{id}/contract
  • neural://components/{id}/readme
  • neural://components/{id}/llms

Theme resources:

  • neural://themes/catalog
  • neural://themes/schema
  • neural://themes/presets
  • neural://themes/presets/neutral
  • neural://themes/presets/glass
  • neural://themes/presets/mist
  • neural://themes/presets/futuristic
  • neural://themes/ai-guide

Component resources are registered as fixed URIs. The server does not accept a filesystem path and does not read arbitrary files.

Component tools

search_components

Searches public selectors, entry points, summaries, README files and llms.txt guidance.

{
  "query": "date calendar localized",
  "limit": 5
}

get_component_contract

Resolves a component by catalog id, class name, selector or public entry point.

{
  "component": "neural-tri-state-checkbox"
}

recommend_components

Uses deterministic intent matching. It does not invoke another model or a network service.

{
  "goal": "nullable inherited permission checkbox",
  "limit": 3
}

Compact theme tools

The theme workflow intentionally operates on the small recipe rather than the resolved 1,348-token Core and Editor graph.

create_theme_recipe

{
  "name": "violet-workspace",
  "options_json": "{\"preset\":\"glass\",\"primary\":\"#7c3aed\",\"radius\":\"large\"}"
}

validate_theme_recipe

{
  "recipe_json": "{\"schemaVersion\":1,\"name\":\"violet-workspace\",\"extends\":\"neutral\"}"
}

edit_theme_recipe

Applies a bounded, prototype-safe sparse patch and validates the result. Theme validation rejects declaration injection, external CSS URLs, malformed aliases, and unknown component tokens before compilation.

{
  "recipe_json": "{\"schemaVersion\":1,\"name\":\"violet-workspace\",\"extends\":\"neutral\"}",
  "patch_json": "{\"set\":{\"color.primary\":\"#7c3aed\",\"shape.radius\":\"large\"}}"
}

diff_theme_recipes

Returns only changed dotted recipe paths instead of repeating both recipes.

get_component_theme_contract

Returns one component's supported theme properties. Use detail: "names" by default and request detail: "defaults" only when current mode values are needed.

{
  "component": "toast",
  "detail": "names"
}

Recipe versions and quality metadata

Theme MCP tools author schema version 1. Early preview recipes should first be migrated with neural-theme migrate or migrateThemeRecipe() from @neural-ng/theme; MCP remains read-only and does not rewrite user files. Preset resources include stability and quality governance metadata so agents can prefer release baselines unless the user explicitly requests a preview style.

compile_theme_recipe

Runs the real @neural-ng/theme compiler and returns validation diagnostics, summary data, artifact byte sizes and integration instructions. It deliberately does not send full CSS or token artifacts through the model context. Generate those files with:

npx neural-theme build

Catalog source

The committed component catalog is generated from:

  • tsconfig.base.json public @neural-ng/core/* paths;
  • each public secondary entry point's index.ts;
  • public Angular component and directive selectors;
  • package exports, README files and llms.txt files.

Regenerate and verify it with:

npx nx run neural-mcp:catalog
npx nx run neural-mcp:catalog-check

Quality commands

npx nx lint neural-mcp
npx nx test neural-mcp
npx nx build neural-mcp
npx nx run neural-mcp:package-test
npx nx run neural-mcp:mcp-smoke

mcp-smoke packs both @neural-ng/theme and the MCP server, installs them into an isolated temporary consumer, initializes stdio MCP, reads component and theme resources, then calls component discovery and compact theme compiler tools.