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

merkl-mcp

v0.1.9

Published

MCP server exposing Merkl opportunities via @modelcontextprotocol/sdk

Downloads

13

Readme

Merkl MCP Server

An MCP server exposing Merkl Opportunities endpoints using @modelcontextprotocol/sdk.

Setup

  • Node.js 18+ recommended
  • Install deps
npm install

Optionally set environment variables:

  • MERKL_BASE_URL (default: https://api.merkl.xyz)
  • MERKL_API_KEY (Bearer token if you have one; public endpoints work without it)

Run (local)

  • Dev server:
npm run dev
  • Start once:
npm run build
npm start
  • Smoke test (direct HTTP call, not MCP):
npm run smoke

Tools exposed

  • opportunities-search
  • opportunities-get
  • opportunities-campaigns
  • opportunities-count
  • opportunities-bins-apr
  • opportunities-bins-tvl
  • opportunities-aggregate
  • opportunities-aggregate-max
  • opportunities-aggregate-min

Use with an MCP-compatible client

This server uses the stdio transport. Point your MCP client to run the command and read/write on stdio:

  • Command:
npx merkl-mcp
  • Or locally via repo:
npm start

Set env vars as needed (e.g. MERKL_API_KEY). The server will register tools listed above.

Note: Requires Node 18+. Enable debug logs by setting MERKL_DEBUG=1.

One-line npx startup

After publishing as merkl-mcp to npm (or using npm link), you can start the server with:

npx merkl-mcp

If dist/server.js is missing, the CLI will build automatically on first run.

Connect to Claude Desktop (macOS)

Claude Desktop supports MCP over stdio. Add this server to Claude's config and restart the app.

  1. Create or edit config file
  • Path: ~/Library/Application Support/Claude/claude_desktop_config.json
  1. Use the published package (one-line npx)
{
  "mcpServers": {
    "merkl": {
      "command": "npx",
      "args": ["-y", "merkl-mcp"],
      "env": {
        "MERKL_API_KEY": "(Optional) YOUR_API_KEY_OR_REMOVE_IF_UNUSED"
      }
    }
  }
}
  1. Or run from local repo
{
  "mcpServers": {
    "merkl": {
      "command": "node",
      "args": ["dist/src/server.js"],
      "cwd": "./merkl-mcp",
      "env": {
        "MERKL_API_KEY": "(Optional) YOUR_API_KEY_OR_REMOVE_IF_UNUSED"
      }
    }
  }
}
  1. Restart Claude Desktop
  • Start a new chat; the tool named merkl should appear in the Tools list.

Troubleshooting

  • Ensure Node.js 18+ is installed and available to Claude's environment.
  • Remove MERKL_API_KEY if you don't have one; public endpoints work without it.
  • Check Claude logs if tools don't appear; verify the config file path and JSON syntax.

Publish to npm

Set the name in package.json (already set up for you via bin aliases) and publish:

npm login   # if not already
npm publish --access public

Then users can run:

npx merkl-mcp
# or the short alias
npx merkl-mcp