eCommerce
smartpress.com
An MCP server for Smartpress that enables finding print products, retrieving product configurations and templates, and managing iterative product configuration sessions.
ENDPOINT 1
https://mcp.smartpress.com/mcp
MCP server metadata
- Name
- smartpress-mcp-server
- Version
- 0.1.0
Known tools 21
get_product_configRetrieve the default product configuration for a given product ID.
Inferred read-onlyget_product_templatesGet the downloadable print templates and design guides for a Smartpress product.
Inferred read-onlycreate_config_sessionCreate a new product configuration session to begin iterative configuration.
Potential side effectslink_file_sessionDurably join a file session to a configuration session (last-write-wins).
Potential side effectsclone_file_sessionCopy a file session — files, approved proofs, and completed check results — into a NEW file session, leaving the original and its configuration join untouched.
Inferred read-onlylist_session_filesList the files currently attached to a file session, including each file's name, size, type, and sessionFileId.
Inferred read-onlyget_file_upload_urlMint a short-lived presigned URL that a client (a browser, an app, or the user) can use to upload a file directly to storage, attached to a file session.
Potential side effectsmcp_health_checkRun a health check against the Smartpress backend by probing each read-only tool with safe minimal inputs.
Inferred read-onlyanalyze_fileAnalyze a file already uploaded to a file session and return its analysis: PDF metadata (page size/count), extracted text, image labels, color palette, quality scores, and an AI classification (productCategory, industry, designStyle, targetAudience, marketingIntent).
Inferred read-onlyget_file_analysisFetch the status/results of a file analysis started by analyze_file (use the uploadId it returned).
Inferred read-onlyget_file_session_analysisRead the persisted structured analysis summary for a file session.
Inferred read-onlyrecommend_productsMap a file analysis (from analyze_file) to Smartpress product candidates: productId, productName, a rationale citing the analysis evidence, a 0-1 confidence, and machine-readable matchSignals.
Inferred read-onlycreate_proofGenerate (enqueue) a preflight proof for a file in a file session: the proof service checks the file against the product's print specs and produces a proof with any errors/warnings.
Inferred read-onlycreate_file_checkRun (enqueue) a file check for a file in a file session: the proof service preflights the file against the product's print specs and produces a report of errors/warnings.
Inferred read-onlyset_proof_approvalRecord the customer's decision on a proof: APPROVED (they sign off on the proof as shown), FURTHER_REVIEW (a Smartpress expert checks the file before printing), or DECLINED.
Inferred read-onlyCONNECT WITH APPROVAL
Client installation
Review this server and its permissions before adding it. Secret placeholders must be set locally.
Codex
~/.codex/config.toml
[mcp_servers.smartpress-mcp-server]
url = "https://mcp.smartpress.com/mcp"
enabled = true
Claude Code
.mcp.json
{
"mcpServers": {
"smartpress-mcp-server": {
"type": "http",
"url": "https://mcp.smartpress.com/mcp"
}
}
}
Claude Desktop
Settings → Connectors → Add custom connector
Name: smartpress-mcp-server
Remote MCP URL: https://mcp.smartpress.com/mcp
Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.
Cursor
.cursor/mcp.json
{
"mcpServers": {
"smartpress-mcp-server": {
"url": "https://mcp.smartpress.com/mcp"
}
}
}
Visual Studio Code
.vscode/mcp.json
Add to Visual Studio Code{
"servers": {
"smartpress-mcp-server": {
"type": "http",
"url": "https://mcp.smartpress.com/mcp"
}
}
}
Generic MCP
Client-specific MCP configuration
{
"name": "smartpress-mcp-server",
"transport": "streamable-http",
"url": "https://mcp.smartpress.com/mcp"
}
MCP Inspector
Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.
TRUST AND VERIFICATION EVIDENCE
Loading Trust v2 evidence…
Checking the associated registrable domain. The BuiltWith key remains server-side.
Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.