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

agentmail-mcp

v1.1.0

Published

stdio compatibility bridge for the hosted AgentMail MCP server

Readme

agentmail-mcp

agentmail-mcp is the supported stdio compatibility bridge for the canonical hosted AgentMail MCP server at https://mcp.agentmail.to/mcp. It loads tools and schemas from that server at runtime; it does not contain a separate AgentMail tool implementation.

Prefer connecting an MCP client directly to the hosted endpoint when it supports Streamable HTTP. For stdio-only clients:

{
    "mcpServers": {
        "AgentMail": {
            "command": "npx",
            "args": ["-y", "agentmail-mcp"],
            "env": {
                "AGENTMAIL_API_KEY": "YOUR_API_KEY"
            }
        }
    }
}

To expose only selected remote tools, add "--tools", "list_inboxes,send_message" to args. The API key is sent to the hosted server as x-api-key and is never written to stdout.

Sending local attachments

Start the bridge with --file-root /absolute/path/to/project to let attachment-capable tools accept a local path in addition to base64 content or a public url:

{
  "mcpServers": {
    "agentmail": {
      "command": "npx",
      "args": ["-y", "agentmail-mcp", "--file-root", "/absolute/path/to/project"],
      "env": { "AGENTMAIL_API_KEY": "your-api-key" }
    }
  }
}

Then an agent can send a file without placing its bytes in the tool call:

{
  "inboxId": "[email protected]",
  "to": ["[email protected]"],
  "subject": "Document",
  "attachments": [
    {
      "path": "documents/report.pdf",
      "contentType": "application/pdf"
    }
  ]
}

The bridge reads and base64-encodes the file locally, then forwards the standard AgentMail tool call. This keeps file bytes out of the model's tool arguments. Paths may be absolute or relative, but must resolve inside the configured file root; symlinks cannot escape it. Hidden files and directories (including .env, .git, and .npmrc) are denied. Local attachments have a 6 MiB combined decoded-size limit. Without --file-root, the bridge exposes the hosted tool contract unchanged and cannot read local files.

Choose the narrowest directory that contains the files you intend to attach. Do not use your home directory or a project directory containing secrets. --file-root limits what this bridge can read; it does not sandbox an agent that has access to other filesystem or shell tools.

See the AgentMail MCP documentation for direct connection and migration guidance.