What is MCP?
Model Context Protocol (MCP) is an open standard that connects AI systems to external data sources and tools. Anthropic released it in November 2024. In December 2025, they donated it to the Linux Foundation's Agentic AI Foundation, with co-founders including Anthropic, Block, and OpenAI.
MCP creates a standard interface between AI applications and the services they need to access. Instead of building custom integrations for every database, API, or tool, developers build against one protocol. The AI application handles the rest.
As of early 2026, MCP has been adopted by OpenAI (in ChatGPT and their Agents SDK), Google DeepMind (in Gemini), and Microsoft. Over 10,000 MCP servers are running in production across the industry.
How MCP Works in Dyad
Dyad acts as an MCP client. When you install an MCP server, Dyad gains new capabilities beyond code generation. It can query databases, authenticate users, deploy apps, pull documentation, and run browser automation, depending on which servers you have installed.
You install MCP servers from Dyad Hub at dyad.sh/hub. Find a server, click Add to Dyad, and the server is configured automatically. You need Dyad v0.25 or later.
MCP servers come in two types:
- HTTP transport: Remote servers hosted elsewhere (like Context7)
- Stdio transport: Local servers running on your machine
Dyad supports both. You can also add servers not listed in Dyad Hub manually, or build your own for internal tools.
Available MCP Servers
Dyad Hub includes servers for databases, authentication, deployment, documentation, analytics, and browser automation. Here are the current options.
Context7
Pulls up-to-date, version-specific documentation and code examples directly from official sources. When you are building with a framework, Context7 ensures you are working with current docs instead of outdated examples from the AI's training data.
Chrome DevTools
Debug web pages directly in Chrome. You can inspect elements, check network requests, and get performance insights without switching windows. Useful when your Dyad app has a UI bug you cannot track down.
Neon
Manage your Neon Postgres database from within Dyad. Create tables, run queries, and handle migrations without opening a separate SQL client.
Auth0
Connect to your Auth0 tenant to create applications, manage users, and deploy Actions. You can set up authentication for your app through conversation instead of navigating the Auth0 dashboard.
Convex
Build full-stack apps with a real-time backend. Query tables, run functions, manage environment variables, and analyze logs. Convex handles the backend while Dyad handles the frontend.
Netlify
Deploy your Dyad app directly to Netlify. Push updates, configure build settings, and manage your site without leaving the editor.
Amplitude
Add behavior analytics to your app. Track events, analyze user flows, and run experiments. Useful once your app has users and you need data on how they interact with it.
Playwright
Write and run end-to-end browser tests. Automate user flows to catch bugs before deployment.
Browserbase
Run headless browser sessions for scraping, testing, or automation at scale. Useful when Playwright on your local machine is not enough.
Astro Docs Server
Access official Astro documentation. If you are building an Astro site in Dyad, this keeps you working with current framework patterns.
Example Workflows
Building a SaaS App
- Use Neon for the database
- Use Auth0 for user authentication
- Use Amplitude for analytics
- Deploy with Netlify
Each step happens inside Dyad. You describe what you need, and Dyad uses the appropriate MCP server to make it happen.
Debugging a UI Issue
- Run your app in Chrome
- Ask Dyad to inspect the failing component using Chrome DevTools
- Get specific information about CSS, network requests, or JavaScript errors
- Fix the issue in your code
Working with Current Documentation
Install Context7 before starting a new project. When you ask Dyad to use a specific library or framework, it pulls from official docs instead of relying on potentially outdated training data.
Adding Your First MCP Server
- Open dyad.sh/hub
- Browse the available servers
- Click Add to Dyad on any server you want
- Open Dyad and start a new chat
- The server's capabilities are now available
I recommend starting with Context7 if you work with frameworks that update frequently. Start with Neon or Convex if you need a database. Start with Netlify if you want to deploy without configuring hosting separately.
Custom MCP Servers
If your team uses internal APIs or proprietary systems, you can build a custom MCP server and add it to Dyad manually. The MCP specification is documented at modelcontextprotocol.io. Any server that follows the protocol works with Dyad.
This is useful for connecting Dyad to internal databases, custom deployment pipelines, or company-specific tools that will never appear in a public hub.
Limitations
MCP servers extend what Dyad can do, but they add dependencies. If an MCP server goes down or changes its API, that capability becomes unavailable until the server is updated. Servers that run locally (stdio transport) avoid this issue but require setup on your machine.
Some servers require API keys or authentication. You configure these when you add the server. Keep in mind that connecting Dyad to external services means your queries go to those services.
