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

nectar-ideas-mcp

v0.1.3

Published

Servidor MCP para gerenciar as ideias do módulo IDEAS (Nectar Engage)

Readme

Nectar Ideas MCP

Servidor MCP (stdio) para gerenciar as ideias do módulo IDEAS do Nectar Engage. Conversa com a API REST do app, autenticando com um Personal API Token que você gera na própria interface — sem segredos do servidor. O token herda as suas permissões, então o MCP reaproveita 100% da lógica de negócio (status, curadoria IA, merge, validações, guards).

Ferramentas

Leitura

  • check_connection — verifica conectividade + auth
  • list_boards, list_statuses, list_board_tags
  • list_ideas — busca/filtra ideias (board, status, tag, busca, esforço/impacto, nota, paginação)
  • get_idea — detalhe completo de uma ideia
  • list_triage_inbox — fila de triagem (filtro por nota de IA: com/sem)

Criação / edição

  • create_idea, update_idea

Triagem

  • set_status, set_effort_impact, set_tags, merge_ideas, delete_idea
  • bulk_action — set-status / add-tag / merge / delete em lote (1..100)

Curadoria IA

  • analyze_idea — analisa 1 ideia (síncrono)
  • start_board_ai_batch, get_board_ai_batch_progress — lote por board

Setup

Via npm (recomendado) — nada para clonar/buildar, roda via npx:

npx -y nectar-ideas-mcp   # só para testar; normalmente vai no config do Claude

Ou a partir do código:

cd mcp
npm install
npm run build

Gere seu token: no Nectar Engage, vá em Perfil → Tokens de API → Criar token. Copie o valor (nctr_…) — ele só aparece uma vez.

Crie um .env (veja .env.example):

| Var | Descrição | |---|---| | NECTAR_API_URL | URL da API (ex.: http://localhost:3080 ou prod) | | NECTAR_API_TOKEN | o token nctr_… gerado no seu perfil |

O token herda as suas permissões. Para as ferramentas de gestão (status, IA, merge…) você precisa ser content manager (editor/admin/owner). Revogue o token a qualquer momento no mesmo lugar.

Registrar no Claude Code / Desktop

No JSON de config dos MCP servers (Claude Desktop/Code):

{
  "mcpServers": {
    "nectar-ideas": {
      "command": "npx",
      "args": ["-y", "nectar-ideas-mcp"],
      "env": {
        "NECTAR_API_URL": "http://localhost:3080",
        "NECTAR_API_TOKEN": "nctr_xxxxxxxxxxxxxxxxxxxx"
      }
    }
  }
}

A partir do código (sem npm), troque por "command": "node", "args": [".../mcp/dist/index.js"], ou rode a fonte com "command": "npx", "args": ["tsx", ".../mcp/src/index.ts"].

Notas

  • Ações de escrita ficam atribuídas ao dono do token (statusHistory, autoria).
  • analyze_idea / *_ai_batch exigem ideasAiEnabled no projeto e ai.curationEnabled no board.
  • Para apontar pra produção, troque NECTAR_API_URL e gere o token no app de produção.