🚀 Astro Docs
Search the official Astro framework documentation for up-to-date information and examples.
Model Context Protocol (MCP) servers extend Claude’s capabilities by providing specialized tools and resources for development tasks. The astro-basics project includes 10 configured MCP servers that enhance the development experience across multiple domains.
MCP (Model Context Protocol) is a standardized protocol that allows Claude to interact with external services and tools through specialized server implementations. Each server provides a set of functions that Claude can call to perform specific tasks.
🚀 Astro Docs
Search the official Astro framework documentation for up-to-date information and examples.
🎭 Playwright
Browser automation and testing with screenshot, navigation, and interaction capabilities.
🗃️ Supabase
Complete database operations, project management, and real-time functionality.
📚 Context7
Library documentation retrieval for any package or framework with up-to-date information.
🎨 Figma
NEW! Complete design-to-code generation, variable extraction, and asset management from Figma files. Learn more →
🔐 Clerk
User authentication, organization management, and secure access control.
💻 IDE Integration
VS Code diagnostics, Jupyter notebook execution, and development environment integration.
🌐 Netlify
Deployment automation, form handling, and serverless function management.
🔍 Web Tools
Web search, content fetching, and online resource discovery.
🔧 Generic MCP
Resource listing, reading, and generic MCP server operations.
MCP servers eliminate the need to manually search documentation, configure services, or switch between tools. Claude can directly interact with your development stack.
Access up-to-date documentation, API references, and service statuses without leaving your conversation with Claude.
Seamlessly work across design (Figma), development (VS Code), database (Supabase), hosting (Netlify), and authentication (Clerk) without context switching.
Perform complex multi-step operations like deploying to Netlify while updating Supabase database schemas and generating TypeScript types.
Here’s how you might use multiple MCP servers together in a complete design-to-deployment workflow:
// 1. Generate component from Figma designawait generateFigmaComponent('user-profile-card', { framework: 'react', styling: 'scss',})
// 2. Search Astro docs for authentication patternsawait searchAstroDocs('authentication middleware')
// 3. Get Clerk user management examplesawait getClerkDocumentation('user management')
// 4. Create Supabase table for user dataawait createSupabaseTable('user_profiles', schema)
// 5. Deploy to Netlify with environment variablesawait deployToNetlify({ envVars: { CLERK_SECRET_KEY: '...', SUPABASE_URL: '...' },})
// 6. Test the complete user flow with generated componentawait testWithPlaywright('/dashboard/profile')This workflow demonstrates the power of integrated MCP servers - from design extraction to research, implementation, testing, and deployment, all within a single conversation context.