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

@agentailor/mcp

v0.2.0

Published

MCP server for Agentailor — search the blog and read articles and open-source repo docs over the Model Context Protocol.

Readme

agentailor-mcp

An MCP server that connects your AI assistant to Agentailor — search the blog, read articles in full, and pull docs from the open-source repos, all over the Model Context Protocol.

Use it with no clone required:

  • npx (local stdio) — run npx @agentailor/mcp as a command in Claude Desktop and other local clients.
  • Hosted HTTP (coming soon) — a zero-install Agentailor-hosted endpoint you point your client at.

Scaffolded with @agentailor/create-mcp-server on FastMCP — the tool building its own ecosystem.

Tools

| Tool | What it does | | ---------------------------- | ---------------------------------------------------------------------------------------------------------------------------- | | agentailor_get_blog_index | Returns the blog's content map (Markdown) — every published article with title, date, tags, summary. | | agentailor_search_articles | Ranked article search in one tool: free-text query, tags filter, guidesOnly, limit, response_format. Returns JSON. | | agentailor_read_article | Fetches a single article's full Markdown by its blog.agentailor.com .md URL. | | agentailor_list_repos | Lists the public repos in the agentailor GitHub org. Returns JSON. | | agentailor_read_repo_doc | Reads a README.md or docs/*.md from a given org repo (Markdown). |

Scope is Agentailor's public content: the blog and the open-source org repos. The list/search tools (search_articles, list_repos) return structured JSON; the content tools return raw Markdown.

Use it

npx (local stdio)

Run the server as a local command — ideal for Claude Desktop. In claude_desktop_config.json:

{
  "mcpServers": {
    "agentailor": {
      "command": "npx",
      "args": ["-y", "@agentailor/mcp"]
    }
  }
}

The repo tools read public GitHub data, so no token is required. If you hit GitHub's unauthenticated rate limit (60 requests/hour), pass a token to raise it to 5,000/hour:

{
  "mcpServers": {
    "agentailor": {
      "command": "npx",
      "args": ["-y", "@agentailor/mcp"],
      "env": { "GITHUB_TOKEN": "ghp_your_token" }
    }
  }
}

Hosted HTTP (coming soon)

A zero-install, Agentailor-hosted HTTP endpoint is planned — point any streamable-HTTP MCP client at a single URL, nothing to install or run. It isn't live yet; for now use the npx setup above. The endpoint URL will be published on agentailor.com when it's ready.

Designed to the "Writing Effective Tools for AI Agents" playbook

These tools follow the five principles from Agentailor's Writing Effective Tools for AI Agents — here's exactly how:

| Principle | How this server applies it | | ---------------------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ | | 1. Strategic selection | One agentailor_search_articles covers discovery by topic, by tag, and guides-only — instead of four fragmented search tools. Tools map to how you actually work, not to endpoints. | | 2. Clear namespacing | Every tool is prefixed agentailor_, so it never collides with other MCP servers on your client. | | 3. Meaningful context | Read tools take response_format: "concise" \| "detailed". Results carry titles, tags, and summaries you can reason on — not bare IDs. | | 4. Token efficiency + guiding errors | Search defaults to 20 results with an overflow hint that tells the agent how to narrow. A GitHub rate-limit returns "set a GITHUB_TOKEN" guidance, not a raw 403. | | 5. Descriptions as prompts | Each tool description includes a When to use section with example calls, and every parameter documents its shape with an example. |

Deploy your own HTTP instance

The HTTP transport serves the MCP endpoint at POST /mcp and a GET /health check.

Native Node host

On any platform that runs a Node web service from this repo:

  • Build command: pnpm install --frozen-lockfile && pnpm build
  • Start command: pnpm start:http
  • Health check path: /health
  • Environment:
    • GITHUB_TOKEN — a token with public read access (recommended on a shared/hosted instance; raises the GitHub limit to 5,000/hour).
    • PORT — most hosts inject this automatically; the server reads it. Defaults to 3000 if unset.

Node 20 is pinned via engines and .node-version.

Docker

A Dockerfile is included for running the server on any container host. The TRANSPORT build arg selects the entrypoint:

docker build --build-arg TRANSPORT=http -t agentailor-mcp-http .
docker run -p 3000:3000 -e GITHUB_TOKEN=ghp_your_token agentailor-mcp-http

Connect any HTTP MCP client to http://<host>:3000/mcp.

Configuration

| Variable | Required | Purpose | | --------------- | -------- | -------------------------------------------------------------------------------------------------------------------------------------------------------- | | PORT | No | HTTP transport port (default 3000). Injected by most hosts. Ignored by stdio. | | GITHUB_TOKEN | No | Raises the GitHub API limit for the repo tools from 60/hr to 5,000/hr. Any token with public read access works. Recommended on a hosted/shared instance. | | BLOG_BASE_URL | No | Override the blog origin (for local/staging testing). |

No credentials are required to run — all exposed data is public.

Develop locally (contributors)

Clone and run from source:

pnpm install
pnpm build

# stdio (local clients)
pnpm start:stdio

# HTTP on PORT (default 3000)
pnpm start:http

Dev mode with reload: pnpm dev:stdio or pnpm dev:http.

pnpm test          # Vitest unit tests
pnpm typecheck     # tsc --noEmit
pnpm format:check  # Prettier check
pnpm inspect       # MCP Inspector against the HTTP server
pnpm inspect:stdio # list tools over stdio

Releasing

The npm package publishes via GitHub Actions when a GitHub Release is published:

  1. Bump version in package.json (and src/server.ts), commit.
  2. Cut a GitHub Release / tag.
  3. The publish workflow runs the test/build gates and publishes @agentailor/mcp to npm (auth via the NPM_TOKEN repo secret).

Learn more

License

Apache 2.0 © Agentailor