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

@artkit-ai/mcp

v0.2.0

Published

MCP server exposing artkit tools, artifact resources and guide prompts (stdio and streamable HTTP).

Readme

@artkit-ai/mcp

MCP server for artkit, built on @modelcontextprotocol/sdk:

  • Tools: the @artkit-ai/agent toolkit tools with the same names, descriptions and JSON Schemas.
  • Resources: artifact://{id} (outline projection of the latest version) and artifact://{id}/v/{version}.
  • Guides: every guide topic as a prompt (artkit-guide-<topic>) and as a resource artkit://guide/{topic}.
  • Transports: stdio and stateless streamable HTTP. Authentication is delegated to the host.
import { createArtifactToolkit } from '@artkit-ai/agent';
import { connectStdio, createArtkitMcpHttpHandler, createArtkitMcpServer } from '@artkit-ai/mcp';

const toolkit = createArtifactToolkit({ registry, store, assets, authorize });

// stdio (local agents)
const server = createArtkitMcpServer({
  toolkit,
  resolveScope: () => ({ workspaceId: 'local', actor: { type: 'agent', id: 'cli' } }),
});
await connectStdio(server);

// HTTP: mount the handler on your route after authenticating the request
const handle = createArtkitMcpHttpHandler({
  toolkit,
  resolveScope: (extra) => ({
    workspaceId: extra.authInfo!.extra!.workspaceId as string,
    actor: { type: 'agent', id: extra.authInfo!.clientId },
  }),
});
export async function POST(request: Request) {
  const authInfo = await verifyBearer(request); // host-specific
  return handle(request, { authInfo });
}

Notes:

  • Scope is resolved per request by resolveScope(extra); tool arguments never carry workspace or user ids. Failures to resolve it are reported without host details.
  • MCP has no stable tool call id, so idempotency uses params._meta.idempotencyKey when the client sends one (override with the idempotencyKey option).
  • Domain errors come back as tool results with isError: true and the artkit error payload; unknown tools and scope failures are protocol errors.
  • Read results carry the projection as a separate text block so it is not JSON-escaped.
  • The server sends the toolkit's compact instructions on initialize (instructions: false disables them).
  • MCP clients ask the user before running tools themselves; readOnlyHint and destructiveHint annotations help them decide.