Deep Integration Configuration Guide
Three key steps are required to achieve seamlessness:
- Service pre-launch: It is recommended to run SiteMCP independently first to complete the crawl, for example
npx sitemcp https://tailwindcss.com -m "/docs/**" - Configuration file modification: Add the MCP service definition in the Claude configuration file
{
"mcpServers": {
"tailwind-docs": {
"command": "npx",
"args": ["sitemcp", "https://tailwindcss.com", "-m", "/docs/**"]
}
}
} - access control: after restarting the Client can be directly referenced via aliases (e.g. @tailwind-docs)
Advanced Integration Tips:
- Create separate configuration groups for different projects
- Shortening common query commands in conjunction with alias
- Monitor port conflict issues (default 3000)
This answer comes from the articleSiteMCP: Crawling website content and turning it into MCP servicesThe































