Add REST API endpoint for MCP server

[JakeSCahill]

Add POST /mcp/api/ask endpoint for tools like Redleader that can't use MCP protocol directly. Includes x-client-id header for analytics.

[netlify]

✅ Deploy Preview for redpanda-documentation ready!

Name	Link
🔨 Latest commit	0a6c3a1
🔍 Latest deploy log	https://app.netlify.com/projects/redpanda-documentation/deploys/694507a1c1a9c1000851d9a6
😎 Deploy Preview	https://deploy-preview-155--redpanda-documentation.netlify.app
📱 Preview on mobile	Toggle QR Code... Use your smartphone camera to open QR code link.
Lighthouse	1 paths audited Performance: 77 (🟢 up 41 from production) Accessibility: 96 (no change from production) Best Practices: 100 (🟢 up 25 from production) SEO: 83 (🔴 down 9 from production) PWA: - View the detailed breakdown and full score reports

---

To edit notification comments on pull requests, go to your Netlify project configuration.

[paulohtb6]

Test request

curl -X POST \
  https://deploy-preview-155--redpanda-documentation.netlify.app/mcp/api/ask \
  -H "Content-Type: application/json" \
  -H "x-client-id: test-client" \
  -d '{"question": "What is Redpanda?"}' \
  -w "\nStatus: %{http_code}\nTotal time: %{time_total}s\n"

Response

{"success":true,"data":"# Current > Get-started\n## Introduction to Redpanda\n\nPage options\n\nCopy as Markdown\nCopied!\n\nView as plain text\n\nAsk AI about this topic\n\nAdd MCP server to VS Code\n\nDistributed systems often require data and system updates to happen as quickly as possible. In software architecture, these updates can be handled with either messages or events.\n\n- With messages, updates are sent directly from one component to another to trigger an action.\n- With events, updates indicate that an action occurred at a specific time, and are not directed to a specific recipient.\n\nAn event is simply a record of something changing state. For example, the event of a credit card transaction includes the product purchased, the payment, the delivery, and the time of the purchase. The event occurred in the purchasing component, but it also impacted the inventory, the payment processing, and the shipping components.\n\nIn an event-driven architecture, all actions are defined and packaged as events to precisely identify individual actions and how they're processed throughout the system. Instead of processing updates in consecutive order, event-driven architecture lets components process events at their own pace. This helps developers build fast and scalable systems.\n\n### What is Redpanda?\n\nRedpanda is an event streaming platform: it provides the infrastructure for streaming real-time data.\n\nProducers are client applications that send data to Redpanda in the form of events. Redpanda safely stores these events in sequence and organizes them into topics, which represent a replayable log of changes in the system.\n\nConsumers are client applications that subscribe to Redpanda topics to asynchronously read events. Consumers can store, process, or react to the events.\n\nRedpanda decouples producers from consumers to allow for asynchronous event processing, event tracking, event manipulation, and event archiving. Producers and consumers interact with Redpanda using the Apache Kafka® API.\n| Event-driven architecture (Redpanda) | Message-driven architecture |\n| --- | --- |\n| Producers send events to an event processing system (Redpanda) that acknowledges receipt of the write. This guarantees that the write is durable within the system and can be read by multiple consumers. | Producers send messages directly to each consumer. The producer must wait for acknowledgement that the consumer received the message before it can continue with its processes. |\n\nEvent streaming lets you extract value out of each event by analyzing, mining, or transforming it for insights. You can:\n\n- Take one event and consume it in multiple ways.\n- Replay events from the past and route them to new processes in your application.\n- Run transformations on the data in real-time or historically.\n- Integrate with other event processing systems that use the Kafka API.","client_id":"test-client","duration_ms":3700}
Status: 200
Total time: 6.866531s