liteparse-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Capabilities
Features and capabilities supported by this server
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| logging | {} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| extensions | {
"io.modelcontextprotocol/ui": {}
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| parse_pdfA | Parse a PDF and return structured text plus bounding boxes for every text item on every page. Bounding-box coordinates are in PDF points (1 pt = 1/72 inch), with the origin at the top-left corner of each page. Returns JSON: { "pages": [ { "page_num", "width_pts", "height_pts", "text", "text_items": [ { "text", "x", "y", "width", "height", "font_name", "font_size", "confidence" } ] } ] } |
| batch_parse_pdfsA | Parse all PDFs in a folder. For each PDF, writes to //: pages.json – text + bounding boxes per page summary.txt – plain text of the whole document page_N.png – raw page screenshot page_N_cited.png – screenshot with bounding-box highlights Returns a JSON summary of successes and any errors. |
| screenshot_pdfA | Render PDF pages as PNG images (base64-encoded). Returns JSON list of: { "page_num", "width_px", "height_px", "image_base64" } |
| cited_screenshotA | Render a single PDF page as a PNG with bounding-box highlights drawn over every extracted text item (or only items matching search_phrase). Returns JSON: { "page_num", "width_px", "height_px", "items_highlighted", "image_base64" } |
| search_pdfA | Search for a phrase in a PDF and return every matching text item with its page number and bounding-box coordinates. Returns JSON: { "phrase", "match_count", "matches": [ { "page_num", "text", "x", "y", "width", "height", "font_size" } ] } |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/lisabrennan1996/liteparse-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server