We’re excited to share a major update in CopilotKit’s MCP ecosystem: We’ve launched the Vibe Coding Server, a new MCP server built with Tadata, designed to make coding copilots code reliably with CopilotKit.
Alongside it, we refreshed the Open MCP Client, so you can plug copilots into MCP servers directly inside your app. Together, they give you both:
Most coding copilots fail when they don’t have the right context. They hallucinate APIs, miss integrations, or burn tokens on irrelevant docs.
The Vibe Coding Server fixes that:
So now when you ask Cursor or Claude Code:
“Build a CopilotKit UI integrated with my backend.”
→ The Vibe Coding Server streams the right snippets.
→ The copilot produces working code on the first try.
That’s what we call vibecodability.
See it in action!
Vibe Coded Demo Repo: https://go.copilotkit.ai/pkM96ie
The client makes this loop complete. We rebuilt our MCP Client into a full toolkit for agent-ready frontends:
'McpToolCall'
Any CopilotKit app can now connect directly to MCP servers without glue code.
MCP has become the standard for connecting LLMs to external tools (Claude Desktop, Cursor, etc.). But until now, copilots lacked:
CopilotKit now ships both.
It’s now easier than ever to spin up a working CopilotKit app with MCP support:
npx create-copilotkit-mcp-app
👉 Explore the Docs: MCP Client | Vibe Coding Server
👉 Check out the GitHub: CopilotKit Open MCP Client
Stay up to date and follow @CopilotKit
→ Book a call and connect with our team
Please tell us who you are → what you're building → company size in the meeting description and we'll help you get started today!
Subscribe to our blog and get updates on CopilotKit in your inbox.