Eyebrow Background Glow

MCP Apps: Bring MCP Apps to your users!

Learn More
Copilot Kit Logo
Docs
Blog
Products
Examples
Gen UI
AG-UI
MCP Apps
A2UI
Pricing
Sign Up
Back
Introducing the Vibe Coding Server + CopilotKit MCP Client
By Eli Berman and Nathan Tarbert
August 21, 2025

Announcing the Vibe Coding Server (Optimized by Tadata) + CopilotKit MCP Client

Making coding copilots actually useful

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:

  • A client bridge (frontend ↔ MCP servers)
  • A coding context source (CopilotKit docs + examples on tap)

Why Vibe Coding Server?

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:

  • Structured access to official CopilotKit docs + real code examples
  • Auto-fetches only relevant snippets (no page dumps → fewer tokens, faster)
  • Removes boilerplate tagging in every prompt — copilots always have context
  • Tested to deliver 66% faster integrations and fewer retries

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 Open MCP Client (Refreshed)

The client makes this loop complete. We rebuilt our MCP Client into a full toolkit for agent-ready frontends:

  • Tool discovery at runtime
  • Native actions (LLMs call MCP tools alongside frontend/backend actions)
  • Live context streaming into conversations
  • UI integration with 'McpToolCall'

Any CopilotKit app can now connect directly to MCP servers without glue code.

Why This Matters

MCP has become the standard for connecting LLMs to external tools (Claude Desktop, Cursor, etc.). But until now, copilots lacked:

  • A reliable client layer for apps
  • A reliable context server for coding

CopilotKit now ships both.

Getting Started

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

Want to learn more?

→ Book a call and connect with our team

Please include who you are, what you're building, and your company size in the meeting description, and we'll help you get started today!

Top posts

See All
Reusable Agents Meet Generative UIs
Anmol Baranwal and Nathan TarbertMarch 12, 2026
Reusable Agents Meet Generative UIsOracle, Google, and CopilotKit have jointly released an integration that standardizes how AI agents are defined, how they communicate with frontends in real time, and how they describe the UI they require. The integration connects three distinct layers. Oracle's Open Agent Specification (Agent Spec) provides a framework-agnostic way to define agent logic, workflows, and tool usage once and run it across compatible runtimes. AG-UI handles the live interaction stream between the agent and the frontend, keeping tool progress, state updates, and user interactions synchronized while the agent is executing. A2UI, developed by Google, allows agents to describe the UI they need - forms, tables, multi-step flows - as structured JSONL, which CopilotKit then renders automatically inside the host application. Previously, each of these layers required custom implementation per project. This release establishes a shared contract across all three, meaning agent developers can define the agent once, expose a standardized interaction stream, and have the frontend render structured UI surfaces without writing custom wiring for each tool or workflow. The practical impact is reduced integration friction across the ecosystem - agent runtimes and frontend clients that implement these standards can interoperate without lock-in to a specific framework or vendor.
The Developer's Guide to Generative UI in 2026
Anmol Baranwal and Nathan TarbertJanuary 29, 2026
The Developer's Guide to Generative UI in 2026AI agents have become much better at reasoning and planning. The UI layer has mostly stayed the same, and it is holding back the experience. Most agent experiences still rely on chat, even when the task clearly needs forms, previews, controls, or step-by-step feedback. Generative UI is the idea that allows agents to influence the interface at runtime, so the UI can change as context changes. This is usually done through UI specs like A2UI, Open-JSON-UI, or MCP Apps. We'll break down Generative UI, the three practical patterns, and how CopilotKit supports them (using AG-UI protocol under the hood).
Bring MCP Apps into your OWN app with CopilotKit & AG-UI
Anmol Baranwal and Nathan TarbertJanuary 22, 2026
Bring MCP Apps into your OWN app with CopilotKit & AG-UIToday, we are excited to announce CopilotKit’s support for MCP Apps. Now, MCP servers can finally ship an interactive UI that works out of the box in real agent applications.
Are you ready?

Stay in the know

Subscribe to our blog and get updates on CopilotKit in your inbox.