Connect to Claude
DesignSkill Agent supports the Model Context Protocol (MCP), a standard JSON-RPC 2.0-based protocol. Select your preferred integration method below:
Open your Claude Desktop config file via "Developer" → "Edit Config", or locate it manually:
- Windows:
%APPDATA%\Claude\claude_desktop_config.json - macOS:
~/Library/Application Support/Claude/claude_desktop_config.json
Add the following block under "mcpServers". Use the absolute path to your cloned server file:
{
"mcpServers": {
"designskill-agent": {
"command": "node",
"args": ["/absolute/path/to/designskill-scraper/mcp-server/index.js"],
"env": {
"DESIGNSKILL_API_KEY": "YOUR_DESIGNSKILL_API_KEY",
"DESIGNSKILL_API_URL": "https://scraper.chowkar.in"
}
}
}
}
C:\\path\\to\\mcp-server\\index.js). Restart Claude Desktop after saving to reload the config.
Register the MCP server directly using the CLI:
# macOS / Linux
claude mcp add designskill-agent -- node "/absolute/path/to/designskill-scraper/mcp-server/index.js"
# Windows
claude mcp add designskill-agent -- node "C:\path\to\designskill-scraper\mcp-server\index.js"
Then expose your API key before launching Claude:
export DESIGNSKILL_API_KEY="YOUR_DESIGNSKILL_API_KEY"
export DESIGNSKILL_API_URL="https://scraper.chowkar.in"
claude
Test Run & Prompt
Once connected, ask Claude to analyze any target public website. Note: loopback hostnames like localhost are blocked to prevent SSRF vulnerabilities.
Claude will call the generate_design_skill tool and return a structured JSON response including extracted token files and a ZIP download link:
{
"ok": true,
"pluginName": "designskill-pack-example",
"zipFileUrl": "https://scraper.chowkar.in/output/uuid-designskill.zip",
"creditsUsed": 2,
"pipeline": ["scrape", "enrich", "package"],
"truncated": false,
"files": [
{
"path": "tokens.json",
"content": "{\n \"colors\": {\n \"primary\": \"#000000\",\n \"accent\": \"#ff0055\"\n }\n}",
"truncated": false
},
{
"path": "variables.css",
"content": ":root {\n --primary: #000000;\n --accent: #ff0055;\n}",
"truncated": false
}
]
}
MCP Distribution Modes
Currently the DesignSkill MCP adapter requires a local clone of the repository. The roadmap outlines lower-friction setup paths coming soon:
| Distribution Mode | Setup Requirements | Status |
|---|---|---|
| Local File Path | Clone repo and point args to index.js |
Available Now — Devs & Contributors |
| NPM Package (npx) | Node.js installed locally; no cloning required | Coming Soon — Public Onboarding |
| Desktop Extension | One-click install from Claude Desktop App | Future Roadmap — End-user simplicity |
npx on Windows (e.g. cmd /c npx ...). The local file path is the most stable fallback for Windows development environments.
Troubleshooting FAQ
-
Why isn't the hammer icon appearing in Claude Desktop?
Check that the absolute path in
"args"is spelled correctly. If Claude cannot locate yourindex.js, it won't boot the server. Review startup logs at%APPDATA%\Claude\Logs\mcp.log(Windows) or~/Library/Logs/Claude/mcp.log(macOS) to trace errors. -
Is Node.js required locally?
Yes. You must have Node.js installed and available on your system
PATHto allow Claude Desktop to execute the server command. -
Can I scrape local dev URLs?
No. Loopback and private IP addresses — such as
localhost,127.0.0.1, or192.168.*— are blocked by design. Scraper targets must be publicly accessible HTTP/HTTPS domains.