Design
siteprint.app
Siteprint provides real website design scans and examples, plus setup instructions to connect its local MCP server to coding agents like Claude Code, Cursor, and Codex.
ENDPOINT 1
https://siteprint.app/api/mcp
MCP server metadata
- Name
- siteprint-examples
- Version
- 1.0.0
Siteprint turns a website into an exact prompt or DESIGN.md. This server has four example DESIGN.md exports and setup steps; the person's own scans come from Siteprint's local server.
Known tools 3
list_example_designsReal Siteprint scans of four public sites, each with the original page a coding agent built from it.
Inferred read-onlyget_setupHow to connect Siteprint's local MCP server, which serves the person's own scans, to Claude Code, Cursor, Codex or another client.
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.siteprint-examples]
url = "https://siteprint.app/api/mcp"
enabled = true
Claude Code
.mcp.json
{
"mcpServers": {
"siteprint-examples": {
"type": "http",
"url": "https://siteprint.app/api/mcp"
}
}
}
Claude Desktop
Settings → Connectors → Add custom connector
Name: siteprint-examples
Remote MCP URL: https://siteprint.app/api/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": {
"siteprint-examples": {
"url": "https://siteprint.app/api/mcp"
}
}
}
Visual Studio Code
.vscode/mcp.json
Add to Visual Studio Code{
"servers": {
"siteprint-examples": {
"type": "http",
"url": "https://siteprint.app/api/mcp"
}
}
}
Generic MCP
Client-specific MCP configuration
{
"name": "siteprint-examples",
"transport": "streamable-http",
"url": "https://siteprint.app/api/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.