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

@grackle-ai/mcp-stdio

v0.118.0

Published

stdio-to-HTTP MCP proxy for Grackle — bridges stdio-only MCP clients (Claude Desktop, Codex CLI, Clawpilot) to a Grackle HTTP MCP server using static API-key auth

Readme

@grackle-ai/mcp-stdio

stdio-to-HTTP MCP proxy for Grackle. Bridges MCP clients that only speak stdio (Claude Desktop, Codex CLI, Clawpilot) to a running Grackle HTTP MCP server using static API-key auth — no OAuth flow required.

Quick Start

Add to your MCP client config:

{
  "grackle": {
    "command": "npx",
    "args": ["-y", "@grackle-ai/mcp-stdio"],
    "env": {
      "GRACKLE_URL": "http://127.0.0.1:7435/mcp",
      "GRACKLE_API_KEY": "<your-api-key>"
    }
  }
}

Or run directly:

GRACKLE_URL=http://127.0.0.1:7435/mcp GRACKLE_API_KEY=<key> npx @grackle-ai/mcp-stdio

Requires Node.js >= 22.

Configuration

| Variable | Description | Default | | --- | --- | --- | | GRACKLE_URL | Full URL of the Grackle MCP HTTP endpoint | http://127.0.0.1:7435/mcp | | GRACKLE_API_KEY | API key for authenticating with the Grackle server. Required — the proxy exits with an error if not set. | (none) |

The API key is the 64-character hex token stored in ~/.grackle/api-key on the machine running the Grackle server. For a Docker deployment, see the section below.


Docker Quick Start

The published Grackle image exposes the MCP port (7435) by default when using the provided docker-compose.yml:

# Start Grackle
docker compose up -d

# Read the API key from the container's volume
docker exec grackle cat /data/.grackle/api-key

Then use the key in your MCP client config as shown above, with GRACKLE_URL=http://127.0.0.1:7435/mcp.

Multi-tenant hosts: The default docker-compose.yml binding exposes port 7435 on all interfaces. To restrict to loopback, change the port mapping to "127.0.0.1:7435:7435" in your compose file.


How It Works

@grackle-ai/mcp-stdio spawns a local stdio MCP server that forwards every tools/list and tools/call request to the Grackle HTTP MCP server over Streamable HTTP. Tool discovery is fully dynamic — the proxy calls listTools upstream on every request so new Grackle tools are automatically available without updating the proxy.

On any network error the proxy reconnects once before propagating the failure. No OAuth flow, no token expiry.


License

MIT