--- title: "Model Context Protocol (MCP) in Action: Using Claude to interact with Quickchat AI Agent" pubDate: 2025-04-11 description: "See how Claude uses the Model Context Protocol (MCP) to delegate product questions to a specialized Quickchat AI Agent." author: name: "Piotr Grudzień" image: "/blog-assets/authors/piotr_grudzien.jpg" image: url: "/blog-assets/posts/mcpAction_bg.jpg" alt: "Background image for Model Context Protocol (MCP) in Action: Using Claude to interact with Quickchat AI Agent" tags: ["tutorials"] --- > **Update (July 2026):** connecting Claude to a Quickchat AI Agent is now even simpler than in this demo: every agent has a hosted MCP server URL you add to Claude as a custom connector. The [step-by-step tutorial with the current flow is here](https://quickchat.ai/post/expose-ai-agent-as-mcp-server). This post is a demonstration of how two different AI systems can work together using **MCP (Model Context Protocol)**. In this example, Claude (from Anthropic) is connected to a Quickchat AI Agent that specializes in answering questions about a specific product: a fictional mobile phone called _Hello Phone_. The result is a smooth, human-like conversation, even though two AIs are working together behind the scenes. Watch the entire interaction here: ## What Is MCP? **Model Context Protocol (MCP)** is a way for one AI agent to connect with another (or external tools). It lets one AI know: _Here’s another AI that can answer this better than I can._ When an AI that supports MCP (like Claude in this case) sees a question outside its expertise, it can send a request to another AI that has more specific knowledge. That model can then respond with relevant information, which is returned to the user. Each AI stays specialized, and they coordinate when needed. It was a very high-level explanation of MCP for the sake of this article, so I highly recommend reading more about how MCP works exactly in our[ ](https://www.quickchat.ai/blog/introducing-mcp)[deep dive article](https://www.quickchat.ai/post/mcp-explained). ## The Demo In this setup, Claude has access to Quickchat AI Agent via MCP. When I message Claude and say: “I’m looking for a new phone, maybe a Samsung” ![Conversation with Claude](../../assets/blog/posts/mcpAction/1_Claude.png) Claude understands that my question might be better answered by another AI, and it knows it can use MCP to reach out to one. ![Claude asking to use a Tool](../../assets/blog/posts/mcpAction/2_tool.png) It asks for permission to forward the request, and once I approve, it contacts the Quickchat AI Agent trained on Hello Phone data. What follows is an **AI-to-AI conversation**. Claude explains the context to the Quickchat Agent, asks for product details, and returns a response to me. ![Claude and Quickchat AI Agent conversation](../../assets/blog/posts/mcpAction/3_SplitScreen.png) You can even see both sides of the exchange: **Right side:** My chat with Claude. **Left side:** Claude’s chat with the Quickchat Agent. When I asked for more product features, Claude again reached out to the Quickchat Agent, but it turns out the Agent’s Knowledge Base was limited. Claude relayed that back to me, apologized, and even passed along feedback when I suggested improving the Knowledge Base. All of this happened without me needing to know anything about the underlying system. This kind of architecture is useful in many areas: product support, internal tools, sales conversations, or AI agents that need to query company-specific knowledge. Rather than building large systems that try to do everything, MCP allows us to build small, accurate systems that work together. **Quickchat MCP is coming soon** We’re working on releasing MCP support for Quickchat AI Agents, so you’ll soon be able to connect your own agents to numerous external apps and tools, enabling the kind of collaboration shown in this demo. If you’d like to learn more about what it unlocks, and you haven’t already read our MCP guide, go here: [How Model Context Protocol works](https://www.quickchat.ai/post/mcp-explained).