io.zsign/zsign
Send documents for e-signature from AI assistants, track signers, and download sealed, signed PDFs.
Install
Add this to your client's MCP configuration (Claude Desktop: claude_desktop_config.json; Cursor: .cursor/mcp.json; VS Code and others use the same "mcpServers" shape).
claude mcp add --transport http zsign 'https://zsign.io/mcp' --header 'Authorization: <Optional. This server is an OAuth 2.1 protected resource: clients should prefer OAuth, discovered automatically via /.well-known/oauth-protected-resource/mcp and /.well-known/oauth-authorization-server (authorization code + PKCE S256, Dynamic Client Registration at /oauth/register, refresh tokens, scopes: credits:read, credits:purchase, envelopes:send, envelopes:read). As an alternative, set this header to a static '\''Bearer zs_live_...'\'' API key. Neither is needed for discovery: create_account and get_pricing work unauthenticated, and create_account returns a key.>'
{
"mcpServers": {
"zsign": {
"type": "http",
"url": "https://zsign.io/mcp",
"headers": {
"Authorization": "<Optional. This server is an OAuth 2.1 protected resource: clients should prefer OAuth, discovered automatically via /.well-known/oauth-protected-resource/mcp and /.well-known/oauth-authorization-server (authorization code + PKCE S256, Dynamic Client Registration at /oauth/register, refresh tokens, scopes: credits:read, credits:purchase, envelopes:send, envelopes:read). As an alternative, set this header to a static 'Bearer zs_live_...' API key. Neither is needed for discovery: create_account and get_pricing work unauthenticated, and create_account returns a key.>"
}
}
}
}
Frequently asked questions
What is io.zsign/zsign?
Send documents for e-signature from AI assistants, track signers, and download sealed, signed PDFs.
How do I install io.zsign/zsign?
It runs as a remote server. In Claude Code: claude mcp add --transport http zsign 'https://zsign.io/mcp' --header 'Authorization: <Optional. This server is an OAuth 2.1 protected resource: clients should prefer OAuth, discovered automatically via /.well-known/oauth-protected-resource/mcp and /.well-known/oauth-authorization-server (authorization code + PKCE S256, Dynamic Client Registration at /oauth/register, refresh tokens, scopes: credits:read, credits:purchase, envelopes:send, envelopes:read). As an alternative, set this header to a static '\''Bearer zs_live_...'\'' API key. Neither is needed for discovery: create_account and get_pricing work unauthenticated, and create_account returns a key.>'. For other clients, paste the JSON configuration from this page into their MCP settings.
Does io.zsign/zsign need an API key?
Yes. It expects Authorization, which you set in its configuration.
Who maintains io.zsign/zsign?
It is published by io.zsign. AI.tn lists it but does not maintain or endorse it.
From the official MCP Registry. Listing is not an endorsement: review a server's code and permissions before giving it access to your data.