Pod

Available as Markdown and JSON. Pod is also available over MCP.

Reported issues for signwell-mcp

Pod holds 6 of 6 GitHub reports that passed its relevance review. This can include external user reports, maintainer-confirmed bugs, and concrete feature gaps. Treat them as evidence to inspect, not a count of distinct defects.

Back to signwell-mcp.

Most discussed

feature: no way to repair a document after create/send (no update_recipients or delete), dates can't be locked to the signing date, and send_draft returns a stale payload

Three gaps found while sending a two-party agreement through @signwell/mcp 0.3.3. They share a theme: the REST API can inspect and repair a document, but the MCP server can't, so anything set wrongly at create time needs a human in the web app.

1. No way to repair a document after document_create / document_send_draft

The document tool surface is document_create, document_get, document_list, document_send_draft, document_send_reminder, document_completed_pdf. The API has…

Read the thread · 2026-09-17 · closed · external user · 1 comment

bug: tolerate Claude Code MCP stringification on 3 affected tools

Summary

3 tools (template_create, template_update, document_send_draft) are unusable from Claude Code: the harness stringifies booleans/arrays before sending, and the Zod validator (correctly) rejects with "expected boolean/array, received string".

Confirmed Claude-Code-specific — same setup in OpenAI Codex sends native types and works (see Codex section). Bug is upstream Anthropic (https://github.com/anthropics/claude-code/issues/18260, no fix ETA), so the practical patch for…

Read the thread · 2026-05-05 · closed · external user · 1 comment

bug: document_create drops recipient names (first_name/last_name never map to the API's name)

What happens

document_create accepts first_name and last_name per recipient, but the created document stores an empty name. Confirmed on four envelopes over several weeks, most recently today with @signwell/mcp 0.3.3.

Request:

{
  "name": "Independent Contractor Agreement",
  "recipients": [
    { "id": "1", "email": "mary.poppins@example.com", "first_name": "Mary", "last_name": "Poppins" }
  ],
  "copied_contacts": [{ "email": "bert@example.com", "name": "Bert the Chimney…

[Read the thread](https://github.com/Bidsketch/signwell-mcp/issues/26) · 2026-09-17 · closed · external user · 0 comments

### enhancement: expose `api_application_id` on `/documents` MCP tools (matches REST docs + `/templates` MCP tools)

## Summary
The REST API documents `api_application_id` as an optional body parameter on `POST /documents` (https://developers.signwell.com/reference/createdocument):

> *"Unique identifier for API Application settings to use. API Applications are optional and mainly used when isolating OAuth apps or for more control over embedded API settings."*

The MCP wrapper exposes this field on the **template** tools (`template_create`, `template_update`) but **not** on any `/documents` tool…

[Read the thread](https://github.com/Bidsketch/signwell-mcp/issues/15) · 2026-05-05 · closed · external user · 0 comments

### docs: `document_create` returns empty `fields[]` before async parsing

## Summary
After `document_create` with `text_tags: true` and a PDF whose tags (`{{signature:1:y}}`, etc.) are selectable text, the immediate POST response shows `fields: []` and `pages_number: 0`. A few seconds later (we observed at T+5s already), `document_get` returns the same doc with parsed fields and `pages_number: 1`. The async parsing window isn't reflected in the create response and isn't documented in the tool description, so callers reading `fields.length === 0` straight after create…

[Read the thread](https://github.com/Bidsketch/signwell-mcp/issues/14) · 2026-05-05 · closed · external user · 0 comments

### enhancement: add `.html` and `.htm` to `ALLOWED_FILE_EXTENSIONS`

## Summary
The MCP wrapper's `ALLOWED_FILE_EXTENSIONS` (`src/tools/documents.ts` ~line 153-170) accepts `.pdf`, `.doc`, `.docx`, `.pages`, `.ppt`, `.pptx`, `.key`, `.xls`, `.xlsx`, `.numbers`, `.jpg`, `.jpeg`, `.png`, `.tiff`, `.tif`, `.webp` — but **omits `.html` and `.htm`**, which the underlying REST API explicitly accepts.

Per `developers.signwell.com/reference/createdocument`:
> *"Valid file types are: `.pdf, .doc, .docx, .pages, .ppt, .pptx, .key, .xls, .xlsx, .numbers, .jpg, .jpeg,…

[Read the thread](https://github.com/Bidsketch/signwell-mcp/issues/12) · 2026-05-05 · closed · external user · 0 comments

## Most recent

The remaining reports are on [the project's issue tracker](https://github.com/Bidsketch/signwell-mcp/issues).