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

@sanity/context-eve

v0.1.0

Published

Sanity Context for eve agents

Readme

@sanity/context-eve

Sanity Context for eve agents. This extension connects an eve agent to a Sanity Context MCP endpoint, so it can answer from your Sanity content.

The agent gets the endpoint's current tools on every run, so changes to the endpoint's sources in the Context app reach it without a redeploy. The extension's instructions tell the model to load the initial context before it uses the connection.

Install

npm install @sanity/context-eve

Requires eve 1.0 or later and Node.js 24 or later.

Mount it

// agent/extensions/sanity-context.ts
import sanityContext from '@sanity/context-eve'

export default sanityContext({
  url: process.env.SANITY_CONTEXT_MCP_URL!,
  token: process.env.SANITY_ORGANIZATION_TOKEN!,
  description: "Acme's product catalog and support articles.",
})

| Option | Description | | ------------- | ------------------------------------------------------------------------------------------------------------- | | url | The Context MCP endpoint URL. Must use https. | | token | An organization API token with Context access. Keep it server-side. | | description | What the endpoint's content covers. The model reads it to decide when to use this connection, so be specific. |

eve reads the extension's configuration when it builds the agent, so set the environment variables in the build environment too.

Notes

  • eve shows a connection's tools to the model only after it searches for them. Tool names start with the mount's file name, so this example's tools are sanity-context__sanity__initial_context, sanity-context__sanity__groq_query, and so on.
  • If the token is rejected, eve tells the model the connection needs authorization, and the run doesn't fail. The agent then answers without Sanity Context.
  • Tool results contain your content, so anyone who can edit that content can influence what the agent does.

See the Sanity Context guide for eve for setting up an endpoint and a token.