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

@alvin0/ai-agent-sdk-mcp

v0.1.0

Published

Universal MCP HTTP client for ai-agent-sdk

Readme

@alvin0/ai-agent-sdk-mcp

Runtime: Universal (Edge/Worker, browser, Deno, Bun, and Node).

pnpm add @alvin0/ai-agent-sdk-core @alvin0/ai-agent-sdk-mcp

Universal MCP client for Fetch-shaped HTTP runtimes. It connects remote MCP servers to the SDK as a versioned ToolSource.

import { createAgentRuntime } from '@alvin0/ai-agent-sdk-core'
import { connectMcpHttp } from '@alvin0/ai-agent-sdk-mcp'

const runtime = await createAgentRuntime({ providers: [modelProvider] })
let connection: Awaited<ReturnType<typeof connectMcpHttp>> | undefined
try {
  connection = await connectMcpHttp({
    serverName: 'tools',
    url: 'https://tools.example.com/mcp',
    logger: runtime.logger({ fields: { integration: 'mcp-http' } }),
  })
  const agent = runtime.agent({ model, toolSources: [connection] })
  await agent.generate('Use the connected tools when needed.')
} finally {
  try {
    await runtime.close()
  } finally {
    await connection?.closeWithReport()
  }
}

The normal root and /client route contain no server, stdio, filesystem, node:http, or process lifecycle integration. Use @alvin0/ai-agent-sdk-mcp-node for the Node stdio client, and a dedicated server package for hosting.

HTTP endpoints are host-selected. HTTPS, public-network-only access, and no redirects are the defaults; local development must opt out explicitly. Use allowedOrigins, the async validateEndpoint hook, a DNS-pinning custom fetch or network egress policy, response/catalog/result bounds, and operation deadlines according to the application's trust boundary. OAuth credential persistence and redirect handling remain caller-owned.

Composition: runtime-agent.toolSources. Lifecycle: connected-caller-owned; create the runtime first, pass runtime.logger(...) while connecting, close the runtime to quiesce runs, then inspect connection.closeWithReport().