---
title: "signatureapi"
description: "SignatureAPI e-signature skills, kept in sync with the hosted MCP server configuration so the same install delivers both."
canonical: https://agentpluginsdirectory.com/plugins/signatureapi
last-updated: 2026-09-09
---

# signatureapi
SignatureAPI e-signature skills, kept in sync with the hosted MCP server configuration so the same install delivers both.
- Slug: signatureapi
- Publisher: SignatureAPI
- Repository: https://github.com/signatureapi/skills
- Manifest: plugin.json
- Version: 1.0.0
- License: MIT
- Category (editorial): other
- Skills: 3 (signatureapi-architecture, signatureapi-diagnose, signatureapi-integrate)
- MCP servers: 1 (signatureapi)
- Stars: 0
- Repository created: 2026-09-02
- Repository last pushed: 2026-09-08
- Publisher type: Organization
- Listing: https://agentpluginsdirectory.com/plugins/signatureapi
- Schema: https://agent-plugins.org/schemas/1.0.0/plugin.schema.json

## What signatureapi does, in the publisher's words

Agent Skills for SignatureAPI, the e-signature API. Three skills let AI coding agents design, build and troubleshoot e-signature integrations from the command line: one decides how an app should use SignatureAPI and writes the design, one builds the signing flow from that design, one diagnoses a flow that already exists.

From the project README, punctuation lightly normalized. Full text: https://raw.githubusercontent.com/signatureapi/skills/HEAD/README.md

## Skills

- signatureapi-architecture: Use when someone asks how to use SignatureAPI in their app, or plans or designs a signing flow or a signing product. Use when someone asks for 'a platform like DocuSign'. Use for any request to add SignatureAPI that is not a narrow change to an existing flow. Use it before any application code exis…
- signatureapi-diagnose: SignatureAPI failure runbook. Use when an envelope is stuck in processing, a signature webhook never arrived, or a recipient never got the signing email. Also use when a deliverable is missing after completion, or the API returns 422 on envelope creation. Use it even for a seemingly simple case lik…
- signatureapi-integrate: Use when building or changing an integration with SignatureAPI: creating envelopes, placing signature fields, wiring up SignatureAPI webhooks, or verifying a signing flow end to end. Use it even for a seemingly simple task like creating a single envelope, and in any host, including one with no repo…

Descriptions come from the frontmatter of each SKILL.md, punctuation lightly normalized.

## MCP servers

- signatureapi: transport: streamable-http; url: https://mcp.signatureapi.com/mcp

Read from the plugin's own mcp.json. Environment variable names only, never values.