SignForge
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SIGNFORGE_API_KEY | Yes | Your SignForge API key. Get one at signforge.io/dashboard/developers. | |
| SIGNFORGE_API_URL | No | API base URL. Only change this for self-hosted instances or staging. | https://signforge.io/api/v1 |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| create_and_sendA | Create an envelope with a PDF document, add a signer, and send it for e-signature. Returns the envelope ID and a signing URL. Provide either a local file path (pdf_path) or base64-encoded PDF content (pdf_base64). |
| check_statusB | Check the current status of an envelope. Returns the envelope details including recipient signing status, document availability, and timestamps. |
| download_signedA | Download the signed PDF document for a completed envelope. The envelope must be in 'completed' status. Saves the file to the specified output path. |
| list_envelopesB | List your envelopes with optional filtering by status. Returns envelope summaries including titles, statuses, and recipient information. |
| send_envelopeA | Send a draft envelope for signing. The envelope must be in 'draft' status with at least one recipient and one field configured. |
| void_envelopeA | Void (cancel) an active envelope. The envelope must be in 'sent' status. All pending signatures will be cancelled and signers will be notified. |
| delete_envelopeA | Permanently delete an envelope. Only draft and voided envelopes can be deleted. |
| download_certificateA | Download the audit certificate PDF for a completed envelope. The certificate contains the full audit trail with timestamps and IP addresses. |
| download_archiveA | Download a ZIP archive containing the signed PDF, audit certificate, and all related documents for a completed envelope. |
| get_embed_urlA | Generate an embeddable signing URL for an envelope. This URL can be embedded in an iframe for in-app signing experiences. |
| create_webhookA | Create a webhook to receive real-time notifications for envelope events. Events include: envelope.sent, envelope.viewed, envelope.signed, envelope.completed, envelope.expired, envelope.voided, envelope.declined. |
| list_webhooksB | List all configured webhooks for your account. |
| delete_webhookA | Delete a webhook by its ID. The webhook will stop receiving events immediately. |
| list_templatesC | List your reusable document templates. Templates contain pre-placed fields and can be used to quickly create envelopes. |
| create_from_templateB | Create an envelope from a template. Optionally pre-fill field values and send immediately. The template's fields will be mapped to the provided recipients. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 15 tools
Each tool has a clearly distinct purpose with no overlap. For example, check_status retrieves envelope details, create_and_send creates and sends a new envelope, download_signed downloads the signed PDF, and void_envelope cancels an active envelope. The actions and targets are well-defined, preventing misselection.
All tool names follow a consistent verb_noun pattern using snake_case, such as check_status, create_and_send, download_signed, and list_envelopes. This predictability makes the tool set easy to navigate and understand at a glance.
With 15 tools, the server is well-scoped for e-signature management. It covers envelope lifecycle (create, send, check, void, delete), document handling (download signed/archive/certificate), templates, webhooks, and listing operations. Each tool earns its place without bloat.
The tool set provides complete CRUD and lifecycle coverage for the e-signature domain. It includes envelope creation (from scratch or template), sending, status checking, voiding, deletion, document downloads, webhook management, and listing operations. There are no obvious gaps that would hinder agent workflows.