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

@un4gt/grok-search

v0.1.0

Published

Rust Grok MCP server with stdio, streamable HTTP, and legacy SSE compatibility transports

Readme

grok-search

Rust rewrite of the grok-with-tavily MCP server using the official modelcontextprotocol/rust-sdk.

Status

  • Transport:
    • stdio: implemented and intended as the default for Claude Code, Codex, and Gemini CLI
    • streamable HTTP at /mcp: implemented
    • legacy SSE compatibility paths /sse and /messages: implemented for older MCP SSE clients
  • Tools:
    • implemented: web_search, get_sources, web_fetch, web_map, get_config_info, switch_model, toggle_builtin_tools, all plan_* tools
  • Migration:
    • ~/.config/grok-search/config.json is preserved
    • GUDA_* is still accepted as a deprecated runtime fallback, but is no longer documented

Verified Locally

  • cargo check: passed
  • cargo test: passed
  • cargo install --path . --root /tmp/grok-search-install: passed

The npm package name and cargo-dist metadata are in place, but the package has not been published to npm or crates.io yet.

Install

Cargo

cargo install --path .

Planned release install:

cargo install grok-search

NPX

Current local wrapper:

node npm/run.js

Planned published package name:

npx -y @un4gt/grok-search

Configuration

Required:

  • GROK_API_URL
  • GROK_API_KEY

Optional:

  • GROK_MODEL
  • TAVILY_ENABLED
  • TAVILY_API_URL
  • TAVILY_API_KEY
  • FIRECRAWL_API_URL
  • FIRECRAWL_API_KEY
  • GROK_DEBUG
  • GROK_LOG_LEVEL
  • GROK_LOG_DIR
  • GROK_RETRY_MAX_ATTEMPTS
  • GROK_RETRY_MULTIPLIER
  • GROK_RETRY_MAX_WAIT

Run

STDIO

grok-search

HTTP

grok-search http --bind 127.0.0.1:8000

The MCP endpoint is http://127.0.0.1:8000/mcp.

Health probe:

curl http://127.0.0.1:8000/health

Agent Setup

Claude Code

Unix-like systems:

{
  "type": "stdio",
  "command": "npx",
  "args": ["-y", "@un4gt/grok-search"],
  "env": {
    "GROK_API_URL": "https://your-api-endpoint.com/v1",
    "GROK_API_KEY": "your-grok-api-key"
  }
}

Native Windows:

{
  "type": "stdio",
  "command": "cmd",
  "args": ["/c", "npx", "-y", "@un4gt/grok-search"],
  "env": {
    "GROK_API_URL": "https://your-api-endpoint.com/v1",
    "GROK_API_KEY": "your-grok-api-key"
  }
}

Codex

Use npx on Unix-like systems or a direct binary path on Windows in ~/.codex/config.toml.

Gemini CLI

Add the server under mcpServers in ~/.gemini/settings.json, again preferring npx on Unix-like systems and the built binary on Windows.

Docker

Build:

docker build -t grok-search:local .

Run as a remote MCP server over streamable HTTP:

docker run --rm -p 8000:8000 \
  -e GROK_API_URL=https://your-api-endpoint.com/v1 \
  -e GROK_API_KEY=your-grok-api-key \
  grok-search:local

Then connect clients to:

http://127.0.0.1:8000/mcp

Compose:

docker compose up --build

For local same-machine agent integration, Docker can also be used with stdio, but that requires docker run -i and is less ergonomic than running the native binary directly.

Verify

cargo check
cargo test