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

@posthubify/mcp

v0.1.2

Published

PostHubify MCP server — Claude/Cursor integration with tools auto-generated from the /v1 OpenAPI spec.

Readme

PostHubify MCP Server

Exposes the PostHubify /v1 API as a Model Context Protocol server — letting Claude Desktop, Cursor, and other MCP clients drive social media publishing, inbox, contacts, analytics, ads, and SMS/OTP operations through natural language.

  • Zero dependencies — Node standard library only (raw JSON-RPC over stdio).
  • Auto-generated tools — tools are generated at runtime from the live /v1/openapi.json spec; when a new endpoint is added, the corresponding tool appears automatically (operationId = tool name).
  • 190+ operations → 190+ MCP tools (can be narrowed with a tag filter).

Configuration

| Environment variable | Required | Description | |---|---|---| | POSTHUBIFY_API_KEY | yes | sk_… API key (from the API Keys screen) | | POSTHUBIFY_BASE_URL | no | Defaults to http://localhost:8787/v1 | | POSTHUBIFY_MCP_TAGS | no | Comma-separated tag filter, e.g. posts,inbox,contacts — if omitted, all endpoints |

Claude Desktop / Cursor setup

Add the following to claude_desktop_config.json (or your Cursor MCP settings):

{
  "mcpServers": {
    "posthubify": {
      "command": "npx",
      "args": ["-y", "@posthubify/mcp"],
      "env": {
        "POSTHUBIFY_API_KEY": "sk_...",
        "POSTHUBIFY_BASE_URL": "https://api.posthubify.com/v1"
      }
    }
  }
}

To narrow the tool surface (so it doesn't consume too much context), add POSTHUBIFY_MCP_TAGS:

"env": { "POSTHUBIFY_API_KEY": "sk_...", "POSTHUBIFY_MCP_TAGS": "posts,inbox,contacts,analytics" }

How it works

  1. At startup, BASE_URL/openapi.json is fetched → each operation becomes a tool (named by operationId, described by summary, with a combined path+query+body inputSchema).
  2. When the client sends tools/call, the arguments are split into path/query/body based on the tool metadata, forwarded to the /v1 endpoint with Bearer auth, and the response is returned as text.

Development

# Run locally (with the API open on 8787):
POSTHUBIFY_API_KEY=sk_test POSTHUBIFY_BASE_URL=http://localhost:8787/v1 npm run start --workspace @posthubify/mcp

# Tests (from root):
npx vitest run packages/mcp

License

MIT