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

@semacode/mcp

v1.4.0

Published

Servidor MCP da Sema que expoe validacao, drift, contexto IA e fluxo vendor-first de persistencia como ferramentas para agentes.

Readme

@semacode/mcp

@semacode/mcp expoe a Sema como servidor MCP para Claude Code, Cursor, VS Code, Cline e clientes compativeis.

Ele usa a CLI da Sema como backend operacional. Instale a CLI antes ou junto:

npm install -g @semacode/cli @semacode/mcp

Tambem funciona sem instalacao previa da ferramenta MCP:

npx -y @semacode/mcp

Ferramentas expostas

  • sema_validar
  • sema_ir
  • sema_drift
  • sema_resumo
  • sema_prompt_ia
  • sema_contexto_ia
  • sema_verificar
  • sema_inspecionar

Essas ferramentas acompanham a linha publica atual da Sema, incluindo persistencia vendor-first para postgres, mysql, sqlite, mongodb e redis.

Configuracao no Claude Code

{
  "mcpServers": {
    "sema": {
      "command": "npx",
      "args": ["-y", "@semacode/mcp"]
    }
  }
}

Configuracao no Cursor, VS Code ou Cline

{
  "mcpServers": {
    "sema": {
      "command": "npx",
      "args": ["-y", "@semacode/mcp"]
    }
  }
}

Rodando localmente pelo repo

{
  "mcpServers": {
    "sema": {
      "command": "node",
      "args": ["C:/GitHub/Sema/pacotes/mcp/dist/index.js"]
    }
  }
}

Modo stdio e modo HTTP

  • padrao: stdio, ideal para uso local com agentes
  • remoto: defina MCP_PORT para expor /mcp e /sse

Exemplo:

MCP_PORT=3333 npx -y @semacode/mcp

Observacoes

  • o servidor MCP resolve sema pelo PATH do sistema
  • sema_verificar usa o diretorio do projeto informado como cwd, evitando escrever artefatos no lugar errado
  • para reproduzibilidade, mantenha @semacode/cli e @semacode/mcp na mesma versao