Pod

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

Reported issues for anymd

Pod holds 20 of 27 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 anymd.

Most discussed

MCP error -32602: Absolute paths are not allowed

Hi! Would there be any way to make this work? It's easier for the AI to access the file and the user to point to it if the user can simply copy paste the file direct link.

{ "sources": [ { "path": "C:\Users\SANDBOX\Desktop\sample-2.pdf" } ], "include_full_text": true, "include_metadata": true, "include_page_count": true } { "results": [ { "source": "C:\Users\SANDBOX\Desktop\sample-2.pdf", "success": false, "error": "MCP error -32600:…

Read the thread · 2025-08-20 · closed · external user · 8 comments

getAll() does not exist

Hi! I tried to build locally but I get following error on freshly cloned repository:

@sylphlab/pdf-reader-mcp@0.3.24 build tsc src/handlers/readPdf.ts:256:40 - error TS2339: Property 'getAll' does not exist on type 'Metadata'. 256 const metadataData = metadataObj.getAll() as PdfMetadata | undefined; ~~~~~ Found 1 error in src/handlers/readPdf.ts:256

Can you fix it please?

Read the thread · 2025-05-23 · closed · external user · 8 comments

[BUG] Unable to start MCP server in VSCode

🐛 Bug Description

MCP server is not getting start itself.

Error Logs: ` 2025-12-03 15:43:51.479 [warning] [server stderr] SyntaxError: The requested module '@sylphx/gust' does not provide an export named 'router' 2025-12-03 15:43:51.479 [warning] [server stderr] at ModuleJob._instantiate (node:internal/modules/esm/module_job:228:21) 2025-12-03 15:43:51.479 [warning] [server stderr] at async ModuleJob.run (node:internal/modules/esm/module_job:337:5) 2025-12-03 15:43:51.479…

Read the thread · 2025-12-03 · closed · external user · 6 comments

no tools

After I installed,mcp server has no tools

Read the thread · 2025-10-14 · closed · external user · 5 comments

Tool schema incompatible with Mistral API (400 error: "Invalid tool schema")

Hi,
Thank you for developing this project!

I’m encountering a problem when running pdf-reader-mcp alongside the Mistral API. When the PDF Reader MCP server is enabled, any API call to Mistral that includes the registered tool schema fails with the following error:

API error occurred: Status 400 Content-Type application/json Body 
{"object":"error","message":"Invalid tool schema: {'type': 'object', 'properties': {'path': {'type': 'string', 'minLength': 1, 'description': 'Relative path…

[Read the thread](https://github.com/SylphxAI/anymd/issues/63) · 2025-05-22 · closed · external user · 5 comments

### File not found error

Hi,

My agent is calling the tool with these args:

{ "sources": [ { "path": "FooBar.pdf" } ], "include_full_text": true, "include_metadata": true, "include_page_count": true }


And getting this response:

{ "results": [ { "source": "FooBar.pdf", "success": false, "error": "MCP error -32600: File not found at 'FooBar.pdf'." } ] }


And I can confirm that the PDF exists. If I run the server directly (without making a request),…

[Read the thread](https://github.com/SylphxAI/anymd/issues/21) · 2025-04-15 · closed · external user · 5 comments

### [BUG] OpenCode中配置后无法使用

## 🐛 Bug Description

opencode配置mcp后请求报错:Invalid schema for function 'PDF____read_pdf': {"type":"object","properties":{"path":{"type":"string","minLength":1,"description":"Relative path to the local PDF file."},"url":{"type":"string","format":"uri","description":"URL of the PDF file."},"pages":{"anyOf":[{"type":"array","items":{"type":"integer","exclusiveMinimum":true,"minimum":0},"minItems":1},{"type":"string","minLength":1}],"description":"Extract text only from specific pages (1-based) or…

[Read the thread](https://github.com/SylphxAI/anymd/issues/562) · 2026-07-23 · closed · external user · 3 comments

### Struggling to access the PDF file multiple times before it suceeds

## 🐛 Bug Description

MCP, struggling to access the PDF file multiple times before it succeeds

## 📋 Steps to Reproduce

1. Do this in Windows OS
2. Have a PDF file with “space” inside the filename (e.g, “Test File Bug.pdf”)
3. Open in VS Code, try to ask GitHub Copilot to read the file content
4. The AI will fail a couple of times to access the file
5. The file should be accessed, but it takes multiple tries to try to open the file.

## ✅ Expected Behavior

The MCP immediately access the…

[Read the thread](https://github.com/SylphxAI/anymd/issues/235) · 2025-11-28 · closed · external user · 3 comments

## Most recent

### `read_pdf` panics on any inline image (`BI ... ID ... EI`) — `unwrap()` of `Parse(InvalidContentStream)`

## Summary

Any content stream containing an inline image kills the `read_pdf` worker with a
Rust panic rather than returning an error:

MCP error -32603: read_pdf worker failed: task 39 panicked with message "called Result::unwrap() on an Err value: Parse(InvalidContentStream)"


Inline images are common in scanned PDFs — they are how many scanner drivers
emit small masks — so this takes out otherwise ordinary documents. The task
number varies between runs; nothing else…

[Read the thread](https://github.com/SylphxAI/anymd/issues/675) · 2026-09-03 · closed · external user · 1 comment

### [BUG] MCP Spec 2026-07-28 conformance failures in `server/discover` and `tools/list` result envelopes cause client initialization to fail

### 🐛 Bug Description

When connecting `@sylphx/citra@5.0.0` (pure-Rust `citra-mcp-server`) to modern MCP clients (such as Gemini Antigravity CLI and MCP 2026 spec runners), the server fails to initialize and register tools.

This happens due to two related protocol issues in `crates/pdf-reader-mcp-server/src/discover_compat.rs`:

1. **Schema Violations in `server/discover` (SEP-2575):**
The payload returned by `discover_result_value()` is missing required fields defined in the MCP 2026-07-28…

[Read the thread](https://github.com/SylphxAI/anymd/issues/663) · 2026-08-25 · closed · external user · 2 comments

### MCP spec conformance: 13 requirement(s) violated (via @hasmcp/mcp-spec-test) — spec 2026-07-28

When the MCP server published from this repo (`npx -y @sylphx/citra`) is tested against the newest MCP spec revision (2026-07-28) with `@hasmcp/mcp-spec-test`, 13 requirements are violated: `server/discover`'s response is missing required fields (`cacheScope`, `ttlMs`), `tools/list`/`tools/call` results are missing required envelope fields (`resultType`, `_meta.serverInfo`, cache hints), and a couple of version-negotiation edge cases cause the server process to exit rather than respond.…

[Read the thread](https://github.com/SylphxAI/anymd/issues/662) · 2026-08-24 · closed · external user · 1 comment

### [pdf-reader-core 3.1.1] cff-parser panic at encoding.rs:150 on CFF fonts with Custom encoding (Adobe InDesign + iTextSharp PDF)

## Summary

`@sylphx/citra` v5.0.0 (native engine `pdf-reader-core` 3.1.1) **panics (explicit `panic!`)** while extracting text from a PDF that embeds CFF / Type 1C fonts with **Custom** encoding. The panic originates in the `cff-parser` Rust crate and kills the native engine, surfacing on the SDK/MCP side as a `timeout tools/call` error.

## Environment

- OS: macOS (darwin) arm64 — Apple Silicon
- Node.js: v22.22.2
- Package: `@sylphx/citra@5.0.0`
- Native engine: `pdf-reader-core` 3.1.1…

[Read the thread](https://github.com/SylphxAI/anymd/issues/660) · 2026-08-22 · closed · external user · 1 comment

### [BUG] The pdf reader crashes on the file provided

## 🐛 Bug Description

<!-- A clear and concise description of what the bug is -->

When reading the file, the MCP crashes with `panicked at adobe-cmap-parser: bad length of hexstring`

## 📋 Steps to Reproduce

1. Run any mcp operation on the file provided.

## ✅ Expected Behavior

<!-- What you expected to happen -->

The tool will work.

## ❌ Actual Behavior

<!-- What actually happened -->

The tool crashes.

## 📸 Screenshots / Logs

<!-- If applicable, add screenshots or error logs -->…

[Read the thread](https://github.com/SylphxAI/anymd/issues/608) · 2026-08-02 · closed · external user · 1 comment

### [BUG] Crash on server/discover during Gemini Antigravity CLI MCP client initialization.

## 🐛 Bug Description

The `pdf-reader-mcp` server crashes immediately during initialization when connected to the Gemini MCP client. The crash happens because the Gemini client sends a custom `server/discover` request before completing the standard JSON-RPC handshake, causing an unhandled exception and a premature stream closure (`EOF`) on the server side.

## 📋 Steps to Reproduce

1. Install `pdf-reader-mcp` and add it to the Gemini Antigravity CLi MCP plugins…

[Read the thread](https://github.com/SylphxAI/anymd/issues/598) · 2026-07-27 · closed · external user · 1 comment

### [BUG] Missing OpenJPEG WASM fallback file causing image decode failures

## 🐛 Bug Description

When processing PDFs with images, the OpenJPEG WASM module fails to initialize due to a missing fallback file (named 'nullopenjpeg_nowasm_fallback.js'), causing image decode failures across all pages.

## 📋 Steps to Reproduce

1. Install pdf-reader-mcp via npx or npm
2. Attempt to process a PDF containing images
3. Observe the OpenJPEG errors in the logs

## ✅ Expected Behavior

Images within PDFs should decode correctly or gracefully fall back to non-WASM/Javascript…

[Read the thread](https://github.com/SylphxAI/anymd/issues/271) · 2026-04-09 · closed · external user · 1 comment

### [BUG] vscode gets unresponsive

First of all: very cool project! I really like the idea.

## 🐛 Bug Description

<!-- A clear and concise description of what the bug is -->

When I try summarizing a larger PDF (20+ pages), it takes forever, and the VS Code window becomes unresponsive almost immediately, even though my CPU usage is only around 20%.

## 📋 Steps to Reproduce

It would be great if you could test this behavior and let me know if my machine is simply too weak to handle it!

1. Set up VS Code
2. Try summarizing…

[Read the thread](https://github.com/SylphxAI/anymd/issues/254) · 2025-12-26 · closed · external user · 2 comments

### Codex stdio handshake fails: connection closed during initialize

### Summary

When Codex (OpenAI's CLI client) launches `@sylphx/pdf-reader-mcp` over stdio, the handshake fails immediately with `connection closed: initialize response`. Running the same command manually works fine.

### Reproduction
1. Add this entry to `~/.codex/config.toml`:
   ```toml
   [mcp_servers.pdf_reader_mcp]
   command = "bunx"
   args = ["-y", "@sylphx/pdf-reader-mcp"]
   startup_timeout_sec = 30
  1. Start Codex CLI and run /mcp (or codex mcp list).
  2. Codex logs show…

Read the thread · 2025-11-11 · closed · external user · 2 comments

Codex stdio handshake fails: connection closed during initialize

Summary

When Codex (OpenAI's CLI client) launches @sylphx/pdf-reader-mcp over stdio, the handshake fails immediately with connection closed: initialize response. Running the same command manually works fine.

Reproduction

  1. Add this entry to ~/.codex/config.toml:
    [mcp_servers.pdf_reader_mcp]
    command = "bunx"
    args = ["-y", "@sylphx/pdf-reader-mcp"]
    startup_timeout_sec = 30
    
  2. Start Codex CLI and run /mcp (or codex mcp list).
  3. Codex logs show…

Read the thread · 2025-11-11 · closed · external user · 2 comments

cant use in claude code

⏺ pdf-reader-mcp - read_pdf (MCP)(sources: [{"path":"Desktop/quant_related/1808.03668v6.pdf","pages":[1,2]}], include_metadata: true, include_full_text: true) ⎿  {
"results": [ { "source": "Desktop/quant_related/1808.03668v6.pdf", "success": false, "error": "Failed to process PDF from…

Read the thread · 2025-10-22 · closed · external user · 1 comment

cursor Compatibility issues

I used the npm installation method. After installation, the cursor could not make normal requests. However, it worked fine after closing pdf-read-mcp. "pdf-reader-mcp": { "command": "npx", "args": ["@sylphlab/pdf-reader-mcp"], "name": "PDF Reader (npx)" }

Image

<img width="3046" height="888" alt="Image"…

Read the thread · 2025-09-10 · closed · external user · 2 comments

The remaining reports are on the project's issue tracker.