Next.js + React + Tailwind Assistant
Provides comprehensive documentation search for Next.js 15+ and Tailwind CSS 3+, along with 27 production-ready Catalyst UI components and 13 design patterns for building modern web applications.
README
Next.js + React + Tailwind Assistant MCP Server
Your comprehensive AI companion for building modern Next.js applications with React and Tailwind CSS.
Features
📚 Complete Documentation
- Next.js 15+: App Router, Server Components, Server Actions, routing, data fetching
- Tailwind CSS 3+: All utility classes, responsive design, dark mode, customization
- Smart Search: Targeted results without overwhelming context
🎨 27 Catalyst UI Components
- Production-ready TypeScript React components
- Built with Tailwind CSS and Headless UI
- Fully accessible, responsive, and customizable
- Categories: forms, navigation, layout, feedback, data display
✨ 13 Design Patterns
Abstracted from 11 professional Next.js templates:
Visual Effects: Gradients, glows, animations, bento grids, decorative SVGs Component Library: Buttons, cards, badges, inputs, avatars, alerts, tooltips Color Systems: 8 palette strategies (Professional, SaaS, Bold, Minimal, Semantic, Dark Mode) Typography: Font systems, type scales, responsive patterns Layouts: App headers, auth pages, sidebars, overlay navigation Pages: Hero sections, pricing tables, blog layouts
All patterns include accessibility, performance, and dark mode support.
Installation
Via Smithery
npx @smithery/cli install @username/nextjs-react-tailwind-assistant --client claude
Manual Installation
- Clone the repository:
git clone https://github.com/CaullenOmdahl/Nextjs-React-Tailwind-Assistant.git
cd Nextjs-React-Tailwind-Assistant
- Install dependencies:
npm install
- Build the server:
npm run build
This will:
- Build the MCP server using Smithery CLI →
.smithery/index.cjs(1.67 MB) - Copy the content directory →
.smithery/content/(5.3 MB)
Development
npm run dev # Start development server with hot reload
npm run inspector # Launch MCP inspector for testing
npm run build # Build production bundle
npm run watch # TypeScript watch mode
Available Tools
search_nextjs_docs- Search Next.js documentationsearch_tailwind_docs- Search Tailwind CSS utilities and conceptsget_nextjs_full_docs- Complete Next.js documentation (large)get_tailwind_full_docs- Complete Tailwind documentation (large)get_catalyst_component- Retrieve production-ready componentslist_catalyst_components- Browse available componentslist_patterns- Browse design patternsget_pattern- Get detailed pattern implementations
Content Structure
content/
├── components/
│ └── catalyst/ # 27 TypeScript React components
├── docs/
│ ├── nextjs/ # Complete Next.js 15+ docs (2.9 MB)
│ └── tailwind/ # Complete Tailwind CSS docs (2.1 MB)
├── patterns/
│ ├── features/ # 6 feature patterns
│ ├── layouts/ # 4 layout patterns
│ └── pages/ # 3 page patterns
└── content-summary.json # Catalog of all content
Deployment to Smithery
Important: Content Directory Deployment
The server requires the content/ directory (5.3 MB) to be available at runtime. Smithery deploys from your GitHub repository and includes files listed in package.json "files" array.
Deployment Process:
- Ensure content is committed to git:
git add content/
git commit -m "Add documentation and pattern content"
- Push to GitHub:
git push origin main
- Deploy to Smithery:
- Smithery clones your repository
- Runs
npm install - Runs
npm run build(which copies content to.smithery/content/) - Deploys the server
Note: The server uses process.cwd() + '/content' to locate files. When deployed to Smithery, the content directory from your repository should be available in the working directory.
Troubleshooting Deployment
If you get a 500 error on Smithery:
- Verify content is in repository:
git ls-files content/ | wc -l # Should show files
du -sh content/ # Should show ~5.3M
- Check package.json "files" array includes "content":
"files": ["dist", "content", "icon.png", "icon.svg"]
- Ensure build copies content:
npm run build
ls -la .smithery/content/ # Should show content directory
- Test locally:
cd .smithery && node index.cjs
# Should start without errors
Architecture
Module System
- ES Modules only (
"type": "module"in package.json) - All imports use
.jsextensions for TypeScript files - No CommonJS
Security Features
- Input validation with regex patterns (alphanumeric +
-_.only) - Path sanitization to prevent
../traversal - Base path boundary checking
- File size limits (3MB for docs, 1MB for components)
- Safe error messages (no internal details exposed)
Caching
- LRU cache with 5-minute timeout
- Cache keys use full resolved file paths
- Improves performance for repeated documentation queries
License
MIT
Credits
- Design patterns abstracted from professional Next.js templates
- Catalyst components from Tailwind Labs
- Documentation from official Next.js and Tailwind CSS sources
推荐服务器
Baidu Map
百度地图核心API现已全面兼容MCP协议,是国内首家兼容MCP协议的地图服务商。
Playwright MCP Server
一个模型上下文协议服务器,它使大型语言模型能够通过结构化的可访问性快照与网页进行交互,而无需视觉模型或屏幕截图。
Magic Component Platform (MCP)
一个由人工智能驱动的工具,可以从自然语言描述生成现代化的用户界面组件,并与流行的集成开发环境(IDE)集成,从而简化用户界面开发流程。
Audiense Insights MCP Server
通过模型上下文协议启用与 Audiense Insights 账户的交互,从而促进营销洞察和受众数据的提取和分析,包括人口统计信息、行为和影响者互动。
VeyraX
一个单一的 MCP 工具,连接你所有喜爱的工具:Gmail、日历以及其他 40 多个工具。
graphlit-mcp-server
模型上下文协议 (MCP) 服务器实现了 MCP 客户端与 Graphlit 服务之间的集成。 除了网络爬取之外,还可以将任何内容(从 Slack 到 Gmail 再到播客订阅源)导入到 Graphlit 项目中,然后从 MCP 客户端检索相关内容。
Kagi MCP Server
一个 MCP 服务器,集成了 Kagi 搜索功能和 Claude AI,使 Claude 能够在回答需要最新信息的问题时执行实时网络搜索。
e2b-mcp-server
使用 MCP 通过 e2b 运行代码。
Neon MCP Server
用于与 Neon 管理 API 和数据库交互的 MCP 服务器
Exa MCP Server
模型上下文协议(MCP)服务器允许像 Claude 这样的 AI 助手使用 Exa AI 搜索 API 进行网络搜索。这种设置允许 AI 模型以安全和受控的方式获取实时的网络信息。