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

@agentskit/mcp

v0.2.7

Published

Expose AgentsKit tools as an MCP server — use them from Claude Desktop, Cursor, Windsurf, or any MCP host.

Readme

@agentskit/mcp

stability

Expose AgentsKit tools as an MCP server — use them from Claude Desktop, Cursor, Windsurf, or any MCP host.

npx @agentskit/mcp --tools fetch,search

Then point your MCP host at the command. Example (Claude Desktop config):

{
  "mcpServers": {
    "agentskit": { "command": "npx", "args": ["@agentskit/mcp", "--tools", "fetch,search"] }
  }
}

Flags

| Flag | Effect | |------|--------| | --tools <a,b> | which tools to expose (default fetch,search). Available: fetch, search, filesystem, shell, sqlite | | --fs-root <dir> | enable the filesystem tool, rooted at <dir> | | --sqlite <file> | enable the sqlite query tool against <file> | | --allow-shell | enable the shell tool (off by default — it runs commands) |

stdout is the MCP JSON-RPC channel; human output goes to stderr.

Programmatic

import { createAgentsKitMcpServer } from '@agentskit/mcp'
import { fetchUrl } from '@agentskit/tools'

createAgentsKitMcpServer({ tools: [fetchUrl()] }) // stdio by default

Pass transport to use a custom MCP transport (e.g. in-memory for tests).

Expose whole agents (agents as MCP tools)

Run a registry agent server-side and expose it as a single MCP tool — the host delegates a specialized job instead of orchestrating primitives:

npx @agentskit/mcp --agents legal-contract-reviewer,fintech-kyc-screener --provider openai

--provider covers the first-class adapters (openai, anthropic, gemini, ollama) plus the OpenAI-compatible set (deepseek, grok, groq, mistral, cohere, together, fireworks, openrouter, cerebras, kimi, huggingface, qwen, lmstudio, vllm, llamacpp) and any other OpenAI-compatible provider in the models.dev catalog. Key from --api-key or <PROVIDER>_API_KEY; --model / --base-url optional.

import { createAgentTool } from '@agentskit/mcp'
createAgentsKitMcpServer({ tools: [createAgentTool({ id, description, systemPrompt, adapter })] })