zSign

MCP办公协作

提供方 未标注

办公协作 HTTP · 远程 API Key 官方维护 Claude DesktopClaudeCursorVS Code
查看接入方式

从 AI 助手发送文档以进行电子签名,跟踪签署人,并下载已密封签署的 PDF。

一句话选型结论

按资料字段整理

zSign 属于办公协作类 MCP 服务器,HTTP · 远程,API Key,可直接接入 Claude Desktop、Claude、Cursor 等,有可直接复制的远程端点配置。接入前先确认权限范围;涉及写入、删除或付款的操作,建议先在测试环境验证。

分类办公协作 传输方式HTTP · 远程 鉴权API Key 部署方式支持远程部署
GitHub 星标 未标注 仓库热度,无公开仓库时显示未标注
工具数 未标注 暴露给模型的工具数量
资源 / 提示词 0 / 0 资源与提示词模板数量
维护方 官方维护 核验等级 仅资料核对

工具与能力

办公协作
数量来自来源目录的标注,具体工具清单以官方文档为准
工具数量未标注暴露给模型可调用的工具个数
资源数量0可读取的资源条目
提示词数量0内置提示词模板数量

能力标签

支持客户端

适用场景

生产力

安装与配置

HTTP · 远程 API Key
连远程 HTTPS 端点,通常为 Streamable HTTP
npx add-mcp 'https://zsign.io/mcp'

这条命令只是入口,具体启动参数请按官方文档补齐,不要直接照搬到别的服务器。

  1. 1
    准备运行环境

    确认你的客户端支持远程端点,并拿到服务地址。

  2. 2
    安装服务

    复制上面的安装命令执行;命令里带占位符的位置,换成自己的密钥或路径。

  3. 3
    写入客户端配置

    在客户端的 MCP 配置里填好启动命令和参数,保存后完全退出客户端再打开,让新配置生效。

  4. 4
    验证是否可用

    连接成功后随便调一个只读工具,确认能返回结果,再接入正式流程。

典型使用场景

3 类
按分类与标签整理的常见用法,具体以官方文档为准
日程与消息

查日程、发消息、约会议。

表单与审批

填表单、走审批流。

团队协作

同步任务、汇总进展。

选择建议

选之前先看这几条
按条目字段给出的判断,不替你决定用不用

值得选的地方

  • 有现成的安装命令,不用自己找入口,照着跑就能起服务。
  • 已适配 Claude Desktop、Claude、Cursor,换客户端不用重新研究配置。

先想清楚的地方

  • 远程端点依赖网络与服务方可用性,注意密钥与调用额度。
  • 使用前要准备好API Key对应的凭据,并按最小权限配置。
  • 资料没标注工具数量,实际能力要装好后确认。
  • 版本更新与行为细节以官方仓库为准。

更适合

  • 需要在办公协作场景里让模型直接调用外部能力的人。
  • 已经在用 Claude Desktop、Claude 的用户,接入路径最短。
  • 想先快速试一下、能接受在本地或自有环境跑服务的人。

不太适合

  • 不方便管理密钥或第三方授权的人。
  • 需要厂商级 SLA 和技术支持的生产环境。

同类对比

6 个同类
同分类里挑最接近的几条,字段以各自详情页为准
MCP 服务器工具数传输方式部署方式安装命令最后核验
zSign当前 未标注 HTTP · 远程 支持远程部署 有 2026-11-20
CowAgent 未标注 stdio · 本地进程 本地部署 有 2026-04-11
Karakeep MCP 未标注 未标注 未标注 无 2026-05-17
agentscope 未标注 stdio · 本地进程 本地部署 有 2026-04-11
note-gen 未标注 stdio · 本地进程 本地部署 有 2026-04-11
Everywhere 未标注 stdio · 本地进程 本地部署 有 2026-04-12

服务器档案

办公协作
字段来自项目仓库与公开索引,中文说明由本站标注
提供方未标注上游标注的维护方 未标注
分类办公协作本站按上游分类展示
连接方式HTTP · 远程连远程 HTTPS 端点,通常为 Streamable HTTP
鉴权方式API Key远程服务建议用最小权限凭据
维护方官方维护核验等级 仅资料核对
包名 / 运行时未标注 · 未标注本地安装时用到的包标识与运行时
部署类型支持远程部署上游给出的部署形态
最近核验2026-11-20上游最后核验时间

详细介绍

8.9 KB
来自项目仓库与上游目录的原文,未做删改

@zsign/convex

zSign e-signature component for Convex. An app installs this component to send a
document for signature, observe envelope progress reactively, run completion
callbacks, and retrieve the signed PDF + completion certificate when done.

Published on npm as @zsign/convex.
example/ is the minimal authenticated demo app it was proven with.
Agent-facing install/use guide: SKILL.md.

Install```bash

npm install @zsign/convex
``````ts
// convex/convex.config.ts
import { defineApp } from "convex/server";
import zsign from "@zsign/convex/convex.config.js";

const app = defineApp();
app.use(zsign, {
env: {
ZSIGN_API_KEY: process.env.ZSIGN_API_KEY,
ZSIGN_API_BASE_URL: process.env.ZSIGN_API_BASE_URL,
ZSIGN_WEBHOOK_SECRET: process.env.ZSIGN_WEBHOOK_SECRET,
ZSIGN_WEBHOOK_SECRET_PREVIOUS: process.env.ZSIGN_WEBHOOK_SECRET_PREVIOUS,
},
});
export default app;


## Env (component, declared in convex.config.ts)

- `ZSIGN_API_KEY` (required) — `zs_live_…`/`zs_test_…` org key.
- `ZSIGN_API_BASE_URL` (optional) — defaults to `https://zsign.io`. An origin;
  a trailing `/api` or `/api/v1` (as the zSign API docs write it) is stripped.
- `ZSIGN_WEBHOOK_SECRET` (optional) — `whsec_…`; required to verify webhook
  signatures.
- `ZSIGN_WEBHOOK_SECRET_PREVIOUS` (optional) — previous `whsec_…`, accepted in
  parallel during secret rotation.

## App usage```ts
import { Zsign } from "@zsign/convex";
import { components } from "./_generated/api";

const zsign = new Zsign(components.zsign);

// Action: send. operationId is your idempotency/correlation key — replays
// return the stored result instead of creating a second envelope.
await zsign.send(ctx, {
  file, filename: "proposal.pdf",
  recipients: [{ name, email, role: "client", signingOrder: 1 }],
  operationId, // required; also sent as the HTTP Idempotency-Key
  metadata: { dealId: "..." }, // strings only; zsign.* keys are reserved
});
// -> { documentId, sessionId, signingUrls, replayed? }

// Queries: reactive reads (subscribe from UI or use in other functions)
await zsign.status(ctx, operationId); // envelope + recipients + completion ids
await zsign.list(ctx, { activeOnly: true }); // non-terminal envelopes

// Actions: canonical sync + artifacts
await zsign.refresh(ctx, operationId); // force a GET against the zSign API
await zsign.getSignedPdf(ctx, completedDocumentId); // -> ArrayBuffer
await zsign.getCertificate(ctx, documentId);        // -> ArrayBuffer

Webhooks

Component http routes did not mount on the self-hosted backend this was built
against, so the app wires one route itself using the shipped verifier:```ts
// convex/http.ts
import { httpRouter } from "convex/server";
import { verifyWebhookRequest } from "@zsign/convex";
import { internal } from "./_generated/api";

const http = httpRouter();
http.route({
path: "/zsign/webhook",
method: "POST",
handler: httpAction(async (ctx, request) => {
const res = await verifyWebhookRequest(request, [
process.env.ZSIGN_WEBHOOK_SECRET,
process.env.ZSIGN_WEBHOOK_SECRET_PREVIOUS,
]);
if (!res.ok) return new Response(res.error, { status: res.status });
try {
await ctx.runMutation(components.zsign.lib.applyWebhookEvent, res.event);
} catch {
return new Response("webhook receipt unavailable", { status: 503 });
}
return new Response("ok", { status: 200 });
}),
});
export default http;


Verified signature (`X-Webhook-Signature: t=…,v1=…`, HMAC-SHA256 over
`t.{raw_body}`, 300s tolerance, either current or previous secret) happens
before any mutation; unknown `X-Webhook-Id`s are deduped; unknown sessions are
persisted as orphaned events and replayed onto the envelope if it appears
later. A receipt failure returns 503 so zSign retries delivery.

## Completion callbacks```ts
// internal mutation the app owns
export const onEnvelopeCompleted = internalMutation({
  args: {
    callbackId: v.string(), operationId: v.string(), sessionId: v.string(),
    documentId: v.string(), completedDocumentId: v.string(),
    metadata: v.record(v.string(), v.string()),
  },
  handler: async (ctx, args) => { /* advance your workflow */ },
});

// drain (e.g. from a cron action)
await zsign.onCompleted(ctx, internal.myFunctions.onEnvelopeCompleted);

Handlers are mutations. Each (envelope, kind) callback is deduped and
persisted; a handler that throws stays failed with lastError and is retried
by the next drain — at-least-once, not exactly-once.

Reconciliation

Webhook-driven state is guarded by generation + status rank; on a conflict
(out-of-order or inconsistent event) the component schedules
reconcile.refreshEnvelope, which fetches GET /api/v1/documents/{id} and
applies canonical state only if the generation still matches, with bounded
backoff. terminal envelopes are never refreshed. lastSyncedAt / syncError
surface per-envelope health; zsign.refresh(ctx, operationId) forces a manual
sync.

Verified end-to-end (2026-09-14)

Stack: self-hosted ghcr.io/get-convex/convex-backend (docker, :3210/:3211),
local zSign backend (:7101, local Postgres + local_gcs_uvicorn.py), webhook
http://127.0.0.1:3211/zsign/webhook.

  1. Send — component action builds multipart manually (Convex runtime's
    FormData drops Blob MIME; zSign 422s without application/pdf), POSTs with
    Idempotency-Key = operationId. Tags {signature*:client} auto-assign to
    role: "client".
  2. Webhooks → reactive status — all lifecycle events delivered, 200 each;
    status completed with completedDocumentId (the completed doc's id —
    document.completed's data.document_id is NOT the original).
  3. Callbacks — document.completed persisted an onCompleted callback; a
    failing drain recorded lastError, and the next drain retried it to
    succeeded. The example app's completions row was written by its own
    internalMutation handler.
  4. Artifacts — signed PDF (tags redacted, signature stamped) and
    certificate both return bytes through component actions.
  5. Signature verification — good sig → applied; replayed X-Webhook-Id →
    "duplicate"; bad sig / stale t → 401; ZSIGN_WEBHOOK_SECRET_PREVIOUS
    accepted.
  6. Replay — send twice with the same operationId → {replayed: true, same documentId}; with PR #393's Idempotency-Key the upstream call also
    collapses to one envelope + one debit.
  7. Auth wrappers (example) — token-authenticated sendEnvelope /
    envelopeStatus / listEnvelopes / refreshEnvelope / artifact fetches;
    bad token → unauthenticated, wrong tenant → not found.
  8. Packed artifact — npm pack → installed into a clean app dir →
    convex codegen + tsc clean, Zsign client types resolve.

Failure semantics

  • Webhook receipt: verify → dedupe → persist. Unknown envelope → orphaned
    row, re-attached on insertEnvelope by sessionId.
  • Send: operation allocated before the HTTP call; a network/5xx failure marks
    it failed and a retry re-sends; a sent op short-circuits to the stored
    result.
  • Reconcile: generation guard drops stale applies; bounded backoff then stops.
  • Callbacks: deduped, persisted, failure-visible, retryable — at-least-once.

zSign has no staging environment, so external-email checks used a dedicated,
clearly labeled live account (signup → 0 credits, email verify grants 3, one
send debits exactly 1, invitation delivered).

Agent plugin pack

This repo also ships the zSign agent plugin pack at the root — the same files
Cursor uses to connect to the remote MCP server. They are not part of the npm
package (files limits the tarball to src/, docs/, SKILL.md,
CHANGELOG.md).

  • plugin.json — Agent Plugins 1.0.0 manifest
  • mcp.json — remote Streamable HTTP MCP server at https://zsign.io/mcp
    (OAuth 2.1 with Dynamic Client Registration; no API key header once OAuth
    completes, no secret stored in the pack)
  • .cursor-plugin/plugin.json — Cursor logo and homepage (Agent Plugins
    plugin.json has no logo field)
  • assets/logo.svg — copied from frontend/public/favicon.svg

Prepaid credits, no seats: Starter $27/50 · Growth $87/250 · Scale $297/1000 ·
White-label $49/mo.

MCP directory manifest

lhm.plugin.json lists the remote zsign MCP server (https://zsign.io/mcp) on
LobeHub MCP. Its tools array is the live catalog,
captured from the public inspection endpoint because /mcp itself needs OAuth:bash mkdir -p /tmp/lhm && echo '{"description":"zsign"}' > /tmp/lhm/package.json npx @lobehub/market-cli plugin init --url https://zsign.io/mcp/open --dir /tmp/lhm

(init needs a description from the server or a package.json, and refuses
to overwrite an existing manifest, so it runs in a scratch directory.)

Copy the generated tools into lhm.plugin.json, keep cloudEndpoint at
https://zsign.io/mcp, and run npm test. After the first lhm plugin publish,
lhm plugin update pushes later edits.

常见问题

8 问
答案由本站依据条目字段整理,不引用上游原文
zSign 怎么安装?

在客户端按下面的安装命令接入:npx add-mcp 'https://zsign.io/mcp'。装完在客户端配置里引用同一个包或端点。

zSign 怎么在 Claude Desktop、Claude、Cursor 里配置?

它的传输方式是HTTP · 远程,在客户端的 MCP 配置里填好启动命令和参数,保存后完全退出客户端再打开,配置才会生效。

zSign 收费吗?

本站不代收费用,也没有标注具体价格。是否收费取决于服务本身和背后的接口额度,正式使用前按官方说明确认。

zSign 需要 API Key 吗?

资料标注需要API Key认证,使用前准备好对应凭据,并按最小权限配置。

zSign 支持哪些客户端?

资料标注支持 Claude Desktop、Claude、Cursor、VS Code、Cline、Gemini CLI;其他客户端只要能配置 MCP Server,也能用同样的命令或地址接入。

zSign 能提供哪些能力?

资料显示能力标签包括 生产力。具体工具清单以官方文档为准。

zSign 需要什么运行环境?

属于远程端点,不需要在本地装运行时。

zSign 是本地还是远程?

它是远程端点,连服务地址即可。传输方式为HTTP · 远程。

热门专题

按标签挑服务器
全部专题 →

服务器信息以作者仓库与官方文档为准;分类、传输方式与鉴权方式的中文说明为中文整理,最近核验 2026-11-20。