upstage-mcp-server
Provides an MCP server that lets an AI client (e.g., Claude Desktop) call Upstage document digitization and information extraction APIs to parse documents (PDF/images/Office files) and extract structured fields based on schemas.
Score Breakdown
⚙ Agent Friendliness
🔒 Security
Uses an API key via environment variable as shown in README (better than hardcoding), and communication to Upstage is implied via HTTP API calls (TLS likely, but not explicitly documented). No evidence is provided about fine-grained scopes, per-request authorization, or protections against local file path misuse/exfiltration in a multi-tenant setting. Dependency hygiene cannot be verified from provided content; includes common libraries (httpx, aiofiles, tenacity, mcp[cli]).
⚡ Reliability
Best When
You want MCP tool access from an MCP client (like Claude Desktop) to Upstage’s document parsing/extraction, and you can provide local file paths and an Upstage API key.
Avoid When
You need a public multi-user API, fine-grained per-user authorization, or you cannot control where files are read from (local file path exposure concerns).
Use Cases
- • Parsing PDFs and images into structured content while preserving layout
- • Extracting specific data points from invoices and other documents using provided or auto-generated schemas
- • Integrating document parsing/extraction into MCP-capable AI assistants for local workflows
Not For
- • Direct use as a general-purpose document hosting or search system
- • Use cases requiring user authentication/authorization between multiple end users
- • Serving untrusted documents in a hardened, multi-tenant environment without additional controls
Interface
Authentication
Authentication is delegated to Upstage via a single API key provided to the MCP server process via environment variables (no OAuth flow or scope-based authorization described at the MCP layer).
Pricing
Pricing for Upstage usage is not described in the provided package content; MCP server usage is tied to your Upstage API usage.
Agent Metadata
Known Gotchas
- ⚠ The server expects local file paths (the agent/client must pass accessible paths), which can fail if paths are incorrect or not permitted in the runtime environment.
- ⚠ Claude Desktop integration may fail with 'Server disconnected' if uvx/uv command resolution is wrong; the README suggests using an absolute path to the executable.
- ⚠ Supported file constraints are mentioned for troubleshooting (e.g., size < 50MB and < 100 pages), which agents should respect to avoid repeated failures.
Alternatives
Full Evaluation Report
Comprehensive deep-dive: security analysis, reliability audit, agent experience review, cost modeling, competitive positioning, and improvement roadmap for upstage-mcp-server.
AI-powered analysis · PDF + markdown · Delivered within 30 minutes
Package Brief
Quick verdict, integration guide, cost projections, gotchas with workarounds, and alternatives comparison.
Delivered within 10 minutes
Score Monitoring
Get alerted when this package's AF, security, or reliability scores change significantly. Stay ahead of regressions.
Continuous monitoring
Scores are editorial opinions as of 2026-04-04.