Mcp Server Upstage — independently scanned and version-tracked by SaferSkills.
SaferSkills independently audited Mcp Server Upstage (Agent Skill) and scored it 100/100 (green). The audit ran 55 deterministic rules across Security, Supply Chain, Maintenance, Transparency, and Community; it found 0 high-severity and 0 lower-severity findings. The full rule-by-rule trace and per-finding evidence are below. Free, methodology-open.
Findings & checks · 0 flagged
Every scanned point with the score it earned and what moved between them.
First recorded scan — no prior version to compare against.
The primary manifest — the file an agent reads to learn what this artifact does.
A Model Context Protocol (MCP) server for Upstage AI's document digitization and information extraction capabilities
The Upstage MCP Server provides a robust bridge between AI assistants and Upstage AI’s powerful document processing APIs. This server enables AI models—such as Claude—to effortlessly extract and structure content from various document types including PDFs, images, and Office files. The package supports multiple formats and comes with seamless integration options for Claude Desktop.
Before using this server, ensure you have the following:
This guide provides step-by-step instructions to set up and configure the mcp-upstage
uv (Recommended)No additional installation is required when using uvx as it handles execution. However, if you prefer to install the package directly:
uv pip install mcp-upstageFor integration with Claude Desktop, add the following content to your claude_desktop_config.json:
%APPDATA%\Claude\claude_desktop_config.json~/Library/Application Support/Claude/claude_desktop_config.json{
"mcpServers": {
"mcp-upstage": {
"command": "uvx",
"args": ["mcp-upstage"],
"env": {
"UPSTAGE_API_KEY": "<your-api-key>"
}
}
}
}If uvx is not available globally, you may encounter a Server disconnected error. To resolve this, run which uvx to find its full path, and replace "command": "uvx" above with the returned path.
Processing results are stored in your home directory under:
~/.mcp-upstage/outputs/document_parsing/
~/.mcp-upstage/outputs/information_extraction/
~/.mcp-upstage/outputs/information_extraction/schemas/
Follow these steps to set up and run the project locally:
git clone https://github.com/UpstageAI/mcp-upstage.git
cd mcp-upstage# Install uv if not already installed
pip install uv
# Create and activate a virtual environment
uv venv
# Activate the virtual environment
# On Windows:
# .venv\Scripts\activate
# On macOS/Linux:
source .venv/bin/activate
# Install dependencies in editable mode
uv pip install -e .claude_desktop_config.json file with the following configurations:For Windows:
{
"mcpServers": {
"mcp-upstage": {
"command": "uv",
"args": [
"run",
"--directory",
"C:\\path\\to\\cloned\\mcp-upstage",
"python",
"-m",
"upstage_mcp.server"
],
"env": {
"UPSTAGE_API_KEY": "your_api_key_here"
}
}
}
}Replace C:\\path\\to\\cloned\\mcp-upstage with your actual repository path.
For macOS/Linux:
{
"mcpServers": {
"mcp-upstage": {
"command": "/Users/username/.local/bin/uv",
"args": [
"run",
"--directory",
"/path/to/cloned/mcp-upstage",
"python",
"-m",
"upstage_mcp.server"
],
"env": {
"UPSTAGE_API_KEY": "your_api_key_here"
}
}
}
}Replace:
/Users/username/.local/bin/uv with the output of which uv./path/to/cloned/mcp-upstage with the absolute path to your local clone.Tip for macOS/Linux users: If connection issues occur, using the full path to your uv executable can improve reliability.
After configuring, restart Claude Desktop.
The server exposes two primary tools for AI models:
file_path – the path to the document to be processed.
"Can you parse the document at `C:\Users\username\Documents\contract.pdf` and provide a summary?"
file_path – the document file path; schema_path (optional) – a JSON file with an extraction schema; auto_generate_schema (default true) – whether to auto-generate a schema.
"Extract the invoice number, date, and total from `C:\Users\username\Documents\invoice.pdf`."
Below is the revised troubleshooting section formatted as requested. You can copy and paste the following Markdown directly into your README:
Ensure that your UPSTAGE_API_KEY is correctly set in your claude_desktop_config.json file. Obtain a valid API key from Upstage Console.
Double-check the file path for correctness and accessibility. Ensure that file paths are absolute (e.g., C:\Users\name\Documents\file.pdf) and that any special characters in the path are properly escaped.
Verify that your virtual environment is activated and all dependencies are installed. Additionally, review the Claude Desktop log files for errors:
%APPDATA%\Claude\logs\mcp-upstage.log~/Library/Logs/Claude/mcp-upstage.logRestart Claude Desktop. Ensure that uvx is installed and available in your system PATH, or use its absolute path in your configuration if needed.
Check that the document is in a supported format (PDF, JPEG, PNG, TIFF, etc.), its file size is under 50MB, and it contains fewer than 100 pages. Test with a simpler document to confirm functionality.
Verify that the document is in a supported, uncorrupted format.
Confirm your network connection, firewall settings, and configuration details in claude_desktop_config.json. Review the logs for more detailed error messages.
For troubleshooting, view the server logs at:
%APPDATA%\Claude\logs\mcp-upstage.log
~/Library/Logs/Claude/mcp-upstage.log
Contributions are welcome! If you wish to enhance the project or add new features, please fork the repository and submit a pull request. For major changes, please open an issue first to discuss what you would like to change.
This project is licensed under the MIT License.
~30 seconds. Free. No account. Every finding cites a rule and a line of evidence.