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

@websem/angular

v0.1.5

Published

Angular WebMCP adapter for @websem/client

Downloads

741

Readme

@websem/angular

Angular v22+ WebMCP tools backed by @websem/client.

Install

npm install @websem/angular

Packages

TypeScript: @websem/client, @websem/builder, @websem/angular, and @websem/types.

Python: websem-client, websem-builder, mkdocs-websem, and websem-types.

The adapter requires a Websem index with prebuilt embeddings. Build the index ahead of time with @websem/builder or websem-builder, serve its generated files as static assets, and point indexUrl to that directory. When using artifacts or client instead, they must already contain the built index.

The config mirrors sdl-mcp: tool instructions, descriptions, query descriptions, and result messages come from texts.DOC_* and optional texts.ICON_* fields. Set exactly one of indexUrl, artifacts, or client for documentation search. Icon search uses the matching iconIndexUrl, iconArtifacts, or iconClient field.

The Markdown reader is enabled by default. It accepts only relative .md paths returned by search and reads the generated source artifact under indexUrl/sources/. Set markdownReader: false to disable it, or use markdownReaderPath when files are served elsewhere. Configure markdown_reader_path on the MkDocs plugin to choose its static output directory.

provideWebsemTools({
  name: "acme-docs",
  description: "Acme documentation",
  displayName: "Acme",
  documentedName: "Acme",
  projectName: "Acme",
  searchToolName: "acme-search",
  indexUrl: "/search/",
  exampleQuestions: [],
  texts: {
    DOC_SEARCH_INSTRUCTION:
      "Search before answering Acme questions. Search is case-insensitive. Read a result's Markdown File path when its snippet is insufficient.",
    DOC_SEARCH_TOOL_DESCRIPTION:
      "Case-insensitive semantic search over Acme docs.",
    DOC_SEARCH_QUERY_DESCRIPTION:
      "Case-insensitive documentation search query.",
    DOC_NO_RESULTS: "No results for {query}.",
    DOC_SUCCESS_HEADER: "Found {count} results for {query}.",
    DOC_RESULT_NOTE: "Only use relevant results.",
  },
});

Angular API: https://angular.dev/api/core/provideExperimentalWebMcpTools