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

@xmcp-dev/clerk

v0.0.2

Published

Clerk authentication integration for xmcp

Downloads

69

Readme

@xmcp-dev/clerk

Clerk authentication integration for xmcp MCP servers.

Installation

npm install @xmcp-dev/clerk

Quick Start

  1. Set up environment variables:
CLERK_SECRET_KEY=sk_...
CLERK_DOMAIN=your-app.clerk.accounts.dev

BASE_URL=http://127.0.0.1:3001 

The BASE_URL in production should be replaced with your deployed server URL.

  1. Create middleware.ts:
import { clerkProvider } from "@xmcp-dev/clerk";

export default clerkProvider({
  secretKey: process.env.CLERK_SECRET_KEY!,
  clerkDomain: process.env.CLERK_DOMAIN!,
  baseURL: process.env.BASE_URL!,
});
  1. Use in tools:
import { getSession, getUser } from "@xmcp-dev/clerk";

export default async function myTool() {
  const session = getSession();
  const user = await getUser();
  
  return `Hello ${user.firstName}! Your ID is ${session.userId}`
}

Configuration

| Option | Type | Required | Description | |--------|------|----------|-------------| | secretKey | string | Yes | Clerk Secret Key | | clerkDomain | string | Yes | Clerk Frontend API domain | | baseURL | string | Yes | Base URL of your MCP server (development: http://127.0.0.1:3001, production: your deployed URL) | | scopes | string[] | No | OAuth scopes (default: ['profile', 'email']) | | docsURL | string | No | URL to your API documentation |

Clerk Setup

  1. Go to Clerk Dashboard
  2. Create a new application or select an existing one
  3. Navigate to Configure and go to API Keys, note your :
    1. Secret Key (sk_test_ for development / sk_live_ for production)
    2. Frontend API URL (your-app.clerk.accounts.dev)
  4. Click on Development, enter to OAuth Applications and enable Dynamic Client Registration

API

clerkProvider(config)

Creates the middleware and router for Clerk authentication.

getSession()

Returns the current user's session data.

getUser()

Fetches the full user profile from Clerk's.

getClient()

Returns the Clerk Backend SDK client.

Documentation

For full documentation, visit xmcp Clerk Plugin.

Contributing

See the main xmcp repository for contribution guidelines.

Questions

For help, use Discord. For security issues, email [email protected].