CanUSign MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| CANUSIGN_API_KEY | Yes | Your CanUSign API key | |
| CANUSIGN_API_URL | No | API base URL (default: https://canusign.com) | https://canusign.com |
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_contractA | Create a new contract for signing, either from HTML content or from a PDF file. Returns a signing URL that can be shared with signers, and can e-mail a link of their own to individual signers ( |
| update_contractA | Rename, retag or finalize a draft, and send or resend signing links to individual signers. The same address again resends the link; a new address replaces it and the old link stops working. The response lists each link with its status (created, sent, opened, signed). |
| list_contractsA | List all contracts. Can filter by status. |
| get_contractA | Get details of a specific contract by ID or token. |
| list_attachment_typesA | List the extra forms that can be appended to a contract, with the fields each one requires. Use before create_contract when the contract needs an attachment, so the fields are sent complete: a missing required field is rejected, and a wrong one would end up blank on a signed document. |
| delete_contractA | Delete a contract. Note: Signed contracts cannot be deleted. |
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 6 tools
The tools are mostly distinct: create/update/list/get/delete cover contract lifecycle, and list_attachment_types is clearly a supporting lookup. Minor ambiguity exists between get_contract and list_contracts, but their descriptions (specific vs. list) make the boundary clear.
All tool names follow a consistent verb_noun pattern: create_contract, update_contract, list_contracts, get_contract, delete_contract, list_attachment_types. The pattern is uniform and predictable.
Six tools is well-scoped for a contract-signing server: full CRUD plus a supporting lookup for attachment types. Each tool earns its place without redundancy or bloat.
The contract lifecycle is well covered: create, update, list, get, delete, plus attachment-type lookup. A minor gap is the lack of a dedicated tool to view signing status/activity beyond what update_contract returns, but the core workflows are complete.