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

@openmark/mcp

v1.1.1

Published

MCP server for openmark — lets AI coding agents create, read, and update markdown documents

Readme

@openmark/mcp

MCP server for openmark — lets AI coding agents create, read, and update markdown documents.

Tools

| Tool | Description | |------|-------------| | openmark_create_doc | Create a new markdown document and return its shareable URL | | openmark_read_doc | Read a document's content by slug or full URL | | openmark_update_doc | Replace the content of an existing document you own | | openmark_list_comments | List comments left on a document | | openmark_resolve_comment | Mark a comment resolved or unresolved | | openmark_delete_comment | Delete a comment on a document you own |

Setup

1. Get an API key

Sign in at openmark.cc, go to Settings → API Keys, and generate a key. It starts with omk_.

2. Add to your MCP client

Claude Code (CLI) — run once in your terminal:

claude mcp add openmark -e OPENMARK_API_KEY=omk_your_key_here -- npx -y @openmark/mcp

This writes to ~/.claude.json. Verify with claude mcp list.


Claude Desktop — edit ~/Library/Application Support/Claude/claude_desktop_config.json:

{
  "mcpServers": {
    "openmark": {
      "command": "npx",
      "args": ["-y", "@openmark/mcp"],
      "env": {
        "OPENMARK_API_KEY": "omk_your_key_here"
      }
    }
  }
}

Cursor — edit ~/.cursor/mcp.json:

{
  "mcpServers": {
    "openmark": {
      "command": "npx",
      "args": ["-y", "@openmark/mcp"],
      "env": {
        "OPENMARK_API_KEY": "omk_your_key_here"
      }
    }
  }
}

Restart your MCP client after saving.

Tool reference

openmark_create_doc

Creates a new document and returns its URL.

| Parameter | Type | Required | Description | |-----------|------|----------|-------------| | content | string | yes | Markdown content (max 500 KB) | | title | string | no | Document title (max 300 chars) |

openmark_read_doc

Reads a document by slug or full URL.

| Parameter | Type | Required | Description | |-----------|------|----------|-------------| | slug | string | yes | 7-character slug (e.g. abc1234) or full openmark URL |

openmark_update_doc

Replaces the content of a document you own.

| Parameter | Type | Required | Description | |-----------|------|----------|-------------| | slug | string | yes | 7-character slug or full openmark URL | | content | string | yes | New markdown content | | title | string | no | New title (omit to leave unchanged) |

openmark_list_comments

Lists comments on a document as a plain-text digest (one line per comment: id, resolved state, author, the anchored text it was left on — if any — and content). The anchored text lets an agent locate which part of the document a comment refers to. Available to any visitor, matching the doc's open comment-reading behavior.

| Parameter | Type | Required | Description | |-----------|------|----------|-------------| | slug | string | yes | 7-character slug or full openmark URL |

openmark_resolve_comment

Marks a comment resolved or unresolved. Not restricted to the doc owner, matching the doc's open resolve behavior. There is no tool for editing comment content — only the resolved flag can be toggled.

| Parameter | Type | Required | Description | |-----------|------|----------|-------------| | slug | string | yes | 7-character slug or full openmark URL | | commentId | string | yes | The comment id, from openmark_list_comments | | resolved | boolean | yes | true to resolve, false to unresolve |

openmark_delete_comment

Deletes a comment. Restricted to the document owner — returns a 403 error if the API key doesn't belong to the doc's owner.

| Parameter | Type | Required | Description | |-----------|------|----------|-------------| | slug | string | yes | 7-character slug or full openmark URL | | commentId | string | yes | The comment id, from openmark_list_comments |

Local development

cd mcp
npm install
npm test          # run tests once
npm run test:watch  # watch mode
npm run build     # compile TypeScript to dist/

Run the server locally against the production API:

OPENMARK_API_KEY=omk_your_key_here node dist/index.js

To test against a local worker dev server, register it in Claude Code CLI:

claude mcp add openmark-local \
  -e OPENMARK_API_KEY=omk_your_key_here \
  -e OPENMARK_BASE_URL=http://localhost:8787 \
  -- node /path/to/markdown-reader/mcp/dist/index.js

Then start the worker (npm run wrangler:dev from the repo root) and run claude mcp list to confirm it's registered.

Release workflow

Releases are triggered by pushing a mcp/v*.*.* git tag from the repo root.

  1. Make your changes inside mcp/
  2. Run tests: npm test
  3. Bump version in mcp/package.json (follow semver)
  4. Commit and tag:
    git add mcp/package.json
    git commit -m "chore: bump mcp to v1.x.x"
    git tag mcp/v1.x.x
    git push origin main --tags
  5. CI builds, type-checks, tests, and stages the package to npm
  6. Go to npmjs.com → @openmark/mcp → Staged Packages, review, and Approve (requires 2FA)

The package publishes under the latest tag once approved.