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

@soltein-net/solt-helpdesk-mcp

v0.1.1

Published

Thin MCP stdio shim wiring core-lib's helpdesk operations to @modelcontextprotocol/sdk. Only package in this repo that depends on the MCP SDK — see docs/approved/ide-helpdesk/SPEC.md Code Style.

Readme

mcp-server

Test Lint

Thin MCP stdio shim over core-lib's curated helpdesk operations (SPEC §2.3, docs/approved/ide-helpdesk/SPEC.md in the soltein repo). No business logic lives here — every tool validates its input (zod) and dispatches straight to the matching core-lib function.

Runs standalone, independent of the VS Code extension and its SecretStorage-backed auth — see SPEC §2.4 and Success Criterion 7/8.

Configuration

Reads its Odoo connection from environment variables (never from VS Code's SecretStorage, never committed anywhere):

| Variable | Example | |---|---| | SOLT_HELPDESK_ODOO_URL | http://localhost:9069 | | SOLT_HELPDESK_ODOO_DB | odoo_server_17 | | SOLT_HELPDESK_ODOO_LOGIN | [email protected] | | SOLT_HELPDESK_ODOO_API_KEY | a standard Odoo API key from your own user's Account Security preferences |

All four are required — the server exits with a clear error listing whichever are missing.

Installing

Published to GitHub Packages as @soltein-net/solt-helpdesk-mcp, not the public npm registry. One-time setup (needs a GitHub PAT with read:packages scope):

npm login --scope=@soltein-net --registry=https://npm.pkg.github.com
npm install -g @soltein-net/solt-helpdesk-mcp --registry=https://npm.pkg.github.com

The global install exposes it on your PATH as solt-helpdesk-mcp (this package's own bin entry) — no need to know or reference its node_modules path anywhere below.

Running standalone

SOLT_HELPDESK_ODOO_URL=... SOLT_HELPDESK_ODOO_DB=... \
SOLT_HELPDESK_ODOO_LOGIN=... SOLT_HELPDESK_ODOO_API_KEY=... \
solt-helpdesk-mcp

It speaks MCP over stdio — nothing to see on its own; connect an MCP host or client.

Registering with an MCP host

Claude Desktop (claude_desktop_config.json) / Claude Code CLI (claude mcp add) / any other stdio-based MCP host — point command at the globally-installed binary, no args needed:

{
  "mcpServers": {
    "solt-helpdesk": {
      "command": "solt-helpdesk-mcp",
      "env": {
        "SOLT_HELPDESK_ODOO_URL": "http://localhost:9069",
        "SOLT_HELPDESK_ODOO_DB": "odoo_server_17",
        "SOLT_HELPDESK_ODOO_LOGIN": "[email protected]",
        "SOLT_HELPDESK_ODOO_API_KEY": "..."
      }
    }
  }
}

PyCharm's AI Assistant (Settings → Tools → AI Assistant → Model Context Protocol → Add): command solt-helpdesk-mcp, no arguments, same four environment variables set in its own env var fields.

VS Code's Copilot agent mode: handled automatically by solt-vscode-helpdesk's own McpServerProvider (Task 14) if you're using the extension — nothing to configure by hand there.

Tools

One per core-lib operation: list_my_issues, search_issues, get_issue, add_issue_note, create_problem, get_problem, update_problem, advance_problem_stage, list_issue_transitions, change_issue_stage, resolve_issue, close_issue, reopen_issue, create_issue. Each tool's description and input schema are self-documenting via tools/list.