You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
docs: update README and MCP integration guide to clarify Node MCP server options, enhance troubleshooting tips, and improve documentation on the new faxbot_pdf tool for PDF text extraction
- Recommended (OCR, avoids base64): use the new Node MCP servers in `node_mcp/` and the `faxbot_pdf` prompt to extract PDF text locally and send as TXT fax.
-**Typical PDF (1MB)**: ~4MB tokens, may hit limits
75
-
-**Large PDF (5MB)**: ~20MB tokens, **will fail**
76
-
77
-
### Why This Design Was Chosen:
78
-
MCP protocol's JSON-based messaging requires binary data as base64. Alternative approaches (file paths, resource URLs) are emerging in the MCP community but not yet standardized for tool parameters.
The new Node MCP servers in `node_mcp/` add a prompt-driven workflow that avoids sending base64 data through the conversation. Python MCP servers now include a matching tool for parity.
83
-
84
-
- Node prompt: `faxbot_pdf`
85
-
- Python tool: `faxbot_pdf(pdf_path, to, header_text?)`
86
-
- Behavior: Extracts text from the local PDF and sends it as a TXT fax to drastically reduce tokens. If text is not embedded, optional OCR fallback can be enabled.
87
-
88
-
Example prompt execution (conceptual GetPrompt request):
- Set `MAX_TEXT_SIZE` (default 100000 bytes) to control extracted text size. Exceeding text is truncated with a warning.
110
85
- This path does not embed base64 in the AI conversation, improving reliability for large PDFs.
86
+
- An optional prompt named `faxbot_pdf` is available in Node that returns a message instructing the model to call the tool; the prompt itself does not send the fax.
0 commit comments