ZapSign
io.github.mcp-dir
ZapSign electronic document signing via the official API: create documents for signature (from PDF,
{ "mcpServers": { "io.github.mcp-dir-zapsign-mcp": { "url": "https://api.mcp.ai/p_zapsign", "headers": {} } }}.cursor/mcp.jsonMCP server
- Transport
- http
- Status
- Remote
Power your agent
Add this server
The publisher's own URL. Not a PlugMCP endpoint.
Host a copy with our keys and logs.
Server URL
https://api.mcp.ai/p_zapsignThe Claude button above opens Claude with the name and URL filled in. You still confirm it there.
shClaude Code
claude mcp add --transport http io.github.mcp-dir-zapsign-mcp https://api.mcp.ai/p_zapsignRun in a terminal.
jsonClaude Desktop
{ "mcpServers": { "io.github.mcp-dir-zapsign-mcp": { "command": "npx", "args": [ "-y", "mcp-remote", "https://api.mcp.ai/p_zapsign" ] } }}claude_desktop_config.json
Remote · HTTPPublisher installStep-by-step: add this in Claude
Remote URL or a command on your machine? How the two installs differ
Run on PlugMCP
Host a copy with our keys and logs.
A new server you create. It is not this listing's official endpoint. Use the publisher install when you want their URL and their credentials.
LaunchServer facts
Remote- Transport
- http
- Version
- 0.1.0
- Last checked
- 2026-10-26
- Stars
- —
- Tools
- —
- Uptime
- —
Tools
Tools
No tool list yet. Remote servers get one after the first health check.
FAQ
Questions
How do I install ZapSign?
Copy the http config for Cursor, Claude Desktop, Claude Code, or VS Code on this page. It uses the publisher's install, not a PlugMCP proxy.
Does ZapSign need an API key?
No required environment variable is listed on this record.
What transport does ZapSign use?
ZapSign is reached over HTTP.
When was ZapSign last checked?
Last checked 2026-10-26. ZapSign electronic document signing via the official API: create documents for signature (from PDF,
From the publisher
Documentation
README is not crawled yet. Open the repository