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

@forgedevstack/forge-mcp

v1.0.0

Published

Tiny helper for building API-key stdio MCP servers: typed tools with plain JSON schemas, one-call setup.

Readme

@forgedevstack/forge-mcp

Tiny helper for building API-key-protected stdio MCP servers. Wraps the official @modelcontextprotocol/sdk so you define tools with plain JSON schemas — no zod, no boilerplate — and get a working server with one call.

Part of the ForgeStack family of libraries.

Install

npm install @forgedevstack/forge-mcp

A working MCP server in under 20 lines

import { createMcpServer, textResult } from '@forgedevstack/forge-mcp';

const { start } = createMcpServer({
  name: 'my-server',
  version: '1.0.0',
  apiKey: { envVar: 'MY_API_KEY' },
  tools: [
    {
      name: 'echo',
      description: 'Echo a message',
      inputSchema: { type: 'object', properties: { message: { type: 'string' } }, required: ['message'] },
      handler: (args) => textResult(String(args.message)),
    },
  ],
});

start();

API

createMcpServer(options): ForgeMcpServer

| Option | Type | Description | |---|---|---| | name | string | Server name reported to MCP clients | | version | string | Server version reported to MCP clients | | tools | McpToolDefinition[] | Tools exposed via tools/list and tools/call | | apiKey | ApiKeyConfig (optional) | API key resolution; omit if no key is needed |

Returns { server, apiKey, start }:

  • server — the underlying SDK Server instance for advanced use
  • apiKey — the resolved API key (pass it to your API clients inside handlers)
  • start() — connects a StdioServerTransport and begins serving

The API key is resolved eagerly, so a misconfigured server fails fast at startup instead of on the first tool call.

Tool definition

interface McpToolDefinition {
  name: string;
  description: string;
  inputSchema: JsonSchema;
  handler: (args: Record<string, unknown>) => Promise<McpToolResult> | McpToolResult;
}

inputSchema is a plain JSON schema object (type, properties, required, items, enum, ...). Handler exceptions are caught and returned as isError results, and calls to unknown tool names return an isError result instead of crashing the server.

API key config

interface ApiKeyConfig {
  envVar?: string;
  value?: string;
  required?: boolean;
}

Precedence: value first, then process.env[envVar] (default env var: MCP_API_KEY). When apiKey is passed and the key is missing, createMcpServer throws unless required: false.

Helpers

  • textResult(text){ content: [{ type: 'text', text }] }
  • errorResult(text) — same, with isError: true
  • resolveApiKey(config) — standalone key resolution, same rules as above
  • DEFAULT_API_KEY_ENV_VAR'MCP_API_KEY'

Wiring into an MCP client

Point your MCP client (Cursor, Claude Desktop, etc.) at your server script and pass the key through env:

{
  "mcpServers": {
    "my-server": {
      "command": "node",
      "args": ["/path/to/my-server.js"],
      "env": { "MY_API_KEY": "your-key-here" }
    }
  }
}

License

MIT