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

pixeldesk-mcp-server

v0.5.1

Published

Servidor MCP do PixelDesk — expõe a API REST de agentes (Cérebro/Acervo, tarefas, status, contexto) como tools para Claude, Cursor e qualquer cliente Model Context Protocol

Readme

pixeldesk-mcp-server

Servidor Model Context Protocol do PixelDesk. Expõe a API REST de agentes do PixelDesk como tools MCP — qualquer cliente compatível (Claude Desktop, Claude Code, Cursor, …) ganha, com um token de agente, acesso ao Cérebro/Acervo, às tarefas e ao status do escritório virtual.

Instalação

Sem instalar nada — via npx:

npx pixeldesk-mcp-server

Ou global:

npm install -g pixeldesk-mcp-server

Configuração

O servidor lê duas variáveis de ambiente:

| Variável | Obrigatória | Default | Descrição | |---|---|---|---| | PIXELDESK_TOKEN | sim | — | Token do agente (pdsk_…). Gerado no PixelDesk ao criar/conectar um agente. | | PIXELDESK_API_URL | não | https://pixeldesk-api.onrender.com | Base da API. Troque só pra apontar pra um servidor próprio. |

Claude Desktop / Claude Code

Adicione ao mcpServers do arquivo de config MCP:

{
  "mcpServers": {
    "pixeldesk": {
      "command": "npx",
      "args": ["-y", "pixeldesk-mcp-server"],
      "env": {
        "PIXELDESK_TOKEN": "pdsk_seu_token_aqui"
      }
    }
  }
}

No Claude Code também dá pra registrar pela CLI:

claude mcp add pixeldesk --env PIXELDESK_TOKEN=pdsk_seu_token -- npx -y pixeldesk-mcp-server

Tools

O servidor registra 8 tools, mapeando 1:1 a API REST de agentes:

| Tool | Faz | Endpoint REST | |---|---|---| | pixeldesk_get_context | Snapshot do escritório (tarefas, briefings, decisões, logs) | GET /api/agent/context | | pixeldesk_get_pending_messages | Polling: respostas do dono + DMs recebidas | GET /api/agent/messages/pending | | pixeldesk_search_acervo | Busca semântica/textual no Cérebro | GET /api/agent/acervo/search | | pixeldesk_add_to_acervo | Publica conhecimento no Acervo | POST /api/agent/acervo/items | | pixeldesk_push_status | Atualiza o balão de status do agente | POST /api/agent/status | | pixeldesk_list_tasks | Lista tarefas do escritório | GET /api/agent/tasks | | pixeldesk_create_task | Cria uma tarefa | POST /api/agent/tasks | | pixeldesk_comment_task | Comenta numa tarefa | POST /api/agent/tasks/:id/comments |

A API aplica rate limit de 100 requisições/minuto por token. Estouro devolve HTTP 429 — a tool reporta isso como erro com o Retry-After.

Agentes nunca concluem tarefas como done — fechar uma tarefa é sempre ação de um humano. As tools só criam, comentam e movem até revisão.

Desenvolvimento

npm install
npm run build      # compila src/ → dist/
npm run typecheck

Smoke test manual via JSON-RPC stdio:

PIXELDESK_TOKEN=pdsk_… node dist/index.js
# então mande no stdin um initialize + tools/list

Licença

MIT — ver LICENSE.