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

mcp-server-zapsign

v2.1.0

Published

Official ZapSign MCP server — remote OAuth (Cloudflare Workers) and local STDIO via npx

Readme

mcp-server-zapsign

Official ZapSign Model Context Protocol server.

Dual-mode:

  1. Remote (recommended) — Cloudflare Workers + OAuth 2.1 at https://mcp.zapsign.com.br/mcp
  2. Local STDIO — npx -y mcp-server-zapsign with ZAPSIGN_API_KEY

Package: mcp-server-zapsign · Repo: ZapSign/api-mcp

Remote install (Claude Connectors)

  1. Open Claude → Settings → Connectors → Add custom connector
  2. URL: https://mcp.zapsign.com.br/mcp
  3. Complete OAuth and paste your ZapSign API token on the authorization page (never put the token in the URL)
  4. Approve scopes and finish

Docs page: https://mcp.zapsign.com.br/docs

Agent tutorials hub

Official how-to hub for Claude, ChatGPT, Cursor, Codex, Gemini, and REST:

Local install (Claude Desktop / Cursor)

{
  "mcpServers": {
    "zapsign": {
      "command": "npx",
      "args": ["-y", "mcp-server-zapsign"],
      "env": {
        "ZAPSIGN_API_KEY": "your-zapsign-api-token",
        "ZAPSIGN_BASE_URL": "https://api.zapsign.com.br"
      }
    }
  }
}

ZAPSIGN_BASE_URL is optional (defaults to production). Use the sandbox API URL when testing against sandbox.

Tools

Core Workers names are preserved. Full union also includes webhooks, envelopes, timestamps, batch sign, and partner tools. See docs/TOOL_UNION.md.

Documents

| Tool | Purpose | |---|---| | list_documents | List/filter documents | | get_document | Document details | | create_document | Create from url_pdf, url_docx, or base64_pdf (async optional) | | update_document | Update metadata | | delete_document | Delete document | | place_signatures | Place signature fields | | add_extra_document | Attach extra PDF | | add_extra_document_from_template | Extra doc from template | | add_timestamp | Timestamp a document URL | | reorder_envelope_documents | Reorder envelope docs |

Signers / templates / webhooks / partner

| Tool | Purpose | |---|---| | add_signer / get_signer / update_signer / delete_signer | Signer CRUD | | sign_in_batch | Batch signing | | list_templates / get_template / create_from_template | Templates (async optional) | | create_webhook / delete_webhook | Webhooks | | create_webhook_header / delete_webhook_header | Webhook headers | | reprocess_documents_webhooks | Reprocess deliveries | | create_partner_account / update_partner_payment_status | Partner APIs |

Template tip: call get_template first and use exact braced strings from inputs[].variable: {{name}}, {{address}}, {{start_date}} — pass those exact braced keys as data keys to create_from_template.

Development

npm install
cp .dev.vars.example .dev.vars
npm run typecheck
npm run lint
npm test
npm run dev          # wrangler local
npm run build:stdio  # npm bin output

Opt-in sandbox integration tests (never against production):

  1. Copy test/.env.test.example → test/.env.test
  2. Set ZAPSIGN_TEST_SIGNER_EMAIL, ZAPSIGN_TEST_PDF_URL, and other sandbox fields
  3. Run npm run test:integration

See AGENTS.md for coding standards and architecture.

Migration from v1 / zapsign-mcp

  • npm v1 (1.0.4) was Express/SSE STDIO-only with different tool names → breaking in 2.0.0
  • Remote OAuth path previously lived in ZapSign/zapsign-mcp → now this repo
  • Prefer mcp.zapsign.com.br and agents.zapsign.com.br over third-party hosted proxies

Related community integrations

These are not the official server. Prefer this package, mcp.zapsign.com.br, and agents.zapsign.com.br.

| Source | Role | |---|---| | vm0-ai zapsign SKILL.md | Community curl/skill | | mcpmarket ZapSign Signature Manager | Directory listing | | mcp.ai/zapsign | Third-party hosted proxy | | @marcelocorrea/mcp-zapsign | Community npm package | | mcpbundles.com/skills/zapsign | Community bundle |

Also scan Smithery, Glama, PulseMCP, mcpservers.org, and the Anthropic Connectors Directory after cutover.

Growth metrics & analytics

Track BR search intent (Google Trends), npm downloads, and shared marketing analytics:

Live marketing analytics (Consent Mode v2 + banner; shared with agents.zapsign.com.br):

  • GA4 G-GNJFSQFD50 + Clarity xq06022ata on /docs and the /mcp browser landing only
  • Never on /authorize
  • Hosts: mcp.zapsign.com.br, mcp.zapsign.co (same Worker vars)

License

MIT © ZapSign